Prompt file imported from jlaws/dotfiles (
.codex/prompts/j-arch.md). Fill in{{arguments}}before use. Copyright stays with the author.
Before starting, gather diagnostic context:
- Detect project architecture from config files and directory structure — monolith, microservices, serverless, etc.
- Identify API patterns by searching for route definitions, API specs (openapi.yaml, swagger), or GraphQL schemas.
- Check architecture documentation for existing ADRs (glob
docs/adr/**/*.md), design docs, or README architecture sections. - Get scope overview of the target area (if {{arguments}} specifies a component, scope to that; otherwise scan for src/, services/, api/, or similar directories).
For deep architecture guidance, delegate to the architecture-specialist agent, passing the diagnostic findings above and the request. It loads its skills (design-first) and the .agents/references/architecture/ library, then returns specific guidance. Verify its output against the codebase before presenting.
If the consultation reaches a significant architecture decision, offer to capture it as an ADR (see the architecture-decision-records reference) in docs/adr/<topic>/<slug>.md. If an accepted ADR already covers the decision, amend it (Amendment Log row plus an updated bump) or supersede it instead of writing a new file. Skip minor or easily reversible changes.
Help with: {{arguments}}