Total 50,367 skills, Product & Design has 1898 skills
Showing 12 of 1898 skills
Use this skill when designing pricing models, packaging products into tiers, building freemium funnels, implementing usage-based billing, structuring enterprise pricing, or running price tests. Triggers on pricing pages, monetization strategy, willingness-to-pay research, price sensitivity analysis, free-to-paid conversion, seat-based vs consumption pricing, and A/B testing prices.
Use this skill when working with game balancing - economy design, difficulty curves, progression systems, reward schedules, playtesting analysis, or tuning game parameters. Triggers on any game design task involving resource sinks and faucets, XP curves, loot tables, difficulty scaling, player retention mechanics, or interpreting playtest data to adjust game feel.
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", or "test assumptions". Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done. Trigger with 'lean', 'startup'.
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
Plan user journeys, onboarding flows, engagement strategies, and day-to-day workflows for digital health products.
Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
Design products around price using Madhavan Ramanujam's "Monetizing Innovation" methodology—determine willingness to pay before you build, not after. Use when: **Set pricing for a new product** before or during development; **Validate willingness to pay** before investing in features; **Structure pricing tiers** (Good-Better-Best) for different segments; **Choose the right monetization model** (subscription, usage-based, freemium, etc.); **Diagnose why a product isn't monetizing** as expected
Conduct an interactive discovery interview to produce a structured product specification. Triggers: write a spec, PRD, feature spec, requirements, product requirements, scope a project, brainstorm a feature, flesh out an idea, plan a new project. Uses AskUserQuestion for all user choices; WebSearch/WebFetch when the user wants research. Outputs: user stories, acceptance criteria, technical constraints, prioritized requirements in docs/specs/ per SPEC_TEMPLATE.md. Do NOT use for: implementation, code review, debugging, refactors, or when the user already has a complete spec they only want edited.
Activate for animation, transitions, micro-interactions, loading states, and scroll-driven motion.
Hand-drawn, sketch-like style with doodles, handwritten fonts, and imperfect lines for a playful, informal feel.
Use when you have a rough product idea and want a complete PRD without sitting through an interactive grilling. Claude walks the full decision tree (edge cases, modules, schema, testing, security), self-answers with software-engineering best practices, streams the Q&A live so you can override, and writes the PRD locally with an option to push as a GitHub issue.
Apply the SERVQUAL model (Parasuraman, Zeithaml, and Berry, 1988) to measure service quality gaps across five dimensions. Use this skill when the user needs to diagnose service quality shortfalls, benchmark customer expectations against perceptions, design service improvement programs, or when they ask 'where is our service failing', 'what do customers expect vs experience', or 'how do we measure service quality'.