editorial

Start by defining tokens for typography, color, and spacing before writing component rules. This Skill provides a Gelasio-based type scale, an 8pt baseline grid, and a structured workflow covering anatomy, states, and accessibility criteria.

This Skill uses a 14/16/18/24/32/40 scale with Gelasio as the primary and display font and Ubuntu Mono for labels. Weights from 100 to 900 are supported, giving flexibility for headings, body text, and captions.

Yes, the guidelines target WCAG 2.2 AA with keyboard-first interactions, visible focus states, semantic HTML before ARIA, reduced-motion support, and 44px minimum touch targets. Every accessibility statement must be testable in implementation.

Define required states including default, hover, focus-visible, active, disabled, loading, and error for each component. Describe keyboard, pointer, and touch interactions, and anchor every rule to a specific token, threshold, or example.

Editorial layouts with serif typography suit long-form reading and content-heavy pages. They are less appropriate for dense data dashboards or utility-focused tools where compact sans-serif interfaces and tighter information density matter more.