Prototype
Turn Claude into a Senior Design Architect — DTCG design tokens, 42 components, WCAG 2.2 accessibility, any-framework code, 138 design systems, and runnable skills.
npx -y skills add plugin87/ux-ui-agent-skills --skill prototypeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts. Use when the user wants to prototype, wireframe, map a user flow, or plan/run usability testing.
SKILL.md
1.6 KB, as published. Nobody here has run it
Skill: Prototype & Research
Guide work through the right fidelity level with validation.
Steps
- Read
workflows/prototyping.md(5-level fidelity ladder, journey mapping template, usability-testing script, sample data). - Identify the current need and pick the lowest fidelity that answers it — never skip levels:
- Content-first (info needs) → Wireframe (layout/nav) → Low-fi (task completion) → High-fi (visual/a11y) → Code (feasibility/perf).
- For flows: produce a user-journey map with decision points, error paths, and edge cases.
- For validation: define the usability test (tasks, success criteria, 5-user rule) using the script.
- High-fi/code steps pull tokens (
tokens/*), components (components/*), taste (taste/*), and a11y (accessibility/*).
Output
The artifact at the chosen fidelity + an explicit "what we validate next" plan.
Verification (before declaring done)
- The fidelity matches the question being answered — no level skipped.
- Flows include decision points, error paths, and edge cases (empty/loading/overflow), not just the happy path.
- A concrete validation step is named (tasks + success criteria), not "test later".
- High-fi/code artifacts pass the same token + a11y bar as
design-code(no hardcoded values, contrast, states).