design-audit
Use when reviewing frontend design quality without a reference. Identifies UX issues, accessibility problems, and visual inconsistencies with actionable fix suggestions.
What this skill does
# Design Audit
## Overview
Quickly identify design issues and provide actionable suggestions for improvement without needing a reference design.
**Core principle:** Good design follows patterns. Deviations from patterns are often bugs.
## When to Use
Use this skill when:
- Reviewing UI during development
- Quick sanity check before PR
- User asks "what's wrong with this design?"
- Accessibility review needed
- User wants "quick feedback on the UI"
- Polishing before demo/launch
## Required Inputs
1. **Screenshot or URL** of the frontend to audit
2. **Context** (optional) - Target audience, brand guidelines, purpose
**Announce:** "I'll perform a quick design audit using design-audit skill."
## Audit Process
### Phase 1: First Impression (2 seconds)
Capture gut reaction:
- What draws attention first?
- Does hierarchy feel clear?
- Any elements feel "off"?
- Professional or amateur feel?
### Phase 2: Systematic Scan
Check each category in order:
#### 1. Visual Hierarchy
- [ ] Clear primary action/CTA
- [ ] Heading levels make sense
- [ ] Important info is prominent
- [ ] Secondary items subdued
#### 2. Spacing & Alignment
- [ ] Consistent margins/padding
- [ ] Grid alignment
- [ ] Breathing room between elements
- [ ] No orphaned elements
#### 3. Typography
- [ ] Max 2-3 font families
- [ ] Readable font sizes (min 14px body)
- [ ] Sufficient line-height (1.4-1.6)
- [ ] Proper font weights
#### 4. Color & Contrast
- [ ] WCAG AA contrast (4.5:1 text, 3:1 UI)
- [ ] Consistent color palette
- [ ] Meaningful color usage
- [ ] Not relying on color alone
#### 5. Components
- [ ] Buttons look clickable
- [ ] Interactive states clear
- [ ] Forms properly labeled
- [ ] Icons sized consistently
#### 6. Accessibility
- [ ] Focus indicators visible
- [ ] Touch targets 44px+
- [ ] Alt text would make sense
- [ ] Keyboard navigation logical
#### 7. Polish
- [ ] No pixelated images
- [ ] Consistent border radius
- [ ] Shadows consistent
- [ ] No alignment jitter
### Phase 3: Generate Audit Report
**Output format:**
```markdown
## Quick Design Audit
### Overall Score: [X/10]
Brief 1-line summary
### Critical Issues (Fix Now)
1. **[Issue]** - [Location]
- Problem: [Description]
- Fix: [Specific actionable suggestion]
- Impact: [Why this matters]
### High Priority Issues (Should Fix)
1. **[Issue]** - [Location]
- Problem: [Description]
- Fix: [Specific actionable suggestion]
### Medium Priority Issues (Consider Fixing)
1. **[Issue]** - [Location]
- Problem: [Description]
- Fix: [Specific actionable suggestion]
### Low Priority Polish (Nice to Have)
1. **[Issue]** - [Location]
- Suggestion: [Improvement idea]
### What's Working Well
- [Positive observation]
- [Another strength]
```
## Issue Priority Matrix
| Impact \ Effort | Low Effort | High Effort |
|-----------------|------------|-------------|
| **High Impact** | Fix Now | Plan Soon |
| **Low Impact** | Quick Win | Backlog |
## Common Issues & Fixes
### Spacing Issues
```css
/* Problem: Inconsistent spacing */
/* Fix: Use spacing scale */
--space-1: 4px;
--space-2: 8px;
--space-3: 16px;
--space-4: 24px;
--space-5: 32px;
```
### Typography Issues
```css
/* Problem: Poor readability */
/* Fix: */
body {
font-size: 16px; /* Not 14px */
line-height: 1.5; /* Not 1.2 */
max-width: 65ch; /* Limit line length */
}
```
### Color Contrast
```css
/* Problem: Low contrast */
/* Fix: Use contrast checker, aim for 4.5:1+ */
/* Bad: #888 on #fff (3.5:1) */
/* Good: #666 on #fff (5.7:1) */
```
### Button States
```css
/* Problem: No hover/focus states */
/* Fix: */
button:hover { background: var(--primary-dark); }
button:focus { outline: 2px solid var(--focus-ring); }
button:active { transform: scale(0.98); }
```
## Severity Definitions
| Severity | Criteria | Examples |
|----------|----------|----------|
| **Critical** | Blocks usage or accessibility | No focus states, contrast < 3:1, touch targets < 30px |
| **High** | Impacts usability significantly | Unclear CTA, confusing hierarchy, inconsistent patterns |
| **Medium** | Noticeable but functional | Minor spacing issues, suboptimal typography |
| **Low** | Polish items | Pixel alignment, shadow refinement |
## Output Actions
After audit, offer:
1. **Generate CSS fixes** - Code snippets to fix issues
2. **Create ticket list** - Formatted for issue tracker
3. **Deep dive area** - Detailed analysis of specific section
4. **Full report** - Use `design-report` for comprehensive analysis
## Red Flags
Stop and clarify if:
- Image is blurry or low resolution
- Cannot determine intended audience
- Multiple distinct UI patterns present
- Unclear what constitutes "done"
## Integration
**Related skills:**
- `design-compare` - When you have a reference design
- `design-report` - For deep expert analysis
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.