Prototyping in a design tool

Use whichever design tool the user or project already works in. This skill owns the process: what to prototype, how to organize the canvas, how to name screens and states, how to pair every screen with a note, and how to hand the result to planning and implementation. It does not own a component library, a capture pipeline, or a mapping from design layers to production code. Tool mechanics live in references/tools.md.

The prototype documents observable screens, states, and transitions. It does not implement behavior; production code implements it later against the paired notes and the story acceptance criteria.

Project root

Design files and the planning index are resolved from the repository where the initiative lives, not from the skills repository. If the active directory is a sibling repository, prepend the explicit project root. Ask only when the target is genuinely ambiguous.

Prompting

Use the harness's structured-question tool for choices that materially branch the result: