444060c3eb
- Introduced `critic`, an independent adversarial reviewer for security and correctness. - Added `fable-orchestrator` to manage task routing and verification. - Implemented `gauntlet-critic` for fresh-context evaluation of gauntlet rounds. - Created `planner` for generating executable implementation plans with dependencies. - Developed `security-auditor` for application security reviews and audits. - Established `system-steward` to improve agent prompts and skills based on verified failures. - Added `dev-loop` skill for autonomous development loops over repositories. - Implemented `gauntlet-loop` skill for iterative quality benchmarking against reference standards. - Updated project settings to utilize the new orchestrator agent. - Created documentation for `GAUNTLET.md`, `PROGRESS.md`, and `REFERENCE_BAR.md` to track project status and quality benchmarks. - Added detailed prompting style guide to enhance understanding of prompt patterns and agentic loops.
2.9 KiB
2.9 KiB
name: design-spec
description: Turn a feature contract into an implementable UX spec BEFORE any user-facing implementation — flows, every screen state, components, complete copy in all supported locales, accessibility, and verifier-checkable acceptance criteria. Owner: ux-ui-designer. Do not use for non-UI work or after the build (that is design-review).
allowed-tools: Read Grep Glob Write Edit
Produce the binding UX spec the builder implements from. A spec that cannot be verified is an opinion — every requirement here must be checkable.
- Read the inputs. The task contract,
docs/DESIGN_SYSTEM.md(create it from the template below if absent), the closest existing screens (templates/widgets), and the user context indocs/SELF_MODEL.md/ project planning. Reuse existing components and patterns by name; propose a new pattern only when no existing one fits, and record it inDESIGN_SYSTEM.md. - Write
docs/design/<feature>.md(≤ 2 screens), containing:- User + job: who uses this and what job it completes; the success moment in one sentence.
- Flow: entry point → steps → exit, with the step count justified (fewer taps beats more options; name the target, e.g. "receipt in ≤ 3 taps").
- Screen states — all of them: empty, loading, error, success, and (for offline-capable surfaces) offline / queued / sync-pending / sync-rejected. A state without a design is a bug deferred to production.
- Components: reused ones by name and path; new ones with their
DESIGN_SYSTEM.mdentry. - Copy: every label, button, error, and empty-state message, in every supported locale — no placeholders, no English-only rows where i18n is required.
- Accessibility: tap-target sizes, contrast, focus order, screen-reader labels for icon-only controls.
- Acceptance criteria: numbered, observable checks a verifier can run or inspect ("tapping X from state Y shows Z"), including one criterion per non-happy-path state.
- Stay in scope. Spec only what the contract includes; list out-of-scope UI you deliberately did not design so nobody infers it was forgotten.
- Return the spec path, the design-system delta, and any open decision that changes scope, risk, or cost.
docs/DESIGN_SYSTEM.md starter template
# Design system
> Conventions every user-facing change follows. Updated only by ux-ui-designer; violations are design-review findings.
## Principles
- [e.g. fewest taps to complete the money task; offline is a first-class state; all copy ships in en + tl]
## Foundations
- Type scale / spacing / color roles: [tokens or file path]
- Tap targets ≥ 48dp; contrast ≥ WCAG AA; focus order follows visual order.
## Components
| Component | Path | Use for | Never for |
| --- | --- | --- | --- |
## Screen-state patterns
- Empty / loading / error / offline / queued / sync-rejected: [canonical pattern per state]
## Copy rules
- [tone, locale coverage, currency/date formats]