메뉴
Use before major product, UI/UX, branding, or prototype work to clarify goals, audience, constraints, design system, variations, and deliverables.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use for product design, UI/UX, branding, high-fidelity web/mobile/desktop interfaces, HTML prototypes, design systems, frontend implementation, and design quality work.
Use to create, repair, or enforce design tokens, semantic surfaces, light/dark themes, spacing, radius, typography, component variants, and reusable UI primitives.
Use for empty states, no-data UI, AI output streaming, thinking steps, loading states, skeletons, progressive disclosure, and conversational product surfaces.
Use after design or implementation to package handoff notes, refactor UI code, split god components, document tokens, and prepare maintainable frontend deliverables.
Use for React Native, Expo SDK 56, NativeWind, iOS/Android UI, mobile UX flows, touch targets, safe areas, and mobile design-system implementation.
Use for interaction design, animations, progressive blur, animated borders, liquid metal accents, transitions, gesture feedback, and motion quality review.
| name | product-design-discovery |
| description | Use before major product, UI/UX, branding, or prototype work to clarify goals, audience, constraints, design system, variations, and deliverables. |
Use this skill when the user starts a new design task or when requirements are broad, ambiguous, or missing context.
Turn vague product intent into enough context to design or implement responsibly.
For broad design work, ask a focused question set covering:
If the user has already given enough information, do not ask redundant questions. State assumptions and proceed.
Use this format when it helps:
<design_brief>
<goal></goal>
<audience></audience>
<platforms></platforms>
<source_context></source_context>
<constraints></constraints>
<deliverables></deliverables>
<variation_plan></variation_plan>
<assumptions></assumptions>
<acceptance_criteria></acceptance_criteria>
</design_brief>
Good hi-fi design must be rooted in existing context. Before designing from scratch, inspect or request:
If none exists, explicitly say the work will use a new design direction and define that direction before implementation.