process-feedback
SEMO 피드백 이슈 분석 및 반영. Use when (1) "피드백 처리해줘", "이슈 반영해줘", (2) check-feedback 후 수정 요청, (3) SEMO 시스템/패키지 개선 요청.
SEMO 피드백 이슈 분석 및 반영. Use when (1) "피드백 처리해줘", "이슈 반영해줘", (2) check-feedback 후 수정 요청, (3) SEMO 시스템/패키지 개선 요청.
Correlate content attributes with performance metrics across GA4, GSC, and SE Ranking. Identify what drives performance and build optimization hypotheses.
Execute SQL, analyze funnels, and define success metrics.
Realiza entrevistas profundas para extraer especificaciones completas de proyectos
EARS記法を用いた要件定義書を作成・編集します。ユーザーストーリーの作成、受入基準の定義、非機能要件の整理が必要な場合に使用してください。
WCAG 2.2 AA compliance, ARIA patterns, screen reader compatibility, and inclusive design patterns
Los usuarios esperan que tu sitio funcione como otros que conocen. Use cuando evalúe patrones de diseño, tome decisiones sobre convenciones, o considere innovaciones en UI.
Los objetos deben sugerir cómo se usan. Use cuando diseñe botones, controles interactivos, o cualquier elemento que invite a la acción.
This skill should be used when writing requirements, specifications, or user stories. Triggers on phrases like "write requirements", "create spec", "define user stories", "document feature", "specify behavior", "what should the system do", or when reviewing specification quality. Provides patterns for clear, testable, unambiguous requirements.
Guide for creating new Transmissions applications with decision support for core vs remote development
Proactively learn about the user through onboarding and ongoing observation. Use at session start and when you notice potential preferences.
Use when asked to "working backwards", "PR/FAQ", "Amazon PR/FAQ", "write a press release", "define a new product", or "write a customer-focused PRD". Helps define products by starting with the customer problem and desired outcome before building. The Working Backwards process (developed at Amazon) forces clarity on customer value before committing engineering resources.
Elimina información irrelevante que compite por atención con lo esencial. Use cuando evalúe densidad de información, jerarquía visual, o simplifique interfaces sobrecargadas.
Use when asked about "pricing strategy", "willingness to pay", "value metric", "packaging tiers", "good better best pricing", "subscription vs usage pricing", or "price before product". Helps design products customers will pay for and choose pricing models that capture value. Based on Madhavan Ramanujam's Monetizing Innovation framework from Simon-Kucher.
spec(仕様書)が存在しない場合の文脈収集を担当するSkill。Issue本文、ユーザー指示、関連コードから要件を推測し、曖昧な点をAskUserQuestionで確認します
Use when executing Phase 1 of vrau workflow - exploring requirements and design
사용자가 간단한 개발 요청을 할 때, 프로젝트 특화 정보를 반영하여 보다 정확하고 문맥에 맞는 요구사항으로 변환합니다.
Animation specialist - handles Framer Motion patterns, motion tokens, transitions, and micro-interactions for the calm aesthetic.
Building and nurturing thriving developer communities
Extracts interaction specifications from Figma designs (hover states, transitions, animations, triggers). Updates the "インタラクション" section in screen spec.md.
Before setting outcome goals, identify your understanding level. If you don't know the levers, set a learning goal, not a revenue goal. Don't commit to outcomes you can't control.