AGENT SKILL

layout-designer

Compose strong layouts with grid systems, visual hierarchy, rhythm, and balance for any format.

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

01 前言 Front Matter

name
layout-designer
category
creative-design
description
Compose strong layouts with grid systems, visual hierarchy, rhythm, and balance for any format.

03 SKILL.md 正文

Overview

Layout is the invisible architecture of design: the arrangement of elements that makes content scannable, credible, and beautiful. Whether it's a magazine spread, a dashboard, or a poster, the same principles apply — grid, hierarchy, rhythm, balance, and the deliberate use of space. This skill teaches layout as a systematic craft, not decoration.

When to use

  • Laying out editorial content (magazines, reports, books)

  • Designing posters, flyers, or marketing collateral

  • Structuring dashboards or data-dense interfaces

  • Improving a layout that feels cluttered or unbalanced

  • Setting up grid systems for multi-page documents

Core concepts

      • The grid. Columns, gutters, margins, and baselines create the skeleton. A 12-column grid handles most needs; the grid's job is consistency across pages and breakpoints, not visible lines.
      • Hierarchy: size, weight, position, color. The eye enters at the largest/boldest/most colorful element and follows the designed path. Every layout should have a clear entry point and a clear next step.
      • Rhythm and repetition. Repeating spacing intervals, consistent image treatments, and recurring elements create rhythm — the visual equivalent of meter in poetry. Rhythm makes multi-page documents feel cohesive.
      • Balance: symmetrical vs asymmetrical. Symmetrical layouts feel stable and formal; asymmetrical layouts feel dynamic and modern. Both need visual weight distributed deliberately — a heavy element on one side needs counterweight.
      • The fold and the scan. People scan in F-patterns (text-heavy) or Z-patterns (visual pages). Put key information on the scan path; don't bury the headline below decorative elements.
      • Breaking the grid. Intentional grid-breaking creates emphasis — but it only works when the grid is otherwise respected. Random misalignment isn't "breaking the grid," it's just misalignment.

Practical workflow

      1. Know the content and format. What must be communicated, in what order of importance? What's the physical or screen format? Content hierarchy drives layout, never the reverse.
      1. Set up the grid. Choose columns based on content complexity (2-3 for simple, up to 12 for complex), set margins for the format (print needs more), establish a baseline grid for text-heavy work.
      1. Block the hierarchy. Before any styling: rough boxes showing headline, key visual, body, secondary info, CTA. Get the information architecture right in grayscale boxes.
      1. Place the entry point. The dominant element goes where the eye lands first (top-left for text cultures, center for visual pieces). Everything else supports or follows it.
      1. Refine spacing. Consistent spacing scale (4/8/16/24/32...), related items grouped (proximity = relationship), generous margins. Squint test: does the structure hold?
      1. Check the details. Alignment (everything aligns to something), widows/orphans in text, image crops and captions, page numbers and running heads for documents, safe areas for print.
      1. Review as a system. For multi-page work: flip through quickly. Does it feel like one publication? Is there variety within consistency — or monotony?

Common pitfalls

      • No clear hierarchy. Everything similar in size and weight forces readers to work out what's important. That's the designer's job, not the reader's.
      • Fear of whitespace. Filling every corner because empty space feels wasteful. Whitespace is what makes the content legible and premium.
      • Inconsistent alignment. Elements almost-but-not-quite aligned — the most common layout flaw. Pick an edge and commit.
      • Trapped whitespace. Awkward gaps in the middle of layouts (often from mismatched element heights). Rebalance so space sits at edges, not stranded mid-page.
      • Ignoring the gutter. Content disappearing into book spines or getting cropped at edges. Respect margins and safe areas for the format.
      • Template rigidity. Using the same layout for every page/spread creates monotony. Vary within the system: full-bleed moments, quiet pages, asymmetric breaks — planned, not random.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You 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).

★ 0