Loading...
Loading...
Found 82 Skills
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
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.
Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on
Deep-dive into customer empathy and user journey thinking. Use when designing onboarding, improving UX, planning features, or trying to understand how to delight users faster.
Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment. Use Day 1 morning and afternoon after the sprint brief is locked. Sets the design target for Tuesday's sketches and Wednesday's storyboard.
Clarify, review, and write project requirements. Use this when you want to discuss requirements, determine whether requirements are clear or ready to enter the design phase, sort out user stories and processes, complete the scope of existing function transformations, or form requirement documents that can be consistently understood by product, development, and testing teams. It is not responsible for technical solutions, task planning, coding implementation, or acceptance execution.
Design first-run experiences that get users to value quickly without overwhelming them.
Turns ideas into working prototypes and MVPs with the smallest useful scope. Use when validating a core hypothesis, shipping a demo-ready flow, or choosing a practical stack for fast learning.
Помогает разобрать продуктовую или UX-задачу до проектирования решения: увидеть скрытое предположение, отделить образ продукта от модели и технологии, найти наиболее ценный вопрос или следующий шаг. Использовать, когда нужно придумать или обсудить фичу, экран, флоу, редизайн, концепт, принцип интерфейса или продуктовую стратегию; когда запрос сразу предлагает решение; когда варианты кажутся одинаково возможными; или когда нужен требовательный дизайн-консультант. Не использовать для исполнения уже согласованного решения, точечной визуальной правки или технической реализации без продуктовой развилки.