prototype · pwguler — Claude Code skill: UI prototypes and installation
This Claude Code skill builds visual UI prototypes before implementation begins. It activates for mockup requests and helps settle a look or flow that text cannot resolve.
MIT 978 installs ★ 10 updated 2026-10-16
npx skills add pwguler/skills --skill prototype -a claude-codeWhat prototype does
The skill creates a disposable UI prototype as a standalone HTML file outside the repository. It uses fake data and leaves backend connections, saved state, branches, and production code untouched. If the design direction is undecided, the file can show several distinct layouts.
A source for typography, color, and spacing is needed first: the project’s DESIGN.md, existing design tokens, or a reference chosen with the user. When the source is a website or a font pairing, the resolved tokens go into DESIGN.md, the one project file the prototype leaves behind. The HTML opens in a browser. Once the user reacts, the prototype is discarded and the selected direction moves into the real work.
What it helps with
- test an interface’s visual direction before implementation
- compare distinct page layouts in one file
- review a screen flow with a visual mockup
- align a prototype with project design tokens
Example prompts for the agent
- Build a settings screen prototype so we can settle the layout before implementation.
- Put several distinct homepage directions in one standalone HTML file.
- Create a mockup from the tokens in
DESIGN.mdand use fake data.
How to install prototype
1Skills CLI (Vercel)
npx skills add pwguler/skills --skill prototype -a claude-code2Manually: put the files in place
~/.claude/skills/prototype/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/prototype/
1Skills CLI (Vercel)
npx skills add pwguler/skills --skill prototype -a codex2Manually: put the files in place
.agents/skills/prototype/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pwguler/skills --skill prototype -a cursor2Manually: put the files in place
.cursor/skills/prototype/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pwguler/skills skills/prototype2Manually: put the files in place
.github/skills/prototype/SKILL.md1Skills CLI (Vercel)
npx skills add pwguler/skills --skill prototype -a gemini-cli2Platform CLI
gemini skills install https://github.com/pwguler/skills --path skills/prototypeManually: put the files in place
.devin/skills/prototype/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pwguler/skills --skill prototype -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about prototype
How do I install prototype in Claude Code?
Run npx skills add pwguler/skills --skill prototype -a claude-code. The skill file is at ~/.claude/skills/prototype/SKILL.md.
What does prototype do?
It creates a standalone HTML UI mockup with fake data for discussing visual choices or screen flow before implementation. It does not connect a backend or modify production code.
What does prototype need before it can build a mockup?
It needs a source for typography, color, and spacing: the project’s DESIGN.md, existing tokens, or a reference selected with the user. If the source is a site or font pairing, the resolved tokens are written to DESIGN.md first.
Source text
SKILL.md · MIT
--- name: prototype description: Build a throwaway UI prototype for the user to react to before any real code. Read this skill when the user asks for a mockup or a prototype of a UI. Use it when a design decision depends on look, feel, or flow that text cannot settle. --- The user wants a throwaway prototype to react to before any real code. It settles a question of look, feel, or flow that text cannot settle. 1. Base the prototype on a design system before you build. Never build on the defaults of the model, because they look generic. Use the `DESIGN.md` of the project, or its existing design tokens, when they exist. When none exists, get one from the user first. That is a `DESIGN.md`, a reference site to match, or a font pairing from a source such as fontpairs.co. Do not start until typography, color, and spacing come from a real source. 2. Sometimes that source is a reference site or a font pairing, not an existing `DESIGN.md`. Then write the resolved tokens to the `DESIGN.md` of the project before you build: typography, color, and spacing. That file is the one thing that the prototype leaves behind. `implement` and `rubric` read it. 3. Tokens leave most of the look open. Build to [look.md](references/look.md): the defaults that generated UI tends toward, and what replaces them. 4. Build the prototype as one self-contained HTML file outside the repository. Give the user its path, to open in a browser. 5. Stop when the user has reacted. Rules: - The prototype is visual only. Mock the screens with fake data. Connect no backend, keep no state, open no branch, and touch no production code. - Write less: short labels, and no helper text or explanation that the design does not need. Generated UI explains too much. A prototype that explains too much is already wrong. - When the direction is open, put a few clearly different layouts in the file to react to. Do not show one polished guess. - Copy what exists: the markup and tokens of the real components or pages to match. Do not describe them. - The prototype is a throwaway. It settles the direction. Discard it when the user picks, and take the decision into the real work.
© pwguler · MIT · pwguler/skills
Similar skills
All skills for Design →prototype by other authors comes first.