What problem does it solve?
Non-trivial repositories often lack a clear, maintained architecture boundary contract, leading to inconsistent module boundaries, forbidden dependency violations, and confusion when making boundary-affecting changes to the codebase.
Core Features & Use Cases
- Dual-mode operation: Supports both inspecting existing repositories to capture actual architecture and creating greenfield architecture baselines for new projects.
- Concrete boundary documentation: Records module responsibilities, allowed/forbidden dependencies, composition roots, shared-code rules, testing boundaries, and accepted deviations specific to your repo.
- Use Case: Use this skill when bootstrapping a new non-trivial codebase, or before implementing changes that modify module boundaries if your repo lacks an existing architecture document.
Quick Start
Invoke the create-architecture skill to generate or update your repo's docs/ARCHITECTURE.md file with concrete, stack-native boundary rules tailored to your codebase.