Loading...
Loading...
Found 36 Skills
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.
Activates the Product Designer to create UI mockups and specs complying with Polaris. Use when designing user interfaces or planning UI components.
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.
Generate and explore ideas effectively. Use when starting new projects, solving problems, or exploring solutions. Covers ideation techniques and divergent thinking.
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.
Build trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.
Apply cognitive bias knowledge to product design and decision-making. Use when designing user experiences, analyzing user behavior, improving conversions, or ensuring ethical design practices.
Create engagement through strategic information gaps that drive user action. Use when designing notifications, writing headlines, planning onboarding flows, or creating content that needs to capture and hold attention.
Understand and design for users' preference for current state over change. Use when planning migrations, introducing new features, designing defaults, or overcoming resistance to product adoption.
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
Use when the user wants IxLab to design or redesign a page, flow, feature, component, or cross-cutting system and produce persistent UX and UI artifacts in the correct order.