ux-design
UX Design — Flows, Structure & Interaction
Design how users move through the app, find what they need, and accomplish tasks with minimal friction. This skill covers the structural and behavioral layer of UX — information architecture, navigation, user flows, interaction patterns, and error handling. For visual design (colors, typography, layout), see the beautify and ui-patterns skills. For onboarding flows, see ONBOARDING.md. For accessibility implementation, see ACCESSIBILITY.md.
Information Architecture
The goal of IA is that users never have to think about where to find something. Navigation should match the user's mental model, not the database schema or org chart.
Core Principles
- Flat > deep. Every additional level of nesting loses users. Aim for max 2 levels of hierarchy in navigation.
- Labels are architecture. Vague labels cause wrong turns. If a label needs explanation, change the label.
- Group by user task, not data type. "Marketing Assets" beats "Images | Documents | Videos." Users think in workflows, not file formats.
- 5-9 items per group (Miller's Law). More than 9 items in a nav section means it needs restructuring.
- Most-used items first. Alphabetical ordering is lazy architecture — prioritize by frequency of use.
URL Structure
URLs must mirror the information architecture:
More from whawkinsiv/claude-code-skills
accounting
Use this skill when the user needs to set up bookkeeping, track revenue and expenses, prepare for taxes, choose accounting software, understand SaaS revenue recognition, or manage the financial operations of their bootstrapped business. Covers bookkeeping setup, tax preparation, accounting tools, and financial hygiene for solo founders.
367hiring
Use this skill when the user needs to hire a developer, find a technical contractor, vet engineering talent, manage freelancers, write a job brief, decide between hiring and contracting, or bring on their first technical team member. Also use when the user says 'I need a developer,' 'should I hire someone,' 'how do I find a contractor,' 'I need technical help I can't do myself,' or 'AI keeps getting this wrong, I need a human.' Covers contractor sourcing, vetting, management, and the founder-developer working relationship for non-technical founders.
21market-research
Use this skill when the user needs to size a market, analyze competitors, calculate TAM/SAM/SOM, or validate a business idea. Covers market sizing, competitive analysis frameworks, napkin math, and bottom-up revenue estimation.
19payments
Use this skill when the user needs to set up Stripe, implement subscriptions, handle billing, configure payment plans, manage failed payments, deal with refunds, set up tax collection, or troubleshoot payment issues. Covers Stripe configuration, subscription lifecycle, dunning, tax compliance, and billing operations for bootstrapped SaaS.
18copywriting
Use this skill when the user needs to write headlines, CTAs, button text, error messages, onboarding copy, or any UI text. Also use when the user says 'write copy for,' 'what should this say,' 'help me with the wording,' or is building any page or component that needs text. Covers headline formulas, microcopy best practices, benefit-driven copy, and SaaS writing style.
17legal
Use this skill when the user needs to form a business entity, choose between LLC and C-Corp, create Terms of Service, write a Privacy Policy, or handle legal compliance. Covers entity selection, legal documents, contracts, and compliance for solo-founded SaaS.
17