Loading...
Loading...
Found 27 Skills
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.
Low/high fidelity wireframes, user flows, information architecture, prototyping techniques, and design iteration processes
Plan content architecture, editorial calendars, taxonomy, and content audits. Activate for content-heavy projects or when organizing information across pages/sections.
UX/UI design principles for clean, intuitive interfaces. Use when designing layouts, improving usability, planning information architecture, or ensuring accessibility. Triggers on "user experience", "usability", "information architecture", "accessibility", "interaction design".
UX design principles for creating intuitive, accessible, and user-centered digital experiences
Create, refine, review, critique, or iterate on page briefings under `stardust/briefings/**/*.md` (including `_site.md`) — intent, audience, key messages, CTAs, tone, page copy (headlines, hero, section copy), imagery direction, plus site-level information architecture and multi-page content reuse maps. Sole source of truth for page copy. Independent of brand extraction: can be authored before or after `/stardust:brand`. Use when the user wants to plan pages, write briefings, define audience or CTAs, plan imagery, map shared sections across pages, when the user asks to change, refine, refactor, review, improve, polish, critique, or iterate on any file under `stardust/briefings/`, or whenever the user asks to modify a file under `stardust/briefings/**/*.md`.
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.
Expert in documentation structure, cohesion, flow, audience targeting, and information architecture. Use PROACTIVELY for documentation quality issues, content organization, duplication, navigation problems, or readability concerns. Detects documentation anti-patterns and optimizes for user experience.
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.
Write and research technical documentation. Cover information architecture, style guides, API documentation, user research, content strategy, and documentation operations. Triggers on "write technical documentation", "create API docs", "developer tutorial", "information architecture", "style guide", "content strategy", "documentation audit", "user research", or "technical writing". Developer learning programs and curriculum: developer-education-lead.
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.