Skip to content
Skills Library
Design & UX · Building & coding

building-interactive-prototypes

/building-interactive-prototypes

Takes an approved Discovery Plan to a working, clickable prototype: presents plain-language layout options (A, B, C), builds the prototype component by component with a review after each, and walks the expert through it. Use when the user says "build the prototype", "let's build it", "show me a working version", "what should it look like", "layout options", "wireframe" or "walk me through it", and an approved plan exists. Not for production code or for reengineering an existing app.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 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.
Content35 / 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
11
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.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

Takes an approved Discovery Plan to a working, clickable prototype: presents plain-language layout options (A, B, C), builds the prototype component by component with a review after each, and walks the expert through it. Use when the user says "build the prototype", "let's build it", "show me a working version", "what should it look like", "layout options", "wireframe" or "walk me through it", and an approved plan exists. Not for production code or for reengineering an existing app.

Triggers from the description

build the prototypeletshow me a working versionwhat should it look likelayout optionswireframewalk me through it
Original author description

Takes an approved Discovery Plan to a working, clickable prototype: presents plain-language layout options (A, B, C), builds the prototype component by component with a review after each, and walks the expert through it. Use when the user says "build the prototype", "let's build it", "show me a working version", "what should it look like", "layout options", "wireframe" or "walk me through it", and an approved plan exists. Not for production code or for reengineering an existing app.

How it works

  1. Contents
  2. Constraints
  3. Quick start
  4. Workflow
  5. Verification
  6. References
Original SKILL.md headings · 45 lines, 254 words
SKILL.md preview
---
name: building-interactive-prototypes
plugin: agent-exploration-cycle
description: >
  Takes an approved Discovery Plan to a working, clickable prototype: presents plain-language layout
  options (A, B, C), builds the prototype component by component with a review after each, and walks
  the expert through it. Use when the user says "build the prototype", "let's build it", "show me a
  working version", "what should it look like", "layout options", "wireframe" or "walk me through
  it", and an approved plan exists. Not for production code or for reengineering an existing app.
allowed-tools: Bash, Read, Write
---

# Building Interactive Prototypes

Phases 2 and 3: [prototyping-chain.mmd](references/prototyping-chain.mmd).

## Contents

- [Constraints](#constraints) • [Quick start](#quick-start) • [Workflow](#workflow) • [Verification](#verification) • [References](#references)

## Constraints

- **Gate**: build nothing until `exploration/discovery-plans/` holds an approved plan (`PLAN_STATUS: APPROVED` or `## SME Approval`). Existence of a file is not approval.
- Offer three distinct layout options in plain language before any code; brownfield sessions with established patterns may skip (`[~]`).
- Build 3 to 6 components, one at a time; advance only when a component is `COMPLETE` (other states: `BLOCKED`, `NEEDS_CONTEXT`). Review each for plan alignment, then quality.
- Work in an isolated workspace using the `os-control-worktree` skill; with the expert say "isolated workspace" and "validation check", never git or TDD terms ([language table](references/phase3-execution-discipline.md)).
- Write only the raw `walkthrough-notes.md`; structured notes come from `capturing-business-requirements`.
- Pick runtime and model through the `cli-agent` skill; never name models.

## Quick start

```bash
ls exploration/discovery-plans/ && ls exploration/captures/layout-direction.md
python3 ../running-exploration-cycle/scripts/validate_phase_gate.py 2
```

## Workflow

1. Gate check, then layout options and confirmation into `exploration/captures/layout-direction.md` (or `document-structure.md`).
2. Decompose, build and review each component into `exploration/prototype/`; assemble `index.html` and a `README.md`.
3. Walk the expert through each main flow; record `exploration/captures/walkthrough-notes.md`.
4. Hand over for observation extraction and the business-rule audit; report `PHASE 3 COMPLETE`.

## Verification

```bash
python3 ../running-exploration-cycle/scripts/validate_phase_gate.py 3
```

Acceptance criteria: [acceptance-criteria.md](references/acceptance-criteria.md).

## References

- Absorbed skills: [visual-companion.md](references/visual-companion.md) (layout options) • [prototype-builder.md](references/prototype-builder.md) (phase coordinator) • [subagent-driven-prototyping.md](references/subagent-driven-prototyping.md) (component loop)
- Guides: [prototyping-build-guide.md](references/prototyping-build-guide.md) (build modes, review) • [phase3-execution-discipline.md](references/phase3-execution-discipline.md) (isolation, language, why validate) • [prototype-builder-agent.md](references/prototype-builder-agent.md) (walkthrough script) • [acceptance criteria](references/prototype-builder-acceptance-criteria.md)
Files in this package (11)
  • SKILL.md 3 KB
  • evals/evals.json 2 KB
  • references/acceptance-criteria.md 2 KB
  • references/phase3-execution-discipline.md 4 KB
  • references/prototype-builder-acceptance-criteria.md 2 KB
  • references/prototype-builder-agent.md 5 KB
  • references/prototype-builder.md 2 KB
  • references/prototyping-build-guide.md 3 KB
  • references/prototyping-chain.mmd 1 KB
  • references/subagent-driven-prototyping.md 2 KB
  • references/visual-companion.md 2 KB

Versions

The database has no other skills named building-interactive-prototypes.

Database snapshot: 13.11.2026 · package version a257d2c69465 (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

  • 100proto-feedback
    Add pinned comments and version history to a clickable HTML prototype, or iterate its design by applying reviewer feedback to the next version. Use for requests such as "rerun it", "apply the feedback", or "make v3" when working with a prototype and its feedback kit.
  • 100iteration-prototype-fidelity
    Use this skill when picking the appropriate prototype fidelity for an iteration cycle — sketches vs. wireframes vs. clickable Figma vs. code prototypes vs. production beta. Trigger when planning a research session, when a project is over- or under-investing in prototypes, or…
  • 100qstack-ui-prototype
    Build a clickable static HTML prototype of one or two screens and keep it in the repo under qstack/compound_engineering/prototypes/<slug>/, or attach it to a QStack plan, where it is embedded in plan.html through an iframe with a link to open it in its own tab. Works from a…
  • 90prototyping
    Use when building an artifact whose purpose is to answer a specific question — paper sketch, wireframe, clickable mockup, wizard-of-oz, role-play, service prototype, or code spike — at the lowest fidelity sufficient to produce that learning. Do NOT use for production-grade…
  • 95arn-spark-clickable-prototype-teams
    This skill should be used when the user says "clickable prototype teams", "arn clickable prototype teams", "team clickable prototype", "debate clickable prototype", "collaborative interaction review", "clickable prototype with debate", "team-based interaction review",…
  • 100arn-spark-clickable-prototype
    This skill should be used when the user says "clickable prototype", "arn clickable prototype", "interactive prototype", "test interactions", "validate UX", "user journeys", "test navigation", "make it clickable", "prototype interactions", "test the prototype", "build the…

Feedback and reports

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