Total 53,920 skills, Product & Design has 2074 skills
Showing 12 of 2074 skills
Standardized camera movement vocabulary for Veo 3 video generation. Use when creating video prompts that require specific camera movements, cinematography terminology, or when validating camera movement specifications. Provides authoritative reference for 50+ camera movements (Dolly, Arc, Crane, FPV Drone, Whip Pan, etc.) to ensure consistent, production-ready terminology.
Use when "product strategy", "OKR planning", "product vision", "market positioning", or asking about "competitive analysis", "product-market fit", "go-to-market strategy", "product roadmap"
Prototype and collaborate with InVision - create interactive prototypes, manage design boards, and gather feedback
Diagnose competitive product analysis state and guide through systematic market evaluation. Use when analyzing a product category, building feature comparisons, understanding competitive landscape, building personas, or deciding build vs. buy. Routes to 6 interconnected frameworks based on current analysis state.
Simulate a senior high school Grade 3 general technology tutor, providing guidance on general technology issues including technical design, structural analysis, flowcharts, algorithms, and simple programming. Focus on cultivating practical operation skills, design thinking, and problem-solving abilities. Activate this when students raise questions about technical design, structural optimization, process design, and algorithms.
Build or evolve a design system by producing a Design System Operating Pack: charter, token model (incl. depth/elevation), component inventory + roadmap, blockframe-to-component mapping, documentation plan, and governance/adoption plan. Use for design systems, component libraries, design tokens, UI kits, and pattern libraries.
Transform text-heavy slides into visual storytelling. Suggest layout improvements, icon usage, and data visualization.
Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks. Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests.
Research-driven UI/UX improvement using Mobbin. Use when user explicitly requests design pattern research ("use Mobbin", "research design patterns", "find UX patterns for X"). Requires Mobbin account and browser automation (claude-in-chrome MCP). Searches Mobbin for relevant UI patterns, extracts design principles, generates a spec document for approval, then implements. NOT for general UI work—only when user wants research-backed design.
RICE, ICE, WSJF, MoSCoW and other prioritization frameworks for product backlogs. Use when scoring features, ranking initiatives, or deciding what to build next.
Analyzes Figma designs and generates implementation-ready PRDs with detailed visual specifications. Use when user provides Figma link or uploads design screenshots. Requires Figma MCP server connection.
Builds comprehensive pricing strategies by reading business context and asking targeted questions interactively. Use when user needs pricing plans, tier structures, price points, pricing model recommendations, or any pricing-related strategy for their product or service.