← ClaudeAtlas

add-architecture-discoverylisted

Use when documenting project architecture — generates Technical Spec section in CLAUDE.md
brabos-ai/code-addiction · ★ 8 · AI & Automation · score 75
Install: claude install-skill brabos-ai/code-addiction
# Architecture Discovery <!-- uses: - skill: add-claude-md-style - command: /add.build - command: /add.plan - command: /add.wiki - skill: add-architecture-discovery/backend-analyzer.md - skill: add-architecture-discovery/database-analyzer.md - skill: add-architecture-discovery/frontend-analyzer.md - skill: add-architecture-discovery/spine-analyzer.md --> Analyzes the codebase and updates the Technical Spec section of CLAUDE.md with structured data in a token-efficient format. **Principle:** Discover, don't impose. Document what EXISTS in the code. CLAUDE.md is self-contained. Never invent patterns. Never create separate `technical-spec.md` files. --- ## When to Use Triggers: need architecture docs, update CLAUDE.md, document technical spec, `/add.plan` needs context, `/add.build` needs patterns. Auto-loaded by: `/add.plan`, `/add.build`. ## When NOT to Use - Greenfield projects with no code yet — nothing to discover - Single-file scripts or trivial repos — no architecture to document - `.codeadd/wiki/` already current and CLAUDE.md Technical Spec reflects the codebase --- ## Phase 0 — Automated Discovery Run: `bash .codeadd/scripts/architecture-discover.sh` → `.claude/temp/architecture-discovery.md` Collects: {"includes":["package.json","turbo.json","tsconfig","dir structure depth 3","stack detection","patterns (CQRS,Repository,DI)","controllers,services,repositories","frontend (UI,state,forms,stores,hooks)","workers,cron,events,webhooks","integrations","statisti