From A2Z FORGE
Run the A2Z FORGE design research tournament and establish the design constitution. Use before building a new interface or when a product direction must change.
How this skill is triggered — by the user, by Claude, or both
Slash command
/a2z-forge:forge-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read \`${CLAUDE_PLUGIN_ROOT}/references/WORKFLOW_PROTOCOL.md\` before mutating project state.
Read `${CLAUDE_PLUGIN_ROOT}/references/WORKFLOW_PROTOCOL.md` before mutating project state.
product goal; users; flows; references; accessibility target; brand constraints.
reference ledger; three distinct directions; independent rankings; selected direction; DESIGN_CONSTITUTION.md.
Extract principles rather than copying. Generate meaningfully different directions. Test realistic flows. Record minority concerns. Define tokens, layout, typography, icons, imagery, motion, states, responsiveness, and anti-references. Require rendered evidence before acceptance.
Honor the current permission mode. Use only task-relevant tools and installed skills. Log consequential actions. Persist outputs before reporting success.
On tool failure, record the command, safe retry state, and blocker. Retry only idempotent work. Never convert a missing credential, unavailable provider, failed test, or incomplete adapter into a success claim.
`/forge-design for a serious technical local dashboard`
Directions are structurally distinct, the selected flow passes keyboard and responsive checks, and no competitor is cloned.
npx claudepluginhub jumpsy/a2z-forge --plugin a2z-forgeGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.