Editorial
Skill0 starsChanged 5 months agoMITView on GitHub
Use when building or styling a UI in the Editorial aesthetic — A magazine-grade design system that makes typography the hero, pairing structured grids with generous whitespace and confident headlines. For Claude Code, Cursor, and Codex.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- futhr/futhrtheir own version, first seen Oct 27, 2026
- zdresearch/p3ntheir own version, first seen Oct 25, 2026
- lachinovedhem/standards-mcptheir own version, first seen Oct 11, 2026
- SkotAlexsander/skillstheir own version, first seen Sep 16, 2026
- matheusflorindo32/apex-elite-frameworktheir own version, first seen Jul 19, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- bergside/awesome-design-skills★ 2.9ksame name
- zdresearch/p3n★ 5same name
- SkotAlexsander/skills★ 1same name
- futhr/futhr★ 0same name
- hemal08ce094/DesignSkillsSwiftUI★ 0same name
- lachinovedhem/standards-mcp★ 0same name
- matheusflorindo32/apex-elite-framework★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- BentoSkill
- ClaymorphismSkill
- DashboardSkill
- GlassmorphismSkill
- MinimalSkill
- NeobrutalismSkill
- NeonSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Respect the measure: Keep body text around 60-72 characters per line so reading never strains.
- Distinctive: line 53
Cards: no shadow, no heavy border — separated by whitespace and a top hairline rule, with a kicker, serif headline, and muted deck.
- Distinctive: line 68
Avoid bouncy or playful easing — everything should feel composed, like turning a page.
- Very specific: line 91
Cursor: add the contents to a .cursor/rules/<name>.mdc file.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Editorial
Editorial treats the page like a printed spread. Type is not decoration here — it is the architecture. The style leans on a refined serif voice, a warm paper background, and disciplined grids so that words breathe and imagery feels curated rather than crammed.
Reach for Editorial when the content itself is the product: essays, journalism, brand stories, and any interface where reading is the primary act. The result should feel like a beautifully art-directed magazine that happens to live on a screen — calm, confident, and unmistakably premium.
Design principles
- Lead with typography. Headlines do the heavy lifting; everything else stays quiet and supportive.
- Respect the measure. Keep body text around 60-72 characters per line so reading never strains.
- Use rules, not boxes. Hairline dividers and column gutters create structure without heavy containers or drop shadows.
- Restrain color. A single warm accent marks links and emphasis; the rest is ink on paper.
- Honor the grid, then break it intentionally for a single dramatic image or pull quote.
- Whitespace is content. Generous vertical rhythm signals quality and confidence.
Color
The foundation is a warm paper background (#FAF8F3) with near-black ink (#1A1714) for text, which reads softer and more premium than pure black on white.
Surfaces such as cards or callouts lift to pure white (#FFFFFF) to feel like an inset clipping pasted onto the page. The rust accent (#B23A2E) is used sparingly — links, active states, pull-quote marks — and never as a flood of color. Muted ink (#6E665B) carries metadata, captions, and kickers, while borders are a faint sand (#E4DFD4) used only as 1px rules.
Light mode is the home of this style: paper, ink, and a single warm accent. Dark mode inverts to a deep espresso background (#16110D) with parchment text (#EDE7DC); warm the accent slightly to #D26352 so it stays legible against the dark field, and keep rules at #33291F.
Typography
A high-contrast display serif carries every heading, set in tight tracking (-0.02em) at large sizes for that printed-masthead authority. Body copy uses a readable text serif at 18-20px with line-height 1.7 for long-form comfort.
- Headlines: display serif, bold (700), 56-96px, -0.02em tracking.
- Subheads / decks: body serif italic, 22-28px, regular weight, muted ink.
- Body: body serif, 18-20px, line-height 1.7, weight 400.
- Kickers & labels: 12-13px uppercase, +0.08em tracking, muted ink, often in small caps.
- Emphasis: real italics and a single medium (500) weight — never faux-bold body.
Weights stay disciplined so the page never feels noisy: regular for body, medium for emphasis, and one bold reserved for top-level headlines.
Layout & spacing
Work on a 12-column grid with a comfortable 24px gutter and a max content width around 1200px, while the reading column itself caps near 680px.
Spacing follows an 8px base with a strong vertical rhythm — section breaks get 64-96px of air. Density is deliberately low; never let elements touch. Captions and footnotes align to the column edge to reinforce the grid, and full-bleed images are welcome as a counterpoint to the tight reading column.
Components
- Buttons: solid rust fill with white serif label and a 2px radius for primary; secondary is a text link with an animated underline.
- Inputs: borderless or single underline rule, with a focus state that thickens the underline to the rust accent.
- Cards: no shadow, no heavy border — separated by whitespace and a top hairline rule, with a kicker, serif headline, and muted deck.
- Navigation: a slim top bar with the masthead wordmark centered or left, links in small-caps, and a thin bottom rule rather than a shadow.
- Modals & overlays: paper-colored sheets centered with ample padding, a thin rule header, and a backdrop of rgba(26,23,20,0.4).
- Tables: ruled rows with no vertical lines, generous cell padding, and small-caps column headers in muted ink.
- Badges: understated — small-caps text with a hairline outline or a faint sand background, never loud pills.
- Pull quotes: large italic serif, indented, with a rust vertical rule or oversized opening quotation mark.
Motion
Motion is subtle and print-respectful — nothing should feel like a web app showing off.
- Links reveal an underline that wipes in over 200ms with an ease-out curve.
- Page and section transitions use gentle 300ms opacity-and-rise fades (8-12px translate).
- Hover states warm color slightly rather than jumping; presses dim to ~92% opacity.
Avoid bouncy or playful easing — everything should feel composed, like turning a page.
Accessibility
- Ink on paper (
#1A1714on#FAF8F3) exceeds 12:1 contrast; muted text stays above 4.5:1 for body sizes. - The rust accent on paper clears AA for large text and UI — always pair links with an underline so they never rely on color alone.
- Focus states use a visible 2px rust outline with a 2px offset, and are never removed.
- Respect
prefers-reduced-motionby disabling rise/fade transitions and keeping instant state changes. - Maintain a minimum 16px body size and ensure all interactive targets are at least 44x44px.
Meets WCAG 2.2 AA across text contrast, focus visibility, and target size.
Example prompt
Article layout
Build a long-form article page in the Editorial style: a large serif drop-headline, a deck subtitle in muted ink, a single-column measure of ~68 characters, and a thin rule separating sections. Use the warm paper background and reserve the rust accent for pull quotes and links only.
Install
Drop the folder into your agent's skills directory, or paste this file's contents into your prompt / rules file:
- Claude Code: copy
skills/<name>/SKILL.mdinto.claude/skills/<name>/SKILL.md(project) or~/.claude/skills/(personal). - Cursor: add the contents to a
.cursor/rules/<name>.mdcfile. - Codex / other agents: paste into your
AGENTS.mdor system prompt.
Part of staqd — a library of 67 design-system skills for Claude, Cursor & Codex. This repo holds the 8 free skills; the full library lives at staqd.ai/skills.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

