product-messaging
Creates complete messaging frameworks for products. Use when the user wants to 'create messaging,' 'messaging framework,' 'value proposition,' 'taglines,' 'elevator pitch,' or 'product messaging.'
38,472 Skills
搜索范围为本次公开目录;榜单和数量均为记录时的数据。
Creates complete messaging frameworks for products. Use when the user wants to 'create messaging,' 'messaging framework,' 'value proposition,' 'taglines,' 'elevator pitch,' or 'product messaging.'
Designs complete onboarding, activation, retention, and expansion lifecycles for SaaS products. Use when the user mentions 'onboarding lifecycle,' 'activation strategy,' 'user onboarding,' 'time to value,' 'aha moment,' 'onboarding audit,' 'retention lifecycle,' or 'lifecycle des
Creates complete positioning frameworks for products. Use when the user wants to 'position my product,' 'create positioning,' 'positioning framework,' 'competitive positioning,' 'how to differentiate,' or 'positioning statement.'
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code
Reproduce web UI bugs and verify browser workflows with Playwright MCP or the project's existing browser tests.
目录记录日期:2026-11-21