oliverv/caro / .agents/skills/oma-design
oma-design
UnverifiedDefine or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.1 KB |
| reference/accessibility.md | markdown | 4.4 KB |
| reference/color-and-contrast.md | markdown | 3.7 KB |
| reference/component-patterns.md | markdown | 5.7 KB |
| reference/motion-design.md | markdown | 7.9 KB |
| reference/responsive-design.md | markdown | 3.6 KB |
| reference/shader-and-3d.md | markdown | 5.0 KB |
| reference/spatial-design.md | markdown | 2.8 KB |
| reference/typography.md | markdown | 2.6 KB |
| reference/visual-hierarchy.md | markdown | 9.6 KB |
| resources/anti-patterns.md | markdown | 8.4 KB |
| resources/asset-strategy.md | markdown | 3.0 KB |
| resources/checklist.md | markdown | 5.6 KB |
| resources/design-md-spec.md | markdown | 8.3 KB |
| resources/design-tokens.md | markdown | 3.9 KB |
| resources/error-playbook.md | markdown | 3.9 KB |
| resources/execution-protocol.md | markdown | 14.5 KB |
| resources/getdesign-fetcher.md | markdown | 13.2 KB |
| resources/prompt-enhancement.md | markdown | 9.2 KB |
| resources/redesign-protocol.md | markdown | 3.7 KB |
| resources/stitch-integration.md | markdown | 3.8 KB |
resources/checklist.md
View on GitHub# Design Audit Checklist
## 1. Responsive (MANDATORY, run first)
- [ ] All sections render correctly at 375px width
- [ ] No horizontal scroll at any breakpoint
- [ ] Touch targets >= 44x44pt on mobile
- [ ] Text readable without zooming on mobile (min 16px body)
- [ ] Images/videos scale or have mobile alternatives
- [ ] Navigation collapses appropriately (hamburger/drawer)
- [ ] Buttons stack vertically on mobile if needed (flex-col)
- [ ] No fixed-width containers causing overflow
## 2. WCAG 2.2 Accessibility
- [ ] Text contrast >= 4.5:1 AA (normal text)
- [ ] Large text contrast >= 3:1 AA (18px bold / 24px+)
- [ ] UI component contrast >= 3:1 against adjacent colors
- [ ] Focus indicators visible with >= 3:1 contrast
- [ ] All images have appropriate alt text (decorative: alt="")
- [ ] Semantic HTML landmarks (header, nav, main, footer)
- [ ] Sequential heading hierarchy (h1 → h2 → h3, no skips)
- [ ] One h1 per page
- [ ] prefers-reduced-motion respected for all animations
- [ ] All interactive elements keyboard-accessible
- [ ] Skip-to-content link present
- [ ] aria-label on icon-only buttons
- [ ] No content conveyed by color alone
## 3. Nielsen's 10 Heuristics
- [ ] Visibility of system status (loading, progress, feedback)
- [ ] Match between system and real world (familiar language, conventions)
- [ ] User control and freedom (undo, back, escape, close)
- [ ] Consistency and standards (same patterns throughout)
- [ ] Error prevention (confirmations for destructive actions)
- [ ] Recognition rather than recall (visible options, no memorization)
- [ ] Flexibility and efficiency (shortcuts for expert users)
- [ ] Aesthetic and minimalist design (no unnecessary elements)
- [ ] Help users recognize and recover from errors (clear messages)
- [ ] Help and documentation (if needed, searchable and task-oriented)
## 4. AI Slop Check
- [ ] Passes the "AI made this" test (would a human designer be proud?)
- [ ] No purple gradient backgrounds
- [ ] No Inter-only or Geist-only typography without justification
- [ ] No triple-nested cards
- [ ] No bounce easing on all animations
- [ ] No generic hero with 3-metric stats row
- [ ] No gradient + glassmorphism + blur triple combo
- [ ] No gradient orbs/blobs as primary decoration
- [ ] Texture/noise preferred over plain gradients where applicable
- [ ] Design reflects project-specific context, not a generic template
- [ ] Custom fonts justified by brand needs, not used by default
## 5. Design System Consistency
- [ ] All colors from the defined palette (no hardcoded hex outside system)
- [ ] All spacing from 8px grid scale (4, 8, 12, 16, 24, 32, 48, 64, 96, 128)
- [ ] Typography uses the defined type scale (no arbitrary font sizes)
- [ ] Component variants consistent (same border-radius, shadow, border treatment)
- [ ] Dark/light theme tokens defined if applicable
- [ ] CSS custom properties used for all design tokens
- [ ] Tailwind config extends theme correctly (no arbitrary values in templates)
## 6. Mechanical Checks (countable — verify by counting/grep, not judgment)
These checks are deliberately mechanical so an agent can self-verify them
deterministically. A failed count is a failed audit; fix before handoff.
### Consistency locks
- [ ] Accent lock: ONE accent color, used identically across all sections (no blue CTA appearing on a warm-grey page in section 7)
- [ ] Radius lock: ONE corner-radius system (all-sharp / all-soft / all-pill), or a documented mixed rule applied everywhere
- [ ] Theme lock: ONE theme (light, dark, or auto) for the whole page; no single section inverting mid-scroll
### Layout counts
- [ ] Eyebrow count: micro-labels (uppercase + letter-spacing above section headlines) <= ceil(sectionCount / 3); hero counts as one
- [ ] Layout-family repetition: no layout family (3-col cards, image+text split, full-width quote, bento...) used for more than one section; a page of 8 sections uses >= 4 distinct families
- [ ] Zigzag cap: max 2 consecutive image+text split sections; the 3rd consecutive one fails
- [ ] Marquee: max 1 horizontal marquee per page
- [ ] Bento cell count: N items → exactly N cells; no empty filler tiles
- [ ] Long lists (> 5 items): grouped chunks / card grid / tabs / carousel — not a default `<ul>` with a hairline under every row
### Hero discipline
- [ ] Hero fits the initial viewport: headline <= 2 lines desktop, subtext <= 20 words, primary CTA visible without scroll
- [ ] Hero stack: max 4 text elements (eyebrow OR brand strip, headline, subtext, CTAs); no trust micro-strip / pricing teaser / tagline-under-CTAs inside the hero
- [ ] Logo wall lives in its own section BELOW the hero, never inside it
### CTA and copy counts
- [ ] ZERO em-dashes: `grep -rn '—' <output files>` returns nothing in visible strings; en-dash (`–`) not used as a separator either (hyphen only)
- [ ] No CTA label wraps to 2+ lines at desktop (primary CTA <= 3 words)
- [ ] One label per CTA intent: no "Get in touch" + "Let's talk" (same contact intent) coexisting on one page; same for signup and portfolio intents
- [ ] Every CTA/button text passes WCAG AA contrast against its own background (no white-on-white, no ghost button vanishing over photos)
### Navigation
- [ ] Nav renders on a single line at desktop (condense labels or use hamburger if not)
- [ ] Nav height <= 80px desktop
### Typography & icons
- [ ] Inter used only with an explicit justification (user asked for neutral/Linear-style, or public-sector/a11y-first brief) — never by reflex
- [ ] ONE icon family per project: grep icon imports; all come from a single library, consistent strokeWidth
- [ ] lucide-react present only if explicitly requested or already a project dependency
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |