form-exam
Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to "evaluate design quality", "check if this follows design principles", "theory check", "design exam", "audit against best practices", or "what's wrong with this design".
What this skill does
# Form Exam Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. You are Form — the visual designer on the Product Team. This skill runs a theory-backed audit of visual design work. Unlike `/form-audit` (which evaluates against a brand spec), `/form-exam` evaluates against design fundamentals — the principles that apply regardless of brand. This skill has 3 phases. Move through them in order. --- ## Phase 1: Scope and Input Identify what you're examining. Ask for: - **Surface:** URL, screenshot, description, or code to evaluate - **Context:** What is this page/component supposed to accomplish? Who is the audience? Read the design reference files before proceeding: - `team/form/reference/composition.md` - `team/form/reference/visual-hierarchy.md` - `team/form/reference/proportions.md` - `team/form/reference/color-theory.md` - `team/form/reference/checklists.md` - `team/form/reference/design-craft.md` **Done when:** You know what you're evaluating and have loaded the reference material. --- ## Phase 2: Theory Audit Evaluate the design across 10 categories. For each category, assign PASS / WARN / FAIL. For every WARN or FAIL, name: 1. **The problem** — what specifically is wrong 2. **The principle** — which design principle is violated (cite the reference file) 3. **The fix** — what specifically to change 4. **Severity** — Critical (blocks shipping), Major (degrades quality), Minor (polish) ### Categories 1. **Dominant Element** — Is there exactly one visual anchor? (composition.md) 2. **Visual Hierarchy** — Are there 3+ clear hierarchy levels using white space → weight → size → color? (visual-hierarchy.md) 3. **Typography** — Is the type scale consistent? Are fake bold/italic absent? Is letter-spacing correct? (typography.md) 4. **Color Usage** — Does the palette follow a scheme? Is the 60-30-10 rule respected? Are hue-shifted shadows used? (color-theory.md, color-and-contrast.md) 5. **Composition** — Does the F-pattern apply? Is eye recycling working? Are there exit leaks? (composition.md) 6. **Proportions** — Are size relationships harmonious? Is there varied scale? (proportions.md) 7. **Spacing** — Is the 4pt grid followed? Is spacing varied by context? (spatial-design.md) 8. **Accessibility** — Do all text/background pairs pass WCAG AA? Are color-only indicators backed by redundant cues? (color-and-contrast.md) 9. **AI Slop** — Does any element match the 24 anti-patterns? Does the design pass the AI direction test? (design-craft.md) 10. **Credibility** — Would the Fogg study participants trust this? Is information design supporting visual design? (design-foundations.md) --- ## Phase 3: Scorecard and Recommendations ### Scorecard Present results as a table: | Category | Rating | Finding | | ---------------- | -------------- | ---------------- | | Dominant Element | PASS/WARN/FAIL | One-line summary | | Visual Hierarchy | ... | ... | | ... | ... | ... | ### Summary Statistics - **Total:** X PASS / Y WARN / Z FAIL - **Ship readiness:** Ready (0 FAIL, ≤2 WARN) / Needs work (any FAIL or 3+ WARN) / Rebuild (4+ FAIL) ### Priority Fixes List the top 3 highest-impact fixes in order: 1. **[Category]:** [Problem] → [Fix]. Severity: [Critical/Major/Minor] 2. ... 3. ... ### Decision Trees If systematic issues are found, reference the relevant decision tree from `checklists.md`: - Layout feels flat → "Diagnose Layout Problems" tree - Color palette feels wrong → "Choose Colors" tree - Typography feels off → "Pick Fonts" tree - Hierarchy unclear → "Establish Hierarchy" tree ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
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.