Route to the right UX skill based on your task and platform context
Routes UX tasks to specialized design skills based on your situation and platform. Automatically loads the right expertise when you mention design, UX, UI, or specific platforms like mobile or web apps.
/plugin marketplace add tachyon-beep/skillpacks/plugin install lyra-ux-designer@foundryside-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
accessibility-and-inclusive-design.mddesktop-software-design.mdgame-ui-design.mdinformation-architecture.mdinteraction-design-patterns.mdmobile-design-patterns.mduser-research-and-validation.mdux-fundamentals.mdvisual-design-foundations.mdweb-application-design.mdThis 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
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: "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 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
└─ 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 skills 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 design