Total 50,474 skills, Product & Design has 1908 skills
Showing 12 of 1908 skills
A/B test evaluation, cohort retention analysis, funnel metrics, and experiment-driven product decisions. Use when analyzing experiments, measuring feature adoption, diagnosing conversion drop-offs, or evaluating statistical significance of product changes.
Generate interactive prototypes from PRD documents. **This skill must be used when users need to generate interactive UI prototypes, multi-page jump demos, or quickly validate product designs based on PRD**. Trigger scenarios: Users say "generate prototype", "make a demo", "generate navigable prototype", "turn PRD into clickable pages".
Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
Extract and structure fuzzy product ideas into validated problem statements, target users, and jobs-to-be-done. Use when a user has a raw idea, concept, or solution in mind but hasn't clearly articulated the problem, target user, or assumptions. This skill helps users communicate context to coding agents more effectively, reducing iteration cycles and "that's not what I meant" moments.
Produce a one-page product intent specification with problem statement, users, metrics, risks, and acceptance criteria in Given/When/Then format. Use before any technical design or implementation work begins.
Surgically updates a specific section of .marrow.md without re-running the full extraction. Accepts a new value, color, image, or description and patches only the relevant section — leaving everything else intact. Use this skill when the user wants to update one part of the extracted soul, change the brand accent color, update spacing rules, replace a typeface, refine the brand personality, or extract color from a new reference image. Triggers on: /marrow-update, or prompts like "update the accent color to X", "change the brand color", "update spacing in marrow", "the font changed to X", "update marrow with this new color", "patch marrow", "update just the accent", "marrow-update accent #FF6B6B", "update the palette from this image". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Use when generating a Product Requirements Document from a high-level idea, feature request, or product vision — covers discovery questions, structured PRD drafting, section-by-section review, and transition to implementation planning
Create a complete, actionable design system for any project (website, app, product) grounded in physical/sensory anchoring rather than design trends. Delivers CSS tokens, typography scale, component patterns, accessibility checklist, and absolute rules as a single developer-ready markdown document. Use this skill whenever the user asks to create a design system, theme, color palette, visual identity, CSS tokens, theme variables, or propose an art direction. Also triggers on "style guide", "site colors", "choose fonts", "look and feel", "visual branding", "charte graphique", "identite visuelle", "direction artistique", "refonte visuelle", or any new project where design isn't yet defined — propose this skill proactively.
This skill should be used when the user needs to structure what to build and when by converting discovery opportunities into prioritized bets and roadmaps. Use when organizing product capability blocks, writing solution briefs, planning quarterly cycles, or communicating product direction without false precision.
Used when applying the SCAMPER creative thinking framework to systematically generate innovative ideas for products, services, processes, or concepts. It is triggered by requests involving SCAMPER (奔驰法), creative ideation, innovative thinking, product improvement, service optimization, brainstorming, systematic innovation, or when users want to explore multiple creative perspectives for an existing object, service, or business model.
Activate for user flows, information architecture, interaction patterns, wireframes, and usability decisions.