Your app architecture, decided together and documented.
What it does
Guides users through architecture decisions for a new app and records the agreed boundaries, domain model, data choices, and resilience plan in project documentation.
When to use it
Use when designing a new app's architecture, choosing boundaries and a domain model, or deciding between a monolith and microservices.
How to use it
Give it a new app idea and its project; it asks you to choose architecture decisions and writes approved documentation that supports resuming across sessions.
What you provide
- An existing project
What you need · 8
Uses this skill for Phase 1 boundary design and layering the first feature; a fallback brief allows the phase to proceed without it.
Uses this skill for Phase 2 bounded contexts, domain vocabulary, and aggregates; a fallback brief allows the phase to proceed without it.
Uses this skill for Phase 3 load estimates, bottlenecks, and justified scaling choices; a fallback brief allows the phase to proceed without it.
Uses this skill for Phase 4 data models, storage engines, isolation, and locking decisions; a fallback brief allows the phase to proceed without it.
Access · 0
No additional actions listed.