Loading...
Loading...
Found 107 Skills
UX design interview → living doc UX Design section (flows, screens, states, components, a11y). Optional — UI features only. Triggers: 'design the UX,' 'what screens,' 'how should users interact,' post-define. Not for: technical design (architect), requirements (define). Skip for API-only, CLI, backend, or exact UI replicas.
Use when designing animations for business tools, project management, collaboration software, or productivity apps
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.
Transforms Claude from a 'Graphic Designer' into a 'Design Thinker'. Trigger this skill whenever the user asks for design, redesign, creation of graphics, layouts, UI/UX, or any creative asset. Use this skill even if the user provides a direct request like 'make a flyer' or 'redesign my site'. The goal is to ask critical questions and solve the underlying problem before touching any visual elements.
Converge ideas of requirements, pages, modules, processes, visuals and experiences into implementable product, interaction, interface and visual design specifications
Create, refine, review, critique, or iterate on low-fidelity grey wireframes under `stardust/wireframes/**/*.html` — structure, hierarchy, section order, spatial relationships, annotations, section metadata (`data-section`/`data-intent`/`data-layout`), and multi-page fragment/reuse mapping (`data-fragment*`). Rendered from briefings. No brand required. Optional stage: users can skip to `/stardust:prototype` for branded layout directly. Use when the user wants to validate page structure before visual design, annotate a wireframe, mark reusable fragments across pages, when the user asks to change, refine, refactor, review, improve, polish, critique, or iterate on structure, section order, or block placement, or whenever the user asks to modify a file under `stardust/wireframes/**/*.html`.
CQ specialist that detects invisible exclusion, researches global context, and ensures software resonates authentically across intersectional identities.
Generous whitespace, consistent padding, and grid-based layouts for clean, readable, and breathing interfaces.
Vibrant, high-contrast palettes and gradients for engaging, memorable, and modern user experiences.
Modern minimalist aesthetic with clean lines, intentional color palette, subtle interactions, and consistent spacing.
Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.
Comprehensive end-to-end validation of the Archon Web UI using browser automation and codebase review. Use when: User wants to validate, test, or audit the Archon web interface, find UI/UX bugs, test workflow management, verify parallel agent orchestration, or run comprehensive browser-based E2E tests. Triggers: "validate ui", "test the ui", "e2e test", "browser test", "validate archon", "test archon ui", "ui audit", "ux review", "comprehensive test", "validate everything". Capability: Starts Archon, runs exhaustive browser automation tests via agent-browser CLI, performs codebase review, and produces a detailed bug/UX report. NOT for: Unit tests (use `bun test`), CLI-only validation (use /validation:validate-simple).