Loading...
Loading...
Found 151 Skills
Help users de-risk new product bets by testing core assumptions, building low-fidelity prototypes, and gathering high-signal evidence before investing heavy engineering resources.
Build a throwaway UI prototype to react to before committing. Prefers the /design canvas; falls back to a self-contained HTML artifact when /design is not available.
프로토타입 제작 전에 아이디어의 실현 가능성을 검증하고 핵심 기능 1개로 좁힌다. 이 스킬은 사용자가 직접 호출할 때만 사용한다. 일반 대화에서는 자동으로 발동하지 않는다.
Use when you need to execute R3 (Prototype Generation) in the product requirement Spec process of sdlc-dev, generate requirements/prototype.md based on requirements/prd.md (including task flow + page structure + ASCII wireframe + AC mapping + walkthrough script), and avoid proceeding with generation without context/PRD, using Open Questions instead of verification checklists, or using non-ASCII formats that make the prototype untraceable and unreviewable.
흑백 HTML 와이어프레임 기반 화면 기획 스킬. "화면 기획", "와이어", "화면 설계", 화면 ID(O1/M1 등), "이 화면 만들어줘" 같은 의도가 보이면 발동.
[user/auto] 비교로 불확실성을 줄일 수 있을 때 disposable UI 또는 logic prototype을 만들고 실행한다. production implementation이나 대화형 아이디어 탐색에는 적용하지 않는다.
Build throwaway code that answers a question, whether an interactive state model you can drive, a script that measures one thing, or competing UI mocks to choose between, then fold the answer into the decision and delete the code. Use when the user says "prototype this", "spike this", "throwaway explore X", "does this state model hold up", "will this design survive <hard case>", "is this library fast enough", "do these two actually interop", "show me a few options for this screen", "mock up three versions", or "/prototypekit". Not a demo generator and never production code.
Build a throwaway prototype that answers one design question — UI variants on a real route, or a single-file logic demo anyone can drive. Use when a design question is answered better by looking at something than by talking about it.
Swiss-style user-research narrative template in warm-paper editorial aesthetics. Use when users ask for a premium research deck or story-first live artifact with minimalist typography, high-clarity layout, subtle motion, donut breakdowns, and keyboard/click navigation across slides in a single HTML file.
**TRIGGER: about to populate `AskUserQuestion` options with `preview:` content for any visual UI / screen / layout / component / animation comparison.** STOP and ask first: *"Quick inline chip comparison, or a full HTML prototype you can open in the browser?"* Chips flatten color, type, spacing, and motion into monospace; HTML prototypes are real. **No carve-out for "simulate", "demo", "mock up", "quick decision" — those name the surface, not an exception.** When user picks HTML, this skill creates prototypes for visual design, component playgrounds, animation tuning, and design system exploration — even when the final target is React, Swift, SwiftUI, Android, or another framework. Use whenever the user wants to mock, prototype, sketch, tune, or explore any UI element before production code. HTML is the fastest design-thinking surface; reach for it even for non-web targets. For N alternatives use html-brainstorm-grid; for a single tunable component use this skill.
Editorial-minimalist: 暖色单色 canvas + serif display + grotesque body
Design the structural anatomy of screens at wireframe fidelity — what goes where and why, before anyone argues about how it looks. Part of the Intent design strategy system. Produces lo-fi idea boards for divergent exploration, complete interactive grayscale wireframes with real labels and real hierarchy, and click-through prototypes that materialize flow logic from /journey. Trigger on: wireframe, wireframes, wireframing, thumbnails, "sketch the screen", "lay out this page", "what goes where on this screen", screen layout, page structure, lo-fi, mid-fi, click-through prototype, wireflow, "wireframe the dashboard", or any request to design the structure of a screen before its visual design. The flow through screens belongs to /journey; the information structure belongs to /organize; the words belong to /articulate — this skill owns the screen itself.