Nw Design
Designs system architecture with C4 diagrams and technology selection.
Install
npx skills add nWave-ai/nWave --skill nw-design -g -a claude-code -y- Repository
- nWave-ai/nWave628
- Category
- Design
- Updated
- 2mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).
NW-DESIGN: Architecture Design
Wave: DESIGN (wave 3 of 6) | Agents: Morgan (nw-solution-architect), nw-system-designer, nw-ddd-architect | Command: *design-architecture
Overview
Execute DESIGN wave through discovery-driven architecture design. The command starts with two interactive decisions:
- Design Scope, routes to the right architect: system-level (@nw-system-designer), domain-level (@nw-ddd-architect), application-level (@nw-solution-architect), or full stack (all three in sequence).
- Interaction Mode, guide (architect asks questions, you decide together) or propose (architect reads requirements, presents 2-3 options with trade-offs).
All architects write to docs/product/architecture/brief.md (SSOT), each in its own section. Analyzes existing codebase, evaluates open-source alternatives, produces C4 diagrams (Mermaid) as mandatory output.
Output Tiers (per D2)
Provenance: feature lean-wave-documentation, D2 (schema-typed sections), D10 (one-line expansion descriptions). Tier-1 [REF] sections (always emitted) + Tier-2 EXPANSION CATALOG items (lazy, on-demand) are the two output bands. Full contract: nWave/skills/nw-density-resolution-contract/SKILL.md.
Tier-1 [REF], always emitted
Under ## Wave: DESIGN / [REF] <Section> headings:
- DDD list, D-numbered design decisions with verdicts and one-line rationale
- Component decomposition, table of components with paths and change types
- Driving ports, inbound surfaces (CLI, skill, HTTP) named per the C4 contract
- Driven ports + adapters, outbound side-effects with adapter mapping
- Technology choices, pinned languages/frameworks/runtime versions
- Decisions table, DDD-N row per locked decision (no rationale prose)
- Reuse Analysis table, every overlapping component classified EXTEND or CREATE NEW
- Open questions, items deliberately deferred to DISTILL/DELIVER


