Total 50,502 skills, Product & Design has 1909 skills
Showing 12 of 1909 skills
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
Keep status and error colours minimal and consistent — too many semantic colours confuse users. Each colour must mean exactly one thing. Errors should be recoverable, large failures must be prevented, and the UI should always give the user a path forward. Use when designing status indicators, error states, form validation, alerts, or any feedback system.
Image generation and presentations. Use when: - User asks for images: logos, icons, app assets, diagrams, flowcharts, architecture diagrams, patterns, textures, photo edits, restorations - User needs a presentation or slide deck Covers nanobanana CLI for image generation and Slidev for presentations.
Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. Use when asked to "show me how users use", "day in the life", "UX research", "replay research", "how do customers use", "what's the user experience like for", "watch replays of", "analyze replays for", "user behavior on", or "replay UX audit" for any Sentry product surface.
Build the initial design structure from a vague or partially formed idea. Use when the task lacks a clear design tree, scope boundaries, core objects, key flows, or explicit decision points. Trigger when the user has an idea, feature request, or system goal that needs to be turned into a structured design skeleton before deeper refinement. Do not use when the design tree already exists and the main need is to deepen or validate it.
Check whether a design is complete enough to move into implementation planning. Use when a design appears mostly done and needs a final readiness review for missing branches, weak assumptions, unresolved risks, failure handling, validation gaps, or non-functional omissions. Trigger before invoking writing-plans or when the user asks whether the current design is ready to implement. Do not use as a general design-document audit for external docs or as a replacement for initial design work.
Coordinate design-stage work across specialized design skills. Use when a task needs structured design before implementation, including design decomposition, design clarification, decision routing, or readiness checks. Trigger whenever the user wants to turn an idea into an implementation-ready design, refine a partially formed design, or determine the next design step. Do not use for direct execution, implementation planning, or single-step coding tasks.
Designs products around price using the 9 rules from Ramanujam and Tacke - WTP conversations, needs-based segmentation, Good/Better/Best configuration, monetization models, behavioral pricing, and price integrity. Use when designing new products, validating pricing for SaaS/B2B/B2C launches, choosing between subscription/usage/freemium models, fixing post-launch sales below plan, diagnosing failed launches as Feature Shock/Minivation/Hidden Gem/Undead, or when product teams say 'let's price it later'. Not for pure commodities or cost-plus regulated environments.
April Dunford's 10-step positioning methodology for B2B tech products. Use when customers don't understand the product, sales cycles are long because reps must "explain it," prospects compare you to wrong competitors, or you face price pressure despite a good product. Covers competitive alternatives, unique attributes, value themes, target market characteristics, market category (Head to Head / Big Fish Small Pond / New Game), and trend layering.
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Documents edge cases, error states, boundary conditions, and recovery paths for a feature. Use during specification to ensure comprehensive coverage, or during QA planning to identify test scenarios.
Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks for a "design review", "design critique", "5 维度评审", "design audit", or "what's wrong with my design".