UX design principles and diagnostic frameworks. Use when: app feels uncomfortable, designing user journeys, layout decisions, product planning. Do not use for: visual styling, color choices, component implementation (use design-system skill). Workflow: Often used before design-system (new features) or standalone (diagnosis, improvements).
Excellent UX/UI Designer and critical thinker who translates product owner outputs into clear, elegant user experiences. Creates minimalist, high-quality interfaces inspired by Tesla and Apple. Produces precise ASCII UI layouts, component structures, and viewport variations (mobile, tablet, desktop). Designs micro-interactions, transitions, feedback states, loading patterns, and error messaging. Asks thoughtful design questions about intent, constraints, and edge cases. Welcomes feedback and iterates quickly. Use when designing user interfaces, creating wireframes, defining interaction patterns, building component systems, or refining designs.
Creates a comprehensive action plan that addresses both substance (strengthening your proposal, filling evidence gaps, doing research) and politics (winning over key people, sequencing conversations, handling objections). Use after /clarify or when you need to turn a goal into concrete actions that make your case stronger AND navigate the people involved.
Professional, skeptical communication style focused on critical thinking and coaching. Never over-enthusiastic, always verifies before agreeing, challenges ideas constructively. Use when you want a persona to act as an expert peer who coaches rather than serves.
Lost and found operations expertise from Maria covering intake procedures, claiming process, fraud prevention, and pattern recognition for efficient item recovery
Generate implementation specs from design specs. Takes a design spec file and produces a detailed, phased task breakdown ready for autonomous execution. Use after brainstorming is complete and design spec is written. Invoke with the design spec file path as argument.
Expert guidance for writing automotive manufacturing business processes, work instructions, and standard operating procedures. Follows IATF 16949, ISO 9001, and APQP/PPAP standards. Covers assembly, machining, quality/inspection, and material handling. USE WHEN user says 'write work instruction', 'create business process', 'automotive SOP', 'manufacturing procedure', 'APQP documentation', 'process flow', or 'quality procedure'. Integrates with A3CriticalThinking for problem solving and SupplyChain for supplier requirements.
Broad ideation and problem definition using Socratic questioning. Use for early-stage exploration when the problem isn't well-defined.
Ensures web applications are accessible to all users including those with disabilities, following WCAG standards
User feedback patterns for interactions - loading states, success/error messages, form validation, empty states. Ensures users understand system state and next steps. Use when implementing user-facing state changes and interactions: - Form submissions with validation feedback, success/error messages - Async operations needing loading indicators (API calls, data fetching) - Error handling flows with clear recovery paths and retry options - Empty state designs with helpful messaging (no data, no results) - User mentions "form", "loading", "error", "validation", "async", "API call" Keywords: loading, success, error, form, validation, async, feedback, toast, empty state Focus on WHEN to show feedback, WHAT type (toast/inline/modal), HOW LONG (timing).
SKILLを作成・整理する際の設計原則とベストプラクティスを提供します。「ハードガードレールで担保されている要素は書かない」「用途をできるだけ絞る」などの原則をカバーします。新しいSKILLを作成する時、既存のSKILLをレビューする時にアクティベートします。
Designer-turned-developer who crafts stunning UI/UX even without design mockups
Pre-implementation research for design, architecture, and impact analysis. Use during brainstorming, architectural design, or before implementation to understand dependencies and integration points. Triggers on (1) designing or architecting a feature, (2) brainstorming implementation approaches, (3) analyzing impact of proposed changes, (4) exploring reference materials in extra/, (5) creating research reports before planning.
두손기획 인쇄 시스템의 비즈니스 규칙. 수량 표기, 가격 계산, 제품별 단위, 규격/옵션 표기 등 프로젝트 전반에 적용되는 규칙을 정의합니다. 두손기획 프로젝트 작업 시 항상 이 규칙을 따라야 합니다. Keywords: 두손기획, 수량, 연, 매수, 단위, 전단지, 명함, 가격, 주문, 규격, 옵션
Matches user profiles to job requirements with semantic understanding. Use when evaluating how well a candidate fits a specific job posting.
Validates Requirements Phase completion before advancing to Design Phase. Checks business requirements document for completeness, quality gate compliance, and readiness for design work.
Write implementation-ready software technical specifications for senior engineers.
Defining clear ownership models and escalation procedures to ensure incidents are handled by the right people at the right time.
Generate consistent, well-formatted reports from UX evaluation findings
Generate a collaborative draft document with clarifying questions for a new feature
Design system patterns with DTCG tokens, WCAG 2.2, and Figma integration
