prototype
Skill9 starsChanged 2 months agoMITView on GitHub
Render 2–3 distinct UI directions side by side and stress-test component states (loading, error, empty, disabled, overflow) before committing to one production layout. Trigger for “prototype”, “varian”, “side-by-side”, “bandingkan arah”, “tunjukkan 2 opsi”, or “cek semua state”. Text-only axes stay on design-direction; frame-by-frame motion is not this skill.
194 other projects use a version of this.
Adopted by
Most recently taken up by
- gaoyu06/harnesstheir own version, first seen Nov 8, 2026
- Firzus/agent-skillstheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use playtest-report, soak-test and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
- lilangMaxSkill
team-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
- CoralGameSkill
team-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 14 projects that use this
- +5 more from lilangMax
- +3 more from CoralGame
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- mattpocock/skills★ 309ksame name
- emilkowalski/skill★ 55ksame name
- emilkowalski/skills★ 55ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- GreyDGL/PentestGPT★ 16ksame name
- spree/spree★ 16ksame name
- usekaneo/kaneo★ 9.7ksame name
- podman-desktop/podman-desktop★ 8.1ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/design-system-enforcer.mdcCursor rule
- frontend-expertSkill
- accessibilitySkill
- anti-slop-codeSkill
- anti-slop-designSkill
- app-shellSkill
- architectureSkill
- componentsSkill
- content-designSkill
- data-fetchingSkill
- design-colorSkill
- design-directionSkill
- design-foundationsSkill
- design-surfacesSkill
- design-typographySkill
- design-vocabularySkill
- devtoolsSkill
- engineering-vocabularySkill
- fidelitySkill
- formsSkill
- frontend-expertSkill
- marketingSkill
- monitoringSkill
- motion-inspectionSkill
- motionSkill
- performanceSkill
- polishSkill
- quality-loopSkill
- responsiveSkill
- seoSkill
- skill-authoringSkill
- testingSkill
- tokensSkill
- webglSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
After design-direction when they need proof, not another paragraph
“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prototype
Overview
Judgment without a render is three similar skins. This skill shows 2–3 directions on distinct axes, then presses real states. Pick one variant before the production build chain.
When to use
- User asks to prototype, compare, or see options on screen
- After
design-directionwhen they need proof, not another paragraph - Stress-test states on an existing component or chosen variant
- Blank-canvas UI where shipping one layout would hide the other axes
When to skip
- Text approaches only / still choosing an axis →
design-direction - “Langsung saja” / direction already locked → build chain
- Micro polish on one chosen UI →
polish - Visual AI-slop audit →
anti-slop-design - Pixel/Figma match →
fidelity - Frame-by-frame motion / reverse-engineering animation →
motion-inspection
MUST
| Rule | Detail |
| Rendered, not sketched | Variants are real markup/CSS in the project stack — not ASCII mockups as the deliverable |
| Distinct axes | 2–3 options; each changes hierarchy, layout, density, interaction, or expression — not hue-only skins |
| Shared facts | Same product content, tokens/project system, and constraints across variants |
| Cap | Do not emit 5 coded mocks or keep all variants in the shipped product |
| Stress states | Default, loading, empty, error, disabled, long/localized text, 320px overflow |
| Pick then build | Name the winner; then design-foundations → tokens → components |
Workflow
- Inherit — load
design-directionfirst if axes are not yet named. - Render — place 2–3 variants side by side (≥1024) or stacked (<768).
- Stress — run the state matrix on the recommended variant (all variants if cheap); inspect local clipping and text/plot readability at actual size, not just viewport overflow. Use the craft-comparison lenses in
references/prototype.md. - Recommend — one winner + why; wait unless they already picked.
- Discard — delete or isolate losing variants; do not ship a gallery as the app.
- Handoff — foundations → tokens → (+ shell/data/forms) → components → rest of
/ui.
Boundaries
- May decide: stacked vs split comparison; which variant to stress first.
- Must not: invent copy/metrics, restyle tokens per variant, treat this as a Figma file, or inspect animation frame-by-frame.
Checklist
- Axes named (or
design-directionskipped for a locked direction) - 2–3 rendered variants on distinct axes
- State matrix exercised
- One winner chosen; losers not in the production tree
- Build chain continues from foundations/tokens
Depth
How to compare and stress: references/prototype.md.
Axes: references/design-axes.md.
States chrome: references/data-fetching.md / references/component-patterns.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.