Loading...
Loading...
Found 22 Skills
Product interaction and UX expert. Use when reviewing UI/UX, conducting heuristic evaluations, designing user journeys, applying cognitive psychology principles, or ensuring WCAG 2.2 accessibility compliance.
단계 사이 선택 활동으로, 사용자 인터뷰와 여정 매핑과 유사사례 조사로 이해를 깊게 판다. 이 스킬은 사용자가 직접 호출할 때만 사용한다. 일반 대화에서는 자동으로 발동하지 않는다.
Investigar, estruturar e validar experiências com pesquisa, arquitetura da informação, jornadas, fluxos, formulários, onboarding e recuperação de erros. Use para problemas de usabilidade, fluxo, descoberta, conteúdo ou validação com usuários; não reduza UX a acabamento visual.
Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product logic — pipelines, dependency resolution, state machines, pricing/tier enforcement, packaging. Checks feature correctness against product rules, edge cases, state transitions, data flow, and user journey completeness. Dispatched by loop-execution-evaluator when track type is 'business-logic', 'generator', or 'core-feature'. Triggered by: 'evaluate logic', 'test business rules', 'verify business rules', 'check feature'.
Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.
Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships.
Maps interaction structure and flow — produces breadboard notation with edge cases, failure paths, and open decisions
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use `zeigarnik-effect`.
Analyze conversion funnels and identify drop-offs. Use when: analyzing checkout funnel; tracking signup flow; identifying conversion blockers; optimizing user journey; visualizing funnel performance
Design or review product experiences through user goals, journeys, information architecture, task flows, interaction models, feedback, recovery, and cross-screen continuity. Use when the primary question is how users understand and complete a goal across steps or surfaces. Do not use for visual styling, implementation-only logic, or unsupported user-research claims.