html-prototype-build skill
scriptsBuild, annotate, review, screenshot, and deliver native HTML UI prototypes with AI agents using reusable UI packs, DOM-bound product annotations, in-browser Direct Edit, browser review pins, a local authoring server, an element-to-source Inspector, and multi-state screenshots. Use when the user mentions /html-prototype-build or asks to reconstruct UI in HTML, create product annotations, edit prototype styles, review or mark DOM elements, capture prototype states, package prototype deliverables, or add components to the module sketch board. Works with Claude Code, Codex, Cursor, and other Agent Skills clients; do not use for generic source-code navigation, ordinary documentation, or production frontend development.
- GitHub stars
- 29
- Files
- 61
- Last commit
- Nov 10, 2026
- License
- MIT
- Allowed tools
- —
What does the html-prototype-build skill do?
html-prototype-build is an agent skill. Build, annotate, review, screenshot, and deliver native HTML UI prototypes with AI agents using reusable UI packs, DOM-bound product annotations, in-browser Direct Edit, browser review pins, a local authoring server, an element-to-source Inspector, and multi-state screenshots. Use when the user mentions /html-prototype-build or asks to reconstruct UI in HTML, create product annotations, edit prototype styles, review or mark DOM elements, capture prototype states, package prototype deliverables, or add components to the module sketch board. Works with Claude Code, Codex, Cursor, and other Agent Skills clients; do not use for generic source-code navigation, ordinary documentation, or production frontend development.
How to install the html-prototype-build skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the html-prototype-build skill in Plugin
/plugin marketplace add Lisuiwen/ai-html-annotation /plugin install ai-html-annotation@lisuiwen-agent-skills
Install the html-prototype-build skill in Claude Code
~/.claude/skills/html-prototype-build/SKILL.md
$ npx degit Lisuiwen/ai-html-annotation/skills/html-prototype-build ~/.claude/skills/html-prototype-buildInstall the html-prototype-build skill in Claude Code (project)
.claude/skills/html-prototype-build/SKILL.md
$ npx degit Lisuiwen/ai-html-annotation/skills/html-prototype-build .claude/skills/html-prototype-buildInstall the html-prototype-build skill in Codex
~/.agents/skills/html-prototype-build/SKILL.md
$ npx degit Lisuiwen/ai-html-annotation/skills/html-prototype-build ~/.agents/skills/html-prototype-buildInstall the html-prototype-build skill in Gemini CLI
~/.gemini/skills/html-prototype-build/SKILL.md
$ npx degit Lisuiwen/ai-html-annotation/skills/html-prototype-build ~/.gemini/skills/html-prototype-buildInstall the html-prototype-build skill in Claude.ai
npx degit Lisuiwen/ai-html-annotation/skills/html-prototype-build html-prototype-build && zip -r html-prototype-build.zip html-prototype-build # claude.ai → Customize → Skills → + → Create skill → Upload a skill → html-prototype-build.zip
SKILL.md
View on GitHubHTML Prototype Build
Quick start
- Confirm the prototype type and business facts from the user's materials; ask first when information is insufficient, do not guess.
- When generating or heavily changing UI, run
node <skill-root>/scripts/resolve-pack.mjs --list, thennode <skill-root>/scripts/resolve-pack.mjs --pack=<pack-id> --select=<preset, pattern, or component id>and read only the minimal file closure it outputs. - Generate the complete
<prototype-name>/delivery directory per shared generation contract §7; route all business state throughPrototypeViewers, and use the Runtime copy as-is for the formal Client Runtime. - When done, run
npm testat the repository root; start the authoring server or scenario screenshots only when the task needs them.
Route the task first
Read only the entry that matches the current task; do not read all references at once:
| User goal | Required entry | Main output or tool |
|---|---|---|
| Generate, rebuild, or heavily change UI | UI generation | HTML prototype and on-demand UI components |
| Install or download missing UI packs | Pack install | scripts/install-pack.mjs |
| Understand Viewer, note cards, SVG connectors, or interaction lightning | Product annotations | snapshot + Client Runtime |
| Start the authoring environment, direct edit, edit notes, or jump to source | Local authoring | runtime/server/index.mjs + Author Tools |
| Add or change a sketch-board component | Sketch board components | pack manifest.json atoms + data-pack-atom |
| Add review pins to a page, export For AI | Review mark | runtime/author/tools/mark/ |
| Batch screenshots by page state | Scenario screenshots | runtime/cli/screenshot.mjs |
| Prepare final files | Delivery & iteration | Final delivery files |
| Final check before delivery | Delivery checklist | Per-item checkboxes |
When generating or heavily changing UI, read the shared generation contract first; for other tasks read the matching entry above without reading the full contract.
For visual tasks, discover packs, pick a foundation and providers via the UI pack catalog, resolve the minimal closure, and follow the consumer pack rules. When no pack is installed, follow Pack install.
scripts/ holds the agent's deterministic tools. runtime/ is split by execution boundary: client/ formal browser runtime, author/ browser authoring tools (including the sketch board), server/ local Node authoring service, cli/ standalone command-line tools. Only runtime/client/ is copied into a prototype. runtime/author/, runtime/server/, and runtime/cli/ stay in the skill.
Terminology
ponytail:— in-place comment marking an intentional prototype shortcut or uncollected state; replace it after you have real screenshots, computed styles, or interaction evidence.- Project materials — screenshots, requirements, and confirmed facts for the current task (not generic framework defaults).
Core boundaries
- Every prototype must use the distributed copies of
runtime/client/core/display-mode.js,runtime/client/core/state.js,runtime/client/notes/model.js,runtime/client/notes/viewer.jsin order;state.jsprovides the singlePrototypeViewersstate source,model.jshandles only note scenario metadata and purewhenmatching, and Notes Viewer handles only DOM/connector rendering. Do not fold these responsibilities back into the Viewer. - Formal notes are written back to
prototype/notes.snapshot.jsonly throughruntime/server/index.mjs+ Notes editor; do not inline a notes editor inprototype.htmland do not store formal notes in localStorage. - Mark is a temporary review tool in the Author Tools panel alongside Direct edit; its data goes to page-path-scoped localStorage, is never written to the snapshot, and is not injected into the source HTML.
- Direct edit previews in the authoring session only and writes back to the source HTML safely through the server.
- The authoring service only handles local editing and in-prototype source lookup; it never enters the source HTML or the final deliverable.
- The sketch board in
runtime/author/sketch/is an authoring-session page. Do not copy it into<prototype-name>/. - Screenshots consume only the URL scene and formal annotation data; they do not generate business state.
- System names, menus, fields, states, and business data must come from the user's materials; ask when information is unclear, never guess.
Files in this skill
61html-prototype-build skill questions
How do I install the html-prototype-build skill in Claude Code?
Run npx degit Lisuiwen/ai-html-annotation/skills/html-prototype-build ~/.claude/skills/html-prototype-build. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the html-prototype-build skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.