Menu
Screaming Architecture project structure (grouped by business feature) — assign to phases creating the tree structure or new modules
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | architecture |
| description | Screaming Architecture project structure (grouped by business feature) — assign to phases creating the tree structure or new modules |
The architecture must reveal the business intention at first glance. Group by Feature rather than by technical role (components/hooks/utils).
src/
├── core/ # Global config (Axios, Contexts)
├── shared/ # Atomic UI components, cross-cutting Hooks & Utils
└── features/ # Folders by Business Domain (Screaming)
└── billing-management/ # Explicit Feature name
├── api/ # Feature-specific service calls
├── components/ # Internal components (e.g.: InvoiceTable.tsx)
├── hooks/ # Domain-specific state logic
├── types/ # Interfaces (e.g.: billingTypes.ts)
├── utils/ # Pure business helpers
└── __tests__/ # Unit and integration tests
├── InvoiceTable.test.tsx
└── useBilling.test.ts
Architect Agent guidelines (CODE ONLY MODE) — converts the business specification (spec.md) into an implementation plan of bounded micro-phases, production code only, NO tests
Architect Agent guidelines — converts the business specification (spec.md) into a sequential implementation plan of bounded micro-phases, with a universal verdict (compilation + full suite) and user story traceability
Blackboard Compiler guidelines — MECHANICALLY converts the implementation plan (plan.md) into a strict blackboard.yaml for the orchestrator
PO Agent guidelines — turns a raw need (need.md) into a refined business specification (spec.md) with user stories, testable acceptance criteria and an explicit scope
Java/Spring Boot production code rules (records, constructor injection, layer separation) — assign to backend feature phases
Fast, isolated Spring Boot test rules (JUnit 5, Mockito, MockMvc slices) — assign to backend test phases