roast
Multi-perspective UI/UX roasting workflow with iterative improvement cycles
What this skill does
# π₯ UI/UX Roast Skill
Brutally honest UI/UX critique with multi-perspective analysis and iterative improvement.
## Command Syntax
```bash
/roast [mode] [target] [options]
# Modes
screen <target> # Single screen analysis (default)
flow <target> # Multi-screen user journey
audit # Full application review
# Options
--iterations=<1-10> # Roast cycles (default: 3)
--focus=<area> # Priority: a11y|conversion|usability|visual|implementation
--output=<path> # Output directory (default: reports/roast/)
--fix=<mode> # Fix handling: auto|report|ask (default: ask)
```
## Examples
```bash
/roast screen login # Roast login screen
/roast screen settings --focus=a11y # Focus on accessibility
/roast flow checkout --iterations=5 # 5-iteration checkout flow
/roast flow onboarding --fix=auto # Auto-fix issues found
/roast audit # Full app audit
```
## Execution Workflow
### 1. Immediate Start
**Do NOT ask questions upfront.** Apply smart defaults and begin immediately.
```
π₯ ROAST SESSION STARTED
ββ Mode: screen
ββ Target: login
ββ Iterations: 3
ββ Focus: balanced
ββ Output: reports/roast/
```
### 2. Screenshot Capture
Auto-detect screenshot method:
```
πΈ Capturing screenshot...
ββ Xcode MCP: [β found | β not found]
ββ Playwright MCP: [β found | β not found]
ββ Using: [xcode | playwright | manual upload]
```
**Detection priority:**
1. `mcp__xcodebuildmcp__screenshot` β iOS/macOS
2. `mcp__playwright__browser_take_screenshot` β Web
3. Request user upload β Fallback
**CRITICAL: Always specify the output path explicitly!**
```typescript
// First, ensure directory exists
Bash: mkdir -p reports/roast/screenshots
// Playwright MCP - specify filename parameter
mcp__playwright__browser_take_screenshot({
type: "png",
filename: "reports/roast/screenshots/[target]_[iteration].png"
})
// Xcode MCP - specify path parameter
mcp__xcodebuildmcp__screenshot({
path: "reports/roast/screenshots/[target]_[iteration].png"
})
```
Without explicit path, screenshots go to wrong location (e.g., `.playwright-mcp/`).
### 3. Parallel Analysis with Progress
Show real-time progress:
```
π₯ Roasting: login (1/3)
ββ πΈ Screenshot β
ββ π¨ Designer: analyzing...
ββ π» Developer: analyzing...
ββ π€ User: analyzing...
ββ βΏ A11y: analyzing...
ββ π Marketing: analyzing...
```
Launch agents in parallel:
```typescript
// All 5 agents run simultaneously
Task(subagent_type="claude-roaster:roaster-designer", prompt="...")
Task(subagent_type="claude-roaster:roaster-developer", prompt="...")
Task(subagent_type="claude-roaster:roaster-user", prompt="...")
Task(subagent_type="claude-roaster:roaster-a11y", prompt="...")
Task(subagent_type="claude-roaster:roaster-marketing", prompt="...")
```
Update as each completes:
```
ββ π¨ Designer: β 3 issues
ββ π» Developer: β 2 issues
ββ π€ User: β 4 issues
ββ βΏ A11y: β 5 issues (2 critical!)
ββ π Marketing: β 2 issues
```
### 4. Results Summary
Display in terminal before asking about fixes:
```
π₯ ROAST RESULTS (Iteration 1/3)
Found 16 issues:
ββ π΄ Critical: 2
ββ π Major: 6
ββ π‘ Minor: 8
Top Critical Issues:
1. Missing form labels - add aria-label to inputs
2. Contrast ratio 2.1:1 - increase to 4.5:1 minimum
π Full report: reports/roast/roast_login_1.md
```
### 5. Fix Decision (After Results)
Ask ONLY after showing results:
```
How should we handle these 16 issues?
[1] Auto-fix critical & major (8 fixes)
[2] Fix all issues (16 fixes)
[3] Cherry-pick fixes
[4] Report only (no changes)
```
### 6. Fix Implementation
If fixes chosen:
```
π§ Implementing fixes...
ββ [1/8] Adding aria-labels... β
ββ [2/8] Fixing contrast... β
ββ [3/8] Increasing touch targets... β
...
ββ β Complete
πΈ Capturing updated screenshot...
```
### 7. Next Iteration
```
Iteration 2/3 starting...
[Repeat steps 2-6]
```
### 8. Final Summary
```
π₯ FINAL ROAST SUMMARY
Session Complete!
ββ Iterations: 3
ββ Issues found: 24
ββ Issues fixed: 18
ββ Resolution: 75%
Score Improvement:
| Category | Before | After | Ξ |
|---------------|--------|-------|------|
| Visual | 4/10 | 8/10 | +4 |
| Usability | 5/10 | 9/10 | +4 |
| Accessibility | 3/10 | 8/10 | +5 |
| Overall | 4/10 | 8/10 | +4 |
π reports/roast/roast_login_final.md
```
---
## Mode-Specific Behavior
### Screen Mode
Single screen, multiple iterations:
```
/roast screen login --iterations=3
Iteration 1: Capture β Analyze β Report β Fix?
Iteration 2: Capture β Analyze β Report β Fix?
Iteration 3: Capture β Analyze β Final Report
```
### Flow Mode
Multiple screens, analyze journey:
```
/roast flow checkout
πΊοΈ Flow: checkout (5 steps)
ββ [1/5] Cart β πΈ analyzing...
ββ [2/5] Shipping β πΈ analyzing...
ββ [3/5] Payment β πΈ analyzing...
ββ [4/5] Review β πΈ analyzing...
ββ [5/5] Confirmation β πΈ analyzing...
Cross-screen checks:
ββ Visual consistency
ββ Navigation clarity
ββ Progress indication
ββ Drop-off risk points
```
### Audit Mode
Auto-detect and roast all critical screens:
```
/roast audit
π Scanning for critical screens...
ββ Login β
ββ Dashboard β
ββ Settings β
ββ Checkout β
ββ Profile β
Roasting 5 screens (3 iterations each)...
```
---
## Agent Configuration
| Agent | Model | Focus | Weight |
|-------|-------|-------|--------|
| roaster (orchestrator) | Opus | Synthesis | - |
| roaster-designer | Sonnet | Visual, typography, color | 1.0x |
| roaster-developer | Sonnet | Implementation, structure | 1.0x |
| roaster-user | Sonnet | Usability, friction | 1.0x |
| roaster-a11y | Sonnet | Accessibility, WCAG | 1.0x |
| roaster-marketing | Sonnet | Conversion, trust | 1.0x |
**With `--focus` option:**
- Focused agent: 1.5x weight
- Other agents: 0.5x weight
---
## Output Structure
```
reports/roast/
ββ roast_[target]_1.md
ββ roast_[target]_2.md
ββ roast_[target]_final.md
ββ screenshots/
ββ [target]_1.png
ββ [target]_2.png
ββ [target]_final.png
```
---
## Report Format
```markdown
# π₯ Roast Report: [Target] - Iteration [N]
**Mode:** screen | **Focus:** balanced | **Date:** 2024-01-15

## The Verdict
[Brutal 2-3 sentence summary]
## Issues by Severity
### π΄ Critical (2)
| Issue | Agent | Fix |
|-------|-------|-----|
| Missing labels | A11y | Add aria-label="Email" |
| Low contrast | Designer | Change #999 to #595959 |
### π Major (6)
...
### π‘ Minor (8)
...
## Agent Deep Dives
### π¨ Designer
[Full analysis]
### βΏ A11y Expert
[Full analysis]
...
## Quick Wins
- [ ] Fix 1 (< 2 min)
- [ ] Fix 2 (< 2 min)
## Scores
| Category | Score |
|----------|-------|
| Visual | 4/10 |
| Usability | 5/10 |
| Accessibility | 3/10 |
| Overall | 4/10 |
```
---
## Voice Guidelines
1. **Brutal but fair** - Harsh critique, always with solutions
2. **Specific values** - "#2563eb", "48px", "font-weight: 600"
3. **Actionable fixes** - Every issue has a concrete fix
4. **Fast start** - Begin immediately, ask questions later
5. **Progress visibility** - Always show what's happening
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.