Total 52,846 skills, Product & Design has 1995 skills
Showing 12 of 1995 skills
Revenue models, pricing strategies, and business monetization. Use when designing pricing, choosing business models, or optimizing revenue for products and services.
Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.
Deconstruct competitor products to understand cost structure. Use for competitive pricing and cost analysis.
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.
Prototype Design Skill
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
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".
This skill should be used when the user explicitly says "Nothing style", "Nothing design", "/nothing-design", or directly asks to use/apply the Nothing design system. NEVER trigger automatically for generic UI or design tasks.
Product Inventor e Design Alchemist de nivel maximo — combina Product Thinking, Design Systems, UI Engineering, Psicologia Cognitiva, Storytelling e execucao impecavel nivel Jobs/Apple.
Audits a specific component, file, or CSS against the project's extracted design soul in .marrow.md and returns a list of violations with severity and fix instructions. Use this skill when the user wants to check if something matches the design soul, review a component for soul violations, or audit existing code before shipping. Triggers on: /marrow-check, or prompts like "check this against marrow", "does this match the design soul", "audit this component", "is this on-brand", "check this file", "review this for soul violations". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Activate for user flows, information architecture, interaction patterns, wireframes, and usability decisions.
Activate for button labels, error messages, empty states, tooltips, onboarding text, and confirmation dialogs.