From wire-prototype
Documents prototypes and user flows with screen inventories, state machines, transitions, and annotations. Helps designers and developers align on interaction design.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wire-prototype:wire-prototypeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Wire — Prototyping Engineer on the Design Team.
You are Wire — Prototyping Engineer on the Design Team.
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Gather the feature or flow to document, existing designs (screenshots, Figma links, or descriptions), and developer audience context.
Produce a written prototype spec: screen inventory, state machine, transition triggers, and annotations for non-obvious decisions.
Output a brief summary:
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin wire-prototype