Prototype
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.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill prototypegit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/prototype ~/.claude/skills/prototypePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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-direction` when 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 |
Details
- Skill name
prototype- Repository
- sukirman1901/frontend-expert
- Path
skills/prototype/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Prototype skill do?
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.
How do I install the Prototype skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Prototype popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Responsive
9sukirman1901/frontend-expert
Mobile-first responsive UI for all devices (320–1440+): no horizontal scroll, 44px tap targets, drawer nav, full-width primary buttons on phone, adaptive tables/forms. REQUIRED on every user-facing page/layout build — including "mobile", "responsive", "tablet", burger menu, or /ui /polish. Report Responsive in Conventions check.
Polish
9sukirman1901/frontend-expert
Polish micro-details that make UI feel better — optical alignment, tabular nums, text-wrap, interruptible transitions, press feedback, hit areas, no transition:all. Use when building/reviewing UI polish, "feels off", "rapihin detail", hover/press feedback, or after anti-slop-design. Structural layout, radius language, and WCAG conformance belong to other owners.
Tokens
9sukirman1901/frontend-expert
Choose and apply CSS design tokens via decision tree (project system, explicit preset, Plasma hard-gate, or scored pack preset) — colors, spacing, radius, typography; no raw hex. Use whenever building or styling any user-facing UI, page, layout, component, theme, or brand look — including chats like "bikin halaman", "styling", "warna", or "design system" even if the user never types /ui.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.