Loading...
Loading...
Found 82 Skills
Reduce complexity by revealing information progressively. Use when designing onboarding, complex forms, feature-rich interfaces, or any experience where showing everything at once would overwhelm users.
Surface interface quality concerns. Works on code, screenshots, specs, or plans.
Hook Model framework for building habit-forming products based on Nir Eyal's "Hooked". Use when you need to: (1) increase user engagement and retention, (2) design habit loops in your product, (3) audit why users aren't returning, (4) create effective triggers and notifications, (5) design variable reward systems, (6) increase investment and switching costs, (7) evaluate the ethics of your engagement tactics, (8) optimize onboarding for habit formation.
Activates the Product Designer to create UI mockups and specs complying with Polaris. Use when designing user interfaces or planning UI components.
Use this skill to design new products, iterate on product ideas, or develop product specifications. Triggers: "design product", "new product idea", "product concept", "product development", "product spec", "iterate on product", "product design", "invention", "prototype spec", "product requirements", "product engineering", "develop product" Outputs: Product specification, BOM estimate, feature breakdown, differentiation analysis.
Fundamental design principles based on Don Norman's "The Design of Everyday Things". Use when you need to: (1) design affordances and signifiers into interfaces, (2) analyze why products are confusing, (3) apply constraints to prevent errors, (4) design clear feedback mechanisms, (5) bridge gulfs of execution and evaluation, (6) create intuitive conceptual models, (7) apply human-centered design, (8) understand why users make errors and design fault-tolerant systems.
Apply the halo effect in product design and UX. Use when designing first impressions, brand perception, feature presentation, or understanding how one positive attribute influences perception of others.
Use for deep design discovery and problem understanding before planning or implementation. Trigger when the user wants to think deeply, build knowledge, surface edge-cases, ask many questions, or explore the problem space without producing plans or code.
Use when reviewing any interface for usability — walks through Krug's principles from Don't Make Me Think covering cognitive load, scanning, navigation, homepage clarity, mobile usability, accessibility, and the goodwill reservoir.
Design Thinking process—Empathize, Define, Ideate, Prototype, Test. Use for product design, solving ambiguous problems, or when you don't know what users really need.
Write clear design rationale connecting decisions to user needs, business goals, and principles.
Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".