design-bootstraplisted
Install: claude install-skill mytechsonamy/VibeFlow
# Design Bootstrap
The DESIGN phase is the one phase VibeFlow doesn't auto-analyze: a design has
to be *authored*, then reviewed. This skill is the author-side guide. It turns
the approved PRD into the design artifacts that DESIGN consensus
(`consensus.design.approved`) and the exit criteria (`design.approved`,
`accessibility.verified`) are checked against — and it lets the operator pick
**how** the design gets made.
## Phase Contract
Runs in **DESIGN** only. Before anything else, read
`vibeflow.config.json`'s `currentPhase`. If it is not DESIGN, emit:
> design-bootstrap is for the DESIGN phase only; current is `<phase>`.
> Advance to DESIGN first (`/vibeflow:advance`).
…and stop. Writes are confined to `design/**`, `.vibeflow/**`, and
`vibeflow.config.json` (the DESIGN phase-write policy).
## Step 1: Resolve context
Read:
- `vibeflow.config.json` → `domain`, `platform`, `project`, optional
`design.sourceDir` (default `design/`), optional `design.figmaFileUrl`.
- The approved PRD (from REQUIREMENTS — the `lastConsensus` primary, or
`docs/<prd>`). The design must serve the PRD's screens / flows / entities.
- Existing `design/**` (re-runs build on top of prior work, never clobber
silently).
Detect what's available, to tailor the offer:
- **design-bridge MCP** (VibeFlow's own Figma bridge): available iff the
`mcp__design-bridge__db_*` tools resolve **and** `FIGMA_TOKEN` is set
(plugin `userConfig.figma_token`). A `db_*` call that returns the
"FIGMA_TOKEN is r