plugins/lyra-ux-designer/skills/using-ux-designer/SKILL.md
Use when starting any UX/UI design task — visual design, IA, interaction, accessibility (WCAG 2.2), user research across mobile, web, desktop, game, and AI surfaces, plus first-principles audience-derived needs analysis. Routes to 11 specialist sheets.
npx skillsauth add tachyon-beep/skillpacks using-ux-designerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This meta-skill routes you to the right UX design skills based on your situation. Load this skill when you need UX expertise but aren't sure which specific skill to use.
Core Principle: Different UX tasks require different skills. Match your situation to the appropriate skill, load only what you need.
Load this skill when:
Don't use for: Backend logic, database design, pure technical implementation without UX implications. For static documentation or marketing sites (developer-tool docs, landing pages, OSS project sites), route to the sibling lyra-site-designer pack instead — this pack is for application UI (interactive web apps, mobile, desktop, game, AI surfaces).
IMPORTANT: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.
When this skill is loaded from:
skills/using-ux-designer/SKILL.md
Reference sheets like ux-fundamentals.md are at:
skills/using-ux-designer/ux-fundamentals.md
NOT at:
skills/ux-fundamentals.md ← WRONG PATH
When you see a link like [ux-fundamentals.md](ux-fundamentals.md), read the file from the same directory as this SKILL.md.
Symptoms: "What is...", "Explain...", "Teach me about...", "How does X work in UX?"
Route to: ux-fundamentals.md
Examples:
Symptoms: "Review this design", "Critique this interface", "Is this usable?", "Does this follow best practices?"
Route to: Relevant competency skills based on critique focus
General Review (no specific focus):
Specific Focus:
Add platform extension if design is platform-specific:
Symptoms: "Design a...", "Create interface for...", "Build a [feature] screen"
Route to: Competency skills + platform extension
Standard Web/Mobile Feature:
Complex Navigation/IA:
Research Phase (early discovery):
Symptoms: "Chatbot UX", "AI assistant", "copilot", "agent", "RAG UI", "streaming output", "model output is wrong / overconfident", "citations", "tool-call confirmation"
Route to: ai-experience-patterns.md
Add:
aria-live streaming + WCAG 2.2 SC 3.3.8 (don't gate AI behind cognitive auth tests)Examples:
Symptoms: "Colors don't work", "Typography feels off", "Hierarchy unclear", "Layout cramped"
Route to: visual-design-foundations.md
Add: accessibility-and-inclusive-design.md if contrast/readability concerns
Symptoms: "Users can't find features", "Navigation confusing", "Menu structure", "Content organization"
Route to: information-architecture.md
Add: Platform extension for platform-specific nav patterns
Symptoms: "Button states unclear", "No loading feedback", "Micro-interactions", "Touch targets too small"
Route to: interaction-design-patterns.md
Add: Platform extension for platform-specific interaction conventions
Symptoms: "WCAG compliance", "Accessibility audit", "Colorblind-safe", "Keyboard navigation", "Screen reader"
Route to: accessibility-and-inclusive-design.md
Note: This skill should be referenced by all other design decisions (accessibility is universal)
Symptoms: "Understand users", "User interviews", "Usability testing", "Mental models", "Journey mapping"
Route to: user-research-and-validation.md
Add: Other skills once research informs design direction
Symptoms: "Mobile app", "iOS", "Android", "Touch interface", "Phone", "Tablet"
Route to:
Mobile-Specific Concerns:
Symptoms: "Web app", "Dashboard", "SaaS", "Data visualization", "Admin panel", "Responsive design"
Route to:
Web-Specific Concerns:
Symptoms: "Desktop app", "Electron", "Native application", "Multi-window", "Keyboard shortcuts"
Route to:
Desktop-Specific Concerns:
Symptoms: "Game", "HUD", "Menu system", "Game interface", "In-game UI", "Player experience"
Route to:
Game-Specific Concerns:
Load in order:
Load in order:
Load in order:
When designing documentation UX:
lyra/ux-designer/information-architecture (organize docs)muna/technical-writer/documentation-structure (content structure)muna/technical-writer/clarity-and-style (microcopy, UI text)Example: "Design documentation site navigation" → Load IA + documentation-structure
When the surface is a static documentation site or marketing page (not an interactive application):
lyra-site-designer — owns information architecture, HTML/CSS, design tokens, and developer-UX patterns for docs-first frameworks (Starlight / VitePress / Docusaurus).This pack stays in scope for: SaaS dashboards, web applications, mobile apps, desktop tools, game UI, AI / chat / agent surfaces.
When designing secure interfaces:
lyra/ux-designer/visual-design-foundations (secure feedback, error states)ordis/security-architect/threat-modeling (authentication UX threats)Example: "Design login with MFA" → Load interaction-patterns + threat-modeling
User Request
|
├─ "What is...?" / "Explain..." → ux-fundamentals
|
├─ "Review this design"
| ├─ General → visual-design + IA + accessibility
| └─ Specific concern → Relevant competency skill
| └─ Add platform extension if platform-specific
|
├─ "Design a [feature]"
| ├─ Research phase? → user-research-and-validation first
| └─ Design phase
| ├─ Identify competencies needed (visual, IA, interaction)
| ├─ Detect platform (mobile, web, desktop, game)
| └─ Load competency + platform extension
|
└─ Specific domain
├─ Visual → visual-design-foundations
├─ Navigation → information-architecture
├─ Interaction → interaction-design-patterns
├─ Accessibility → accessibility-and-inclusive-design
├─ AI / chatbot / agent / RAG / streaming → ai-experience-patterns
└─ Research → user-research-and-validation
Load: ux-fundamentals.md (teaches principles)
Load: visual-design + IA + accessibility + [platform-extension]
Load: Relevant competencies + [platform-extension]
Load: accessibility-and-inclusive-design.md (primary) Reference: visual-design (contrast), interaction-design (keyboard nav)
Load: information-architecture.md (primary) Add: user-research-and-validation (if testing/validation needed)
Focused expertise: Load only what's needed for the task Clear boundaries: Each skill has distinct responsibility Composable: Combine skills for complex scenarios Efficient: Avoid loading all 11 specialist sheets at once Explicit: User sees which skills are active
After routing, load the appropriate specialist skill for detailed guidance:
Cross-faction:
muna/technical-writer/* - Documentation UX and microcopyordis/security-architect/* - Security-aware interface designtools
Use when designing, implementing, or auditing an MCP (Model Context Protocol) server — tool API design, idempotency under agent retry, structured error envelopes agents can recover from, schema versioning across model drift, transport reliability (stdio / HTTP), output-shape and pagination discipline, and choosing between tools / resources / prompts / sampling. Also use when an MCP server's tools confuse agents, return unstructured errors, deadlock under concurrent calls, double-execute under retry, or lose state across reconnects. Do not use for general REST/GraphQL API design (use `/web-backend`), for client-side prompt engineering or tool-loop design (use `/llm-specialist`), for general in-process plugin architecture (use `/system-architect`), or for cryptographic-provenance audit trails (use `/audit-pipelines`).
development
Use when running **SQLite or DuckDB inside an application process** as the durable store — not as a development convenience but as the production database. Use when scaling an SQLite layer that worked at low concurrency and is now hitting SQLITE_BUSY, WAL bloat, lock contention, schema-migration ceremony, or correctness gaps under multi-process writers. Use when introducing DuckDB as an OLAP complement to an OLTP SQLite store, or when picking between the two for a new component. Pairs with `/web-backend` (the API surface above the DB) and `/audit-pipelines` (when the DB is also the audit trail). Do not load for server databases (Postgres, MySQL), key-value stores, or ORM choice in isolation.
development
Use when designing or critiquing the structure of a staged procedure — a wizard, configuration flow, troubleshooting tree, training curriculum, multi-stage approval pipeline, decision pipeline, or any decomposition of expert work into composable stages. Use for both producer work (build the decomposition) and critic work (audit a proposed decomposition). Use when reasoning about capacity, bottlenecks, or soundness of a procedural flow. Do not use for implementation-plan critique of code changes (use `/axiom-planning` instead), for execution-time dynamics (use `/simulation-foundations`), or for rendering an already-designed procedure as docs or UI (use `/technical-writer` or `/ux-designer`).
testing
Use when the user wants to draft fiction or creative nonfiction prose, get craft critique on prose they have written, or plan story structure, outline, or premise. Workshop-voiced. Three explicit modes (draft, critique, plan) and the router will refuse to begin work without a declared mode.