architecture-boundaries
Preserve clean starter architecture boundaries between shared config, runtime wiring, API, CLI, agentic modules, and ETL modules. Use when moving code or introducing new packages in src.
Works with
--- name: architecture-boundaries description: Preserve clean starter architecture boundaries between shared config, runtime wiring, API, CLI, agentic modules, and ETL modules. Use when moving code or introducing new packages in src. license: MIT --- # Architecture Boundaries ## Boundaries - `shared`: configuration and cross-cutting helpers - `runtime`: bootstrap and application context - `api`: HTTP layer only - `cli`: command layer only - `agentic`: agent registry and execution contracts - `etl`: ETL registry and execution contracts ## Rules - Do not let API or CLI become the home of domain logic. - Do not import FastAPI into ETL or agent registries. - Keep starter extension points obvious and shallow.
More Data Engineering skills
data-pipeline
claude-office-skills/skills
Data pipeline and ETL automation - extract, transform, load workflows for data integration and analytics
ETL Pipeline
claude-office-skills/skills
Design and automate Extract, Transform, Load data pipelines for data integration and analytics
data-throughput-accelerator
affaan-m/ecc
Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much faster while preserving data correctness.

