Loading...
Loading...
Found 23 Skills
Activate for user flows, information architecture, interaction patterns, wireframes, and usability decisions.
Plan content architecture, editorial calendars, taxonomy, and content audits. Activate for content-heavy projects or when organizing information across pages/sections.
Design UI as information architecture + interaction + visual tone, then translate into implementable specs. Apply when discussing screen design, component design, design systems, or visual hierarchy.
Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.
Generate an Information Architecture (IA) document from a service plan, PRD, or product idea. Outputs a structured screen hierarchy as Markdown nested lists and saves to SCREENS.md.
Use when the user needs user research methodologies, persona development, journey mapping, usability testing plans, or information architecture analysis. Triggers: user says "user research", "persona", "journey map", "usability test", "card sort", "heuristic evaluation", "information architecture", "user interview", understanding user behavior.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean.
Design experiences that optimize mental resources using Cognitive Load Theory. Use when designing interfaces, creating onboarding flows, planning information architecture, or improving task completion rates.
Evaluates interfaces, components, screens, and flows against universal UX/UI principles (heuristics, UX laws, Gestalt, cognitive psychology, accessibility) and delivers concrete, prioritized improvements. Use whenever the user shares UI code, screenshots, components, or mockups and wants feedback — even if they don't use the words "critique" or "review". Also trigger when the user asks "what's wrong with this UI", "how can I improve this", "review my component", "does this look right", "give me feedback on this design", or shares any interface and asks for thoughts. Trigger for partial slices too (a single button, form, or card) — not only full screens.
Structure information so people can find what they need, understand where they are, and navigate confidently. Covers navigation pattern design, taxonomy, labeling systems, search and browse strategy, wayfinding, and IA research methods. Trigger when designing navigation structures, categorization schemes, site maps, taxonomies, labeling systems, search experiences, or asking "how should we organize this?" Also trigger for card sorting, tree testing, information findability problems, or when users report they can't find things. Use this skill any time the structural organization of information is the problem — not the flow through it, not the words in it, not the visual presentation of it.
Evaluate design effectiveness from a UX perspective. Use when user says "critique this design", "review the UX", "give design feedback", "is this good design", "design review", "evaluate this layout", or wants expert evaluative feedback on visual hierarchy, information architecture, and emotional resonance.