Loading...
Loading...
Found 46 Skills
Surface interface quality concerns. Works on code, screenshots, specs, or plans.
Navigate the stardust design pipeline — assess project state under `stardust/` and recommend the next design stage. Use when the user wants to check design-pipeline progress, doesn't know which stage to run next, asks a general question about `stardust/` artifacts without naming a specific stage, says `/stardust`, or asks about files under `stardust/` (brand, briefings, wireframes, prototypes) without a clear edit target.
Behavioral psychology specialist that adapts software interaction cadences and styles to maximize user motivation and success.
The official Digital Speed brand persona, voice, and values. Use when asked to write any content, copy, or communication on behalf of Digital Speed.
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.
Write clear design rationale connecting decisions to user needs, business goals, and principles.
Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships.
Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.
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.
In large applications, information architecture determines whether users can find, understand, and act on data. Naming matters. The UI should mirror the data model and signal how data can be transformed. Dangerous or irreversible changes always require a confirm dialog. Use when designing navigation, naming entities, structuring large feature sets, or modelling data-driven UI.
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
Maps interaction structure and flow — produces breadboard notation with edge cases, failure paths, and open decisions