Architecture Anti-Patterns
Named vocabulary and consequence-framing for spotting god objects, tight coupling, and shared-DB coupling.
Getest · Werkt
Wat het doet
A single-file reference that names and explains common architectural failure patterns (God Object, Big Ball of Mud, Circular Dependency, Database as Integration Point, N+1 queries, cascade failures) and gives stock phrasing for raising them with a team. Triggers when reviewing a system design, diagnosing recurring outages, or asking what mistakes to avoid before building something new.
Testrapport
Reviewed a fictional order/inventory/pricing architecture with synchronous chaining, a shared DB, and an N+1 loop: the skill named each pattern precisely (Tight Coupling/cascade failure, Database as Integration Point, N+1 Query Problem) and added stakeholder-ready framing, but the underlying technical findings matched what a baseline review already caught.
Getest op: 2026-07-15 · Claude Code 2.x (agent harness)
Installatie
git clone https://github.com/sethdford/claude-skills cd claude-skills mkdir -p ~/.claude/skills cp -r architect/architect-toolkit/skills/architecture-anti-patterns ~/.claude/skills/architecture-anti-patterns
Commando's en voorbeeldprompts
/architecture-anti-patternsNamed vocabulary and consequence-framing for spotting god objects, tight coupling, and shared-DB coupling.
Skills reageren op gewone verzoeken — geen commando's om te onthouden. Na installatie activeren prompts zoals deze de skill (in het Engels):
what's wrong with three services all writing to the same shared databaseis this checkout code an N+1 query problem waiting to happenhelp me name why this service is turning into a big ball of mud