Software Development
DESIGN CODE ARCHITECTURE
Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems, software-design-philosophy, release-it, pragmatic-programmer, 37signals-way - asking the user questions at every decision point and recording results in the project docs/ folder (ARCHITECTURE.md, DESIGN-CODE-ARCHITECTURE-PLAN.md) so the journey resumes across sessions. Use when the user wants to design a new app''s architecture, choose boundaries and a domain model, decide monolith versus microservices, or says ''how should I structure this app''. If a codebase already exists, use remove-technical-debt (aged), improve-code-quality (fresh prototype), or architecture-optimization (slow but working); if unvalidated, run create-business or create-app first. For one framework in isolation, invoke that skill directly.
- Publisher / source
- wondelai/skills (found on skills.sh, an awesome list, the CSV list)
- Upstream record
- wondelai/skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
4bf2140050ca60a10bfda878bdb86782df98a9946102461590494134c9cc0e6d