Loading...
Loading...
Found 61 Skills
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
The official Digital Speed brand persona, voice, and values. Use when asked to write any content, copy, or communication on behalf of Digital Speed.
Define an illustration style guide with visual language, color usage, and application rules.
Translate PRDs into detailed UX specifications including user flows, screen descriptions, components, and interaction patterns. Use when a user has a PRD and needs to define the concrete UI/UX before generating development prompts. Bridges product requirements to implementation details.
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
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.
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.
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
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.