architecture
FeaturedUse when reviewing architecture in any codebase — module boundaries, stated design contracts, abstraction depth, error-handling design. Assess by default, apply changes on request; complexity is dependencies plus obscurity, and deep modules win.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- automagik-dev
- Repository
- automagik-dev/genie
- Created
- 1 years ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
architecture-review
Surfaces architectural friction in real code — shallow modules, tight coupling, untested seams — and proposes deepening refactors using Ousterhout's deep-module principle (small interface hiding a large implementation). Use when the founder says 'architecture review', 'find shallow modules', 'architectural friction', 'deep module analysis', or asks for refactor recommendations on a directory of code. Scope it to actual code (plugins/, q-system/.q-system/scripts/) — not markdown rules, canonical files, or prose.
architecture-lens
Architecture review lens for evaluating structural integrity, coupling, cohesion, and evolutionary fitness. Used by review orchestrators — not invoked directly.
architecture-review
A focused, single-lens review of a change's design and structure — not its defects. Judges separation of concerns and SOLID, coupling and cohesion, module/layer boundaries and dependency direction, whether the right abstraction is present (and the wrong/early one is absent), files and functions that have grown too large or do too much, leaky abstractions, intent-hiding names, duplication that wants to be a shared unit, and whether the change fits how this codebase is already built. Every finding cites file/module:line, a severity, the future cost it imposes, and a concrete refactor direction. Constructive and pragmatic — flags structure that will cost future change, never taste.