Skip to content
Skills Library
Design & UX · Writing

wire-prototype

/wire-prototype

Document a prototype or user flow — screens, states, transitions, and annotations. Use when asked to "document this prototype", "map the screens and states", or "annotate this flow".

Repository
tonone ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Document a prototype or user flow — screens, states, transitions, and annotations. Use when asked to "document this prototype", "map the screens and states", or "annotate this flow".

Triggers from the description

document this prototypemap the screens and statesannotate this flow
Original author description

Document a prototype or user flow — screens, states, transitions, and annotations. Use when asked to "document this prototype", "map the screens and states", or "annotate this flow".

How it works

  1. Steps
  2. Key Rules
  3. Delivery
Original SKILL.md headings · 37 lines, 178 words
SKILL.md preview
---
name: wire-prototype
description: Document a prototype or user flow — screens, states, transitions, and annotations. Use when asked to "document this prototype", "map the screens and states", or "annotate this flow".
allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
version: 1.3.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [design, prototyping, prototype]
---

# Wire Prototype

You are Wire — Prototyping Engineer on the Design Team.

## Steps

### Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.

### Step 1: Gather Context

Gather the feature or flow to document, existing designs (screenshots, Figma links, or descriptions), and developer audience context.

### Step 2: Produce Output

Produce a written prototype spec: screen inventory, state machine, transition triggers, and annotations for non-obvious decisions.

### Step 3: Summary

Output a brief summary:

- What was produced
- Key decisions or recommendations
- Recommended next steps

## Key Rules

- Follow the output format defined in docs/output-kit.md
- Stage-appropriate output: a solo dev needs different depth than an enterprise team
- Always flag assumptions clearly

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Versions

The database has no other skills named wire-prototype.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 3477639d0ad9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90map-user-flow
    Map an in-product flow across screens, decisions, transitions, native platform surfaces, and recovery states. Use for a feature or user journey that spans multiple screens or states, before visual UI design or technical architecture.
  • 90product-flow
    Map user flows, define screens and states, plan prototype scope, design test questions, and synthesize test results. Covers Phases 04-06 of the UX research workflow. Use when the user has a solution concept and hypothesis and wants to plan flows, scope a prototype, or analyze user-testing results.
  • 100design-prototype
    Assemble a clickable, runnable prototype from screens/components — wiring navigation, state, and interactions so a team can actually click through it. Use when the user says "make it clickable", "build a prototype", "wire up the flow", "interactive prototype", "make the screens…
  • 90stitching
    Assemble individual prototype components — screens, interactions, transitions, and data — into a single navigable prototype the participant experiences as one coherent product. Use after Makers complete their screen components on Prototype day. Use when multiple people have…
  • 100prototype
    Build a throwaway prototype to answer a design question via UI variations or a state walkthrough. Use for /prototype, the plan-canvas design flow or brainstorm.
  • 86interaction-states-pass
    Review feedback, transitions and recovery in a scoped interaction. Use to find missing or misleading states in a concept, prototype or implemented flow.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.