build-prototype

Generates interactive HTML/CSS/JS UI prototypes from requirement specs and design system tokens.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Samind-Samind/projexa --skill build-prototype-samind-samind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-prototype
Source: https://github.com/Samind-Samind/projexa/tree/main/.claude/skills/build-prototype
Command: npx skills add https://github.com/Samind-Samind/projexa --skill build-prototype-samind-samind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning written requirements into clickable screen prototypes is slow and inconsistent when done by hand. This Skill synthesizes existing requirement specs, backlog, feature lists, and user journeys into interactive per-screen HTML/CSS/JS prototypes with a consistent design system, so stakeholders can review real interactions before development begins. ## Core Features & Use Cases - Interactive prototype generation: Creates vanilla JS prototypes per screen (add/remove rows, popovers, tab switching, toast notifications) that run offline with no backend dependency. - Versioned output management: Organizes prototypes into versioned folders (v1, v2, ...) with metadata files, per-version indexes, and change logs, never overwriting confirmed versions without approval. - Design system enforcement: Builds or reuses a DESIGN.md token file (color tone, style, logo) so every screen stays visually consistent. - Use Case: A BA finishes screen specs for 13 MVP screens and asks to build the MVP prototype; the Skill verifies all source docs, confirms scope and versioning with the user, then delegates file writing to a prototype-builder sub agent. ## Quick Start Ask the assistant to build an interactive prototype for the MVP screens using the existing requirement specs and user journey documents.

Frequently Asked Questions about build-prototype

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an interactive HTML prototype from requirement documents?▼

Provide the screen scope (SCR codes, module names, or all screens) and the Skill reads the spec files, backlog, feature list, and user journey, then generates per-screen HTML/CSS/JS prototypes with real client-side interactions after you confirm the plan.

What input files are required before building a prototype?▼

The Skill requires backlog.md, feature-list.md, user-journey.md, and a spec file for every screen in scope. If summary files are missing it suggests running the gen-feature-journey skill first; missing specs trigger the requirement skill.

Does the prototype need a framework or backend to run?▼

No. Prototypes use vanilla JavaScript only, simulating interactions like row editing, popovers, tabs, and toasts entirely client-side, so they open offline in any browser without build steps or backend services.

How does prototype versioning work when updating existing screens?▼

The Skill checks existing vN folders and their _meta.md status, then asks whether to create a new version or edit the current one. Reviewed or Confirmed versions are never overwritten; structural changes get a new version folder.

Can I customize the visual design of the generated prototypes?▼

Yes. If no DESIGN.md exists, the Skill asks about color tone, style reference, and logo, then writes a design token file that all screens reference. Existing DESIGN.md files are reused automatically for consistency.