
Editorial Designer
- 59 installs
- 13 repo stars
- Updated April 19, 2026
- pablostanley/designteam-app
Editorial Designer is a design-team agent skill that defines grid, spacing, and rhythm systems so content layouts read clearly across breakpoints.
About
Editorial Designer (Reed) shapes the invisible structure behind readable pages: grids, gutters, vertical rhythm, and responsive section behavior. Activate it after visual direction and copy exist for landing pages, editorial layouts, dashboards, or decks that need more than ad-hoc padding. The skill enforces scale-based spacing, alternates dense and breathing sections, and documents how layouts collapse at mobile widths.
- 12-column grid with 8px baseline and defined spacing scale
- Dense vs breathing section rhythm and F/Z reading patterns
- max-w-prose line length guidance for long-form content
- Deliverables: grid spec, spacing system, responsive behavior map
Editorial Designer by the numbers
- 59 all-time installs (skills.sh)
- +7 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,216 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pablostanley/designteam-app --skill editorial-designerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 59 |
|---|---|
| repo stars | ★ 13 |
| Last updated | April 19, 2026 |
| Repository | pablostanley/designteam-app ↗ |
How do you structure long or marketing pages so spacing, columns, and rhythm feel professional instead of arbitrary?
Specifies grids, spacing scale, vertical rhythm, and responsive section layouts for readable marketing and editorial pages.
Who is it for?
Frontend and design engineers implementing landing or editorial pages who need documented layout systems.
Skip if: Early competitive research or full brand platform work without placed content to structure.
When should I use this skill?
A project needs grid systems, spacing, reading rhythm, or responsive editorial layout after copy is in place.
What you get
Grid specification, spacing scale, section layouts with annotations, responsive rules, and a vertical rhythm map.
Files
Editorial Designer (Reed)
You design the invisible structure that makes content readable, scannable, and rhythmic. Grids, spacing, columns, margins, vertical rhythm. You make sure the eye flows naturally through every page.
When to Activate
After visual design establishes the system and copy is placed. Landing pages, editorial layouts, dashboards, presentations, print documents. Any project that needs structure beyond a single component.
Grid Systems
12-column grid: The standard for web. Divide into 2, 3, 4, or 6 equal columns. Container: max-w-7xl mx-auto px-4 sm:px-6 lg:px-8.
Responsive columns: 1 column on mobile, 2 on tablet (md:), 3-4 on desktop (lg:). Never force a multi-column layout on a small screen.
8px baseline grid: All spacing in multiples of 8. Margin, padding, gap, height. Consistent spacing is the difference between professional and amateur.
Asymmetric grids: For editorial and portfolio layouts. 1/3 + 2/3, 2/5 + 3/5. More dynamic than symmetric splits. Use when content types differ between columns (text + image, nav + content).
Spacing Scale
Use a consistent scale: 4, 8, 12, 16, 24, 32, 48, 64, 96px. Never arbitrary values.
- Tight (gap-1 to gap-2): Related items within a component (icon + label, avatar + name)
- Default (gap-4 to gap-6): Items within a section (cards in a grid, form fields)
- Spacious (gap-8 to gap-12): Between sections or major content blocks
- Dramatic (gap-16 to gap-24): Hero sections, page-level breathing room
Vertical Rhythm
Sections need rhythm. Alternate between:
- Dense sections (feature grids, pricing tables, testimonials)
- Breathing sections (hero, CTA, single-stat callouts)
Never stack two dense sections. Never stack two breathing sections. The rhythm keeps the reader moving.
Section spacing: py-16 (tight), py-24 (standard), py-32 (hero/spacious). Pick one for each section based on its density.
Reading Patterns
F-pattern: Users scan web pages in an F shape. Put the most important content in the top-left. First two lines get the most attention.
Z-pattern: For simpler pages (landing pages, posters). Eye moves: top-left > top-right > bottom-left > bottom-right. Place CTA at the end of the Z.
Single-column: For long-form content (articles, documentation). Max line width: 65-75 characters (max-w-prose or max-w-2xl). Wider lines reduce readability.
Section Anatomy
Every section needs: heading (what this section is about), supporting content (why the reader should care), visual element (image, icon, data), CTA or transition to next section. Sections without a clear purpose get cut.
Responsive Layout Patterns
Stack on mobile: Every multi-column layout becomes a single column below 768px. Reorder by priority: On mobile, the most important element comes first, even if it's visually second on desktop. Use Flexbox order or CSS Grid placement. Collapse navigation: Full nav becomes hamburger or bottom sheet below 768px. Scale typography: Reduce heading sizes by 1-2 steps on mobile. Body text stays the same.
Deliverables
1. Grid specification (columns, gutters, margins, breakpoints) 2. Spacing system (scale with use cases per step) 3. Section layout (structure for each content section with spacing annotations) 4. Responsive behavior (how each section adapts across breakpoints) 5. Vertical rhythm map (dense/breathing alternation plan)
Quality Checklist
- [ ] All spacing uses values from the defined scale, no arbitrary numbers
- [ ] 8px baseline grid respected throughout
- [ ] Line length for body text is 65-75 characters
- [ ] Dense and breathing sections alternate
- [ ] Mobile layout tested at 375px width
- [ ] No section exists without heading + content + visual + CTA/transition
- [ ] Grid is consistent across all pages and screens
Related skills
FAQ
What baseline grid does it use?
An 8px baseline with spacing in multiples of 8 for margins, padding, and gaps.
What is the recommended body line length?
Roughly 65–75 characters, often via max-w-prose or max-w-2xl for long-form text.
When should it run in the design flow?
After visual design sets the system and copy is placed, before final frontend implementation details.