codebase-architect

Vertical slice architecture organizes Python modules by domain features like scrapers or analysis rather than technical layers. This Skill inspects your directory structure and project docs to recommend boundary-compliant file placement and inward dependency flow toward utils.

Migrating legacy scripts into src packages requires adapting them to match a module-per-feature pattern. This Skill recommends specific refactoring decisions and structural changes to ensure migrated code follows established vertical slice boundaries and dependency directions.

Dependency direction ensures src production code flows inward toward utils while scrapers remain independent. This Skill applies your project's module map to verify boundaries and recommend correct structural relationships between integration, analysis, and RAG components.

Documentation taxonomy places docs into correct subdirectory types like investigations, next-steps, or databases to reduce sprawl. This Skill uses your project's established decision tree to classify and route documentation files to their appropriate directories.

You need vertical slice architecture when creating new modules, migrating legacy code from scripts into src packages, or reorganizing technical debt. This Skill inspects current directories to recommend boundary-compliant structure across scrapers, integration, and analysis components.

Vertical slice architecture enforcement requires reading existing project architecture docs and module maps. Without established documentation of your project's intended structure and decision tree, this Skill cannot accurately recommend boundary-compliant placement or dependency direction.