594fccc80a
Plugin pairs with Symphony — Composer's output (issues in the project's tracker) is Symphony's input. State-aware /composer command walks the user through 11 phases: concept, users (with workflow probing for hidden actors), requirements/NFR/IA, design system, interaction design, flows, mocks, architecture, stories, roadmap, load. Each phase produces a reviewable artifact in docs/planning/ (or, for design and interaction, a project-local skill — see below). Architecture is intentionally LAST, after the spec is complete. Mocks are JSX/TSX regardless of final stack and pass a "text feasibility" audit — every visible string is categorized (static/computed/authored), computed strings are traced to source data, and any string implying an unspecified feature halts the commit. Design system and interaction design are produced as PROJECT-LOCAL SKILLS in .claude/skills/<slug>-design-system/ and .claude/skills/<slug>-interaction-design/, not as docs in docs/planning/. Skills auto-load via description matching whenever UI work happens; a reference doc gets read once and drifts out of context. The mocks skill imports tokens directly from the design-system skill for a single source of truth across mocks and (eventually) real code. ui-system is currently a PLACEHOLDER — captures the minimum needed for mocks to proceed with <TBD: ...> markers as a return-pass worklist. Full interview specification is the next pass. Council touchpoints baked in: PM/skeptic/end-user after requirements, end-user/a11y after mocks, full architecture council after architecture, plus auto-additions (legal-triage on regulated data, privacy-advocate on PII, finance-controller on money flows). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
51 lines
1.2 KiB
Markdown
51 lines
1.2 KiB
Markdown
# Information architecture
|
|
|
|
<!--
|
|
The taxonomy file. Top-level concepts, how they relate, how they're
|
|
named. Mocks and architecture both look up here.
|
|
-->
|
|
|
|
## Top-level concepts
|
|
|
|
<!--
|
|
The nouns of the app. One block each.
|
|
-->
|
|
|
|
### <Concept name>
|
|
|
|
- **What it is**: <one-line definition>
|
|
- **Identifying field(s)**: <what makes one of these unique>
|
|
- **Key attributes**: <list>
|
|
- **Relationships**: <to other concepts — "has many X", "belongs to Y", "describes Z">
|
|
- **Lifecycle states**: <if it has lifecycle — draft / active / archived / etc.>
|
|
|
|
## Relationships
|
|
|
|
<!--
|
|
A small relationship diagram in plain text or list form. The shape of
|
|
the data, before any database is chosen.
|
|
-->
|
|
|
|
- <Concept A> 1—N <Concept B>
|
|
- <Concept B> N—N <Concept C> via <Concept Join>
|
|
|
|
## Vocabulary rules
|
|
|
|
<!--
|
|
Words used in two senses on the same screen will hurt. Names every
|
|
concept with one canonical word and lists synonyms to avoid.
|
|
-->
|
|
|
|
| Use | Don't use | Reason |
|
|
|---|---|---|
|
|
| <word> | <synonym> | <why we picked one> |
|
|
|
|
## Navigation top-level
|
|
|
|
<!--
|
|
The skeleton of how a user moves through the app. Not screens — the
|
|
conceptual map.
|
|
-->
|
|
|
|
- <section> → <subsection> → <subsection>
|