skills/ui-typography-spacing/SKILL.md
Typography hierarchy and spacing scale fallbacks. Yields to project design-dna when present.
npx skillsauth add adilkalam/orca ui-typography-spacingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design-DNA override: When a project has design-dna.json or equivalent design
tokens, those values override ALL defaults below.
| Element | Size | Weight | Line Height | Letter Spacing | |---------|------|--------|-------------|----------------| | H1 (page title) | 2.25-3rem | 700-800 | 1.1-1.2 | -0.02em | | H2 (section) | 1.5-2rem | 600-700 | 1.2-1.3 | -0.01em | | H3 (subsection) | 1.25-1.5rem | 600 | 1.3 | 0 | | Body | 1rem (16px min) | 400 | 1.5-1.6 | 0 | | Small/caption | 0.875rem | 400-500 | 1.4 | 0.01em | | Label | 0.75-0.875rem | 500-600 | 1.3 | 0.05em |
max-width: 65ch to 75ch)| Level | Desktop | Mobile | CSS Example |
|-------|---------|--------|-------------|
| Section-to-section | 64-96px | 48-64px | py-16 to py-24 / gap-16 to gap-24 |
| Component-to-component | 24-32px | 16-24px | gap-6 to gap-8 |
| Element-to-element | 8-16px | 8-16px | gap-2 to gap-4 |
Section gaps should be approximately 2x component gaps. Component gaps should be approximately 2x element gaps.
This creates natural visual grouping: elements within a component feel connected, components within a section feel related, sections feel distinct.
Example: If element gaps are 12px, component gaps should be ~24px, section gaps ~48-64px.
The same gap value MUST be used for the same element type across ALL sections of a page. If card-to-card spacing is 24px in one section, it must be 24px in every section.
content-media
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
development
Web UI quality rules: interactions, forms, loading, animations, layout, content, performance, accessibility, design. Apply to all web UI work. Adapted from Vercel Design Guidelines.
testing
MANDATORY protocol enforcing knowledge check before EVERY response - prevents explaining systems without reading docs, claiming without verification, and ignoring auto-loaded context
development
New page checklist: metadata, loading/error states, component states, form completeness, mobile-first, SEO, API routes. Use when creating or auditing Next.js pages.