[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757S39PCWN5A37ZZ19MMC2B":3,"skill-same:01M757S39PCWN5A37ZZ19MMC2B":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M757S39PCWN5A37ZZ19MMC2B","layout-and-composition",null,"Reference-grade system for composing any screen — visual hierarchy, Gestalt grouping, alignment, whitespace, scanning patterns, and modern intrinsic CSS layout (Grid\u002FFlexbox\u002Fsubgrid\u002Fcontainer queries\u002F:has) with copy-pasteable recipes.","jpoindexter\u002FVanta","jpoindexter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2729617?v=4","01M72VRRYY1CP7RPF3B7GHH0CR","01M757GWDBT6RD147ZZ79N4MEX",4,"MIT","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fdesign-system-skills\u002Flayout-and-composition\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: layout-and-composition\ndescription: Reference-grade system for composing any screen — visual hierarchy, Gestalt grouping, alignment, whitespace, scanning patterns, and modern intrinsic CSS layout (Grid\u002FFlexbox\u002Fsubgrid\u002Fcontainer queries\u002F:has) with copy-pasteable recipes.\ntags: [design-systems, layout, composition, hierarchy, gestalt]\n---\n# Layout & Composition\n\nComposition is the deliberate arrangement of elements so the eye lands where you want, groups what belongs together, and never has to guess what matters. Hierarchy is the *what*; layout is the *where*. This skill is the bible for both. Apply it to any screen — marketing page, dense dashboard, settings form, mobile flow.\n\n## 1. Visual hierarchy — ranking the eye's path\n\nThe eye does not read a screen top-to-bottom; it ranks elements by salience and jumps to the loudest. You control the ranking with these levers, roughly in order of power:\n\n| Lever | How it raises rank | Watch out for |\n|---|---|---|\n| **Size \u002F scale** | Bigger = more important. The strongest, fastest signal. | One hero only. Two \"biggest\" things = no hero. |\n| **Weight** | Bolder text\u002Fheavier shapes advance. | Don't bold everything — bold loses meaning if overused. |\n| **Color & saturation** | Saturated\u002Fwarm advances; muted\u002Fcool recedes. One accent = one action. | Color alone fails for ~8% (colorblind) + low-vision. Pair with shape\u002Ftext. |\n| **Contrast** | High contrast vs background pulls focus. | Body text needs ≥4.5:1; large\u002FUI ≥3:1 (WCAG AA). |\n| **Position** | Top-left (LTR) reads first; center = focal; corners = utility. | Don't bury the primary action below the fold. |\n| **Whitespace \u002F isolation** | Space *around* an element isolates it → it reads as important. | The single most underused lever. |\n\n**Establish three tiers explicitly.** Primary (the one thing — hero, the CTA), secondary (supporting — subhead, secondary buttons), tertiary (metadata, captions, legal). If you can't point at the one primary element, the screen has no hierarchy. A **focal point** is created by *contrast against context*: a saturated button on a calm page, a large number on a card of small labels. Isolation beats decoration — give the focal point room before you give it a glow.\n\n**Don't stack levers redundantly.** Size *and* weight *and* color *and* a box on the same element is shouting — the eye can't rank four equally-loud things. One or two levers per tier is enough: a heading earns rank from size alone; a CTA from color + isolation. Reserve the loudest combination for the single primary element so it has nothing to compete with.\n\n**Squint test.** Blur your eyes (or drop the design to 10% size). The element that still reads is your primary; if several do, or none does, the hierarchy is flat. This is the fastest hierarchy audit you have — run it on every screen before shipping.\n\n```css\n\u002F* Type scale carries 80% of hierarchy. Use a ratio, not arbitrary px. *\u002F\n:root {\n  --step--1: clamp(0.83rem, 0.8rem + 0.15vw, 0.9rem);\n  --step-0:  clamp(1rem,   0.95rem + 0.25vw, 1.125rem);  \u002F* body *\u002F\n  --step-1:  clamp(1.33rem, 1.2rem + 0.6vw, 1.6rem);\n  --step-2:  clamp(1.77rem, 1.5rem + 1.3vw, 2.4rem);\n  --step-3:  clamp(2.37rem, 1.9rem + 2.3vw, 3.6rem);      \u002F* hero *\u002F\n}\n```\n\n## 2. Gestalt principles — how the eye groups\n\nGestalt is *perception of grouping*. The brain auto-clusters before it reads. Use it to make structure feel obvious without borders.\n\n| Principle | The eye perceives… | Concrete UI use |\n|---|---|---|\n| **Proximity** | Near things as one group. | Label sits 4px above its input, 24px from the next field → reads as one unit. The biggest grouping tool you have. |\n| **Similarity** | Like-looking things as same kind. | All destructive actions red; all links one color → role learned once. |\n| **Common region** | Things in a shared boundary as a set. | A card `background` + `border-radius` groups its contents, even with little spacing. |\n| **Closure** | Implied\u002Fincomplete shapes as whole. | A 3-sided card edge, a progress ring, an icon outline read as complete. |\n| **Continuity** | Aligned elements as a connected flow. | A shared left edge guides the eye down a list\u002Fform effortlessly. |\n| **Figure \u002F ground** | One layer as subject, rest as backdrop. | Modal + dim scrim; the dialog is figure, page is ground. Elevation = z-shadow. |\n| **Common fate** | Things moving together as a group. | Accordion rows sliding in unison read as one section; a staggered list reads as items. |\n\n**Rule:** spacing *between* groups must be visibly larger than spacing *within* a group. If inner and outer gaps are equal, proximity breaks and everything reads as one undifferentiated wall.\n\n**Worked example — a form field.** Label `--s-1` (4px) above its input; help text `--s-1` below; the whole field block separated from the next by `--s-6` (24px). Now the eye reads three fields, not nine loose elements — and you've used zero borders. The same ratio drives list rows, nav sections, and card stacks: tight within, loose between.\n\n**Stacking contexts and figure\u002Fground in practice.** Elevation (`box-shadow`) and a higher `z-index` push an element forward as *figure*; a dim scrim (`background: rgb(0 0 0 \u002F .5)`) pushes everything else back as *ground*. Keep a small, named elevation scale (e.g. `--e-1` card, `--e-2` dropdown, `--e-3` modal) rather than ad-hoc shadows, so depth reads as a system and z-index wars don't start.\n\n## 3. Alignment, balance, rhythm\n\n- **Alignment.** Every element should align to *something* — a grid line, a sibling's edge, a shared baseline. **Edge alignment** (shared left\u002Fright) is the workhorse; **center alignment** suits short, symmetric, isolated content (hero, empty state) but fails for ragged left edges (lists, forms) because the eye loses its return point. **Optical alignment** overrides mathematical: nudge a play-triangle, a quote mark, or an arrow icon so it *looks* centered, not so its bounding box is. A single misaligned edge reads as broken even when nothing else is wrong.\n- **Proximity \u002F grouping** → see Gestalt §2. Group with space first, region (card\u002Fdivider) second.\n- **Balance.** **Symmetric** = formal, stable, calm (landing heroes, auth screens). **Asymmetric** = dynamic, modern; balance a large element against several small ones (visual weight, not mirror image). A dashboard is asymmetric by nature — balance a wide chart against a stacked column of stat cards.\n- **Tension** is intentional imbalance — an off-center subject, a diagonal, a deliberate overlap — used to draw the eye and add energy. Use sparingly; uncontrolled tension reads as a mistake.\n- **Rhythm & repetition.** Consistent spacing, recurring card shapes, a repeated type scale create rhythm the eye predicts and relaxes into. **Repetition** is what makes a design feel like a *system*; break it only to signal \"this is different.\"\n- **Contrast, scale, dominance.** Contrast (size\u002Fweight\u002Fcolor\u002Fspace) creates the difference that makes hierarchy legible. **Dominance** = one element clearly wins; without a dominant element, the composition has no entry point.\n\n**Grid as alignment backbone.** A column grid (commonly 12 columns on desktop, 4–8 on smaller) gives every element a legal edge to snap to, so alignment is enforced by structure rather than vigilance. Define it once with named lines or `repeat()` and place blocks on it. A **baseline grid** (vertical rhythm — line-heights and spacing as multiples of a base, e.g. 4px) does the same for the vertical axis: text baselines and block edges land on a predictable cadence, which is why a system *feels* tidy even when nothing is consciously noticed.\n\n```css\n.grid-12 { display: grid; grid-template-columns: repeat(12, 1fr); gap: var(--s-6); }\n.feature { grid-column: 1 \u002F 8; }   \u002F* span 7 cols *\u002F\n.aside   { grid-column: 8 \u002F -1; }  \u002F* fill to the last line *\u002F\n```\n\n## 4. Whitespace \u002F negative space\n\nWhitespace is not empty — it is an active grouping and hierarchy tool. **Macro whitespace** = space between major blocks\u002Fsections (sets page rhythm, signals importance, gives the page air). **Micro whitespace** = space between lines, words, list items, label-and-input (sets legibility and intra-group cohesion). More space *around* an element raises its perceived rank — luxury\u002Fpremium UIs are mostly whitespace.\n\nDensity is a deliberate choice, not an accident. Offer modes:\n\n| Mode | Use | Row height | Section gap |\n|---|---|---|---|\n| **Comfortable** | Marketing, reading, onboarding | 48–56px | 64–96px |\n| **Cozy** (default) | Most apps | 40–44px | 32–48px |\n| **Compact** | Data tables, power tools, IDEs | 28–32px | 16–24px |\n\n```css\n\u002F* Spacing token scale — one source of truth, multiples of a base. *\u002F\n:root { --s-1:4px; --s-2:8px; --s-3:12px; --s-4:16px; --s-6:24px; --s-8:32px; --s-12:48px; --s-16:64px; }\n[data-density=\"compact\"] { --row: 30px; --gap: var(--s-4); }\n[data-density=\"comfortable\"] { --row: 52px; --gap: var(--s-12); }\n```\n\nThe core law: **perceived grouping is a function of relative spacing.** Halve the gap inside a group and double it between groups before you reach for a single border.\n\n## 5. Scanning patterns\n\n- **F-pattern** — text-heavy pages (articles, search results, docs). Eyes scan the top line, drop down the left edge, scan again. Front-load headings and the start of each line with the meaningful word; never bury a verb at line-end.\n- **Z-pattern** — sparse pages (landing, hero, sign-up). Eye sweeps top-left → top-right (logo → nav\u002FCTA), diagonally to bottom-left, then bottom-right (final CTA). Place logo, primary nav, and the closing CTA on the Z's anchor points.\n- **Layer-cake** — alternating headings and content blocks; users scan headings\u002Fsubheads and dip into bodies that matter. Make headings genuinely scannable and self-describing.\n- **Spotted** — goal-directed scanning for a specific element (a price, a button, an error). Make the target visually distinct so the spotting succeeds fast.\n- **Reading direction \u002F RTL.** LTR primacy is top-left; for RTL (Arabic, Hebrew) it mirrors to top-right. Use **logical properties** (`margin-inline-start`, `inset-inline-end`) and `dir=\"rtl\"` so layout flips automatically — never hardcode `left`\u002F`right`.\n- **Above the fold** is fuzzy across devices but real: the first viewport must communicate what this is and offer the primary action or a clear scroll affordance. Don't cram everything above it — earn the scroll.\n\n**Match layout to the scan you expect.** A landing page is Z\u002Fspotted → big hero, sparse, one CTA on the diagonal. A docs page is F\u002Flayer-cake → strong left-aligned headings, scannable subheads, short line-start verbs. A data table is spotted → align numerics right, keep one accent for the cell that matters. Designing a content-heavy article like a sparse landing (centered, huge type) destroys the F-scan; designing a landing like an article (dense left rail of text) buries the CTA. The pattern is a constraint, not a decoration.\n\n## 6. Responsive layout patterns\n\nCatalog of recurring page skeletons and the responsive strategy each uses:\n\n| Pattern | Shape | Use |\n|---|---|---|\n| **Centered column** | `max-width` measure (60–75ch), auto margins | Reading, articles, settings |\n| **Sidebar + content** | Fixed\u002Fmin sidebar, fluid main | Docs, app shells, dashboards |\n| **Holy grail** | Header, footer, fluid center, two flank rails | Classic app shell |\n| **Split \u002F 50-50** | Two equal panes | Auth, compare, before\u002Fafter |\n| **Master–detail** | List rail + detail pane; collapses to stack on mobile | Mail, settings, chat |\n| **Card grid** | Auto-fitting responsive cards | Galleries, products, catalogs |\n\n**Responsive strategies** (Brad Frost): **mostly-fluid** (fluid grid, reflows then stacks — simplest, default for most); **column-drop** (full-width columns drop one-by-one as width shrinks); **layout-shifter** (layout meaningfully rearranges per breakpoint — most control, most maintenance); **off-canvas** (secondary nav\u002Fpanels slide off-screen, summoned on demand — mobile nav). **Intrinsic web design** (Jen Simmons): let content size itself — `auto-fit` + `minmax()`, `flex-wrap`, `min()\u002Fmax()\u002Fclamp()` — so the layout responds to *content and container*, not just a handful of device breakpoints. Prefer intrinsic methods; reach for `@media` breakpoints only where intrinsic rules can't express the change.\n\n**Breakpoints are content-driven, not device-driven.** Don't chase device widths (iPhone, iPad…) — they change yearly and you'll never cover them all. Add a breakpoint where *the layout breaks*: a line gets too long, a card too cramped, columns too narrow. Common anchors: ~`30rem`\u002F480px (phone→large phone), ~`48rem`\u002F768px (→tablet\u002Fstack-to-row), ~`64rem`\u002F1024px (→sidebar appears), ~`80rem`\u002F1280px (→max content width \u002F multi-column). Treat these as starting guesses you adjust by eye.\n\n**The `min()` column trick** prevents the classic `minmax()` overflow on tiny screens. `minmax(16rem, 1fr)` overflows below 16rem; `minmax(min(16rem, 100%), 1fr)` clamps to 100% and never blows out the viewport. Use it in every `auto-fit` grid.\n\n## 7. CSS implementation — Flexbox vs Grid, and recipes\n\n**Choose by dimensionality.** **Flexbox** = one axis, content-driven distribution (toolbars, button rows, tag lists, nav, anything that should wrap by content size). **Grid** = two axes, layout-driven structure (page skeletons, card galleries, forms, anything with row *and* column alignment). They compose — Grid for the page, Flex inside cells.\n\n```css\n\u002F* Sticky footer — page fills viewport, footer pinned to bottom. *\u002F\nbody { min-block-size: 100dvh; display: grid; grid-template-rows: auto 1fr auto; }\n\n\u002F* Perfectly centered card — modern, no margin hacks. *\u002F\n.center { display: grid; place-items: center; min-block-size: 100dvh; }\n\n\u002F* Responsive sidebar shell — sidebar shrinks to content, main takes the rest. *\u002F\n.shell { display: grid; grid-template-columns: minmax(200px, 18rem) 1fr; gap: var(--s-6); }\n@media (max-width: 48rem) { .shell { grid-template-columns: 1fr; } } \u002F* stack on mobile *\u002F\n\n\u002F* Intrinsic auto-grid gallery — NO media queries; cards reflow by available width. *\u002F\n.gallery {\n  display: grid;\n  grid-template-columns: repeat(auto-fit, minmax(min(16rem, 100%), 1fr));\n  gap: var(--s-6);\n}\n\n\u002F* Stack → row by content (the \"RAM\" \u002F Switcher pattern). *\u002F\n.cluster { display: flex; flex-wrap: wrap; gap: var(--s-4); }\n\n\u002F* Subgrid — align card internals (title\u002Fbody\u002Ffooter) across a row. *\u002F\n.card-row { display: grid; grid-template-columns: repeat(auto-fit, minmax(16rem,1fr)); gap: var(--s-6); }\n.card { display: grid; grid-row: span 3; grid-template-rows: subgrid; } \u002F* titles\u002Fbodies\u002Ffooters line up *\u002F\n```\n\n**Logical properties** (`block`\u002F`inline`, `inset-*`, `margin-inline`, `padding-block`) make layouts direction- and writing-mode-agnostic — default to them over physical `top\u002Fleft\u002Fwidth\u002Fheight`.\n\n**Container queries** make components responsive to *their container*, not the viewport — the same card adapts whether dropped in a sidebar or a full-width grid. This is component-level responsive design and the single biggest 2024+ shift.\n\n```css\n.card-wrap { container-type: inline-size; container-name: card; }\n@container card (min-width: 22rem) {\n  .card { grid-template-columns: 8rem 1fr; }   \u002F* media beside text when the container is wide *\u002F\n}\n```\n\n**`:has()` for layout reactions** — parent responds to children, no JS:\n\n```css\n.layout:has(> .sidebar) { grid-template-columns: 16rem 1fr; } \u002F* only when a sidebar exists *\u002F\n.field:has(:invalid) { border-color: var(--danger); }\n```\n\n**Worked recipe — full holy-grail app shell, intrinsic + container-aware.**\n\n```css\n.app-shell {\n  display: grid;\n  min-block-size: 100dvh;\n  grid-template:\n    \"header  header\" auto\n    \"sidebar main\"   1fr\n    \"footer  footer\" auto \u002F minmax(0, 16rem) 1fr;\n  gap: var(--s-4);\n}\n.app-shell > header { grid-area: header; }\n.app-shell > .sidebar { grid-area: sidebar; }\n.app-shell > main { grid-area: main; container-type: inline-size; min-inline-size: 0; }\n.app-shell > footer { grid-area: footer; }\n\n@media (max-width: 48rem) {                 \u002F* stack on small screens *\u002F\n  .app-shell { grid-template:\n    \"header\" auto \"main\" 1fr \"footer\" auto \u002F 1fr; }\n  .app-shell > .sidebar { display: none; }  \u002F* move to off-canvas drawer *\u002F\n}\n```\n\n`min-inline-size: 0` on `main` is load-bearing: grid\u002Fflex children default to `min-width: auto`, which lets long content (a wide table, a `\u003Cpre>`) refuse to shrink and blow out the layout. Set it to `0` (or `min-width:0`) on any flex\u002Fgrid child that holds variable-width content.\n\n## 8. Aspect ratio, overflow, sticky, safe areas\n\n```css\n.thumb { aspect-ratio: 16 \u002F 9; object-fit: cover; }     \u002F* reserve space, no layout shift *\u002F\n.scroll-x { overflow-x: auto; overscroll-behavior-x: contain; scroll-snap-type: x mandatory; }\n.sticky-head { position: sticky; inset-block-start: 0; z-index: 10; }  \u002F* table\u002Fsection headers *\u002F\n.app { padding: env(safe-area-inset-top) env(safe-area-inset-right)    \u002F* notches, home indicators *\u002F\n        env(safe-area-inset-bottom) env(safe-area-inset-left); }\n\n\u002F* Robust truncation: needs min-width:0 on the flex item or it never shrinks. *\u002F\n.truncate { min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }\n\u002F* Multi-line clamp (2 lines, then ellipsis). *\u002F\n.clamp-2 { display: -webkit-box; -webkit-line-clamp: 2; -webkit-box-orient: vertical; overflow: hidden; }\n```\n\n- **Overflow strategy:** decide per region — wrap (clusters), scroll (tables, horizontal card rails with snap), truncate (`text-overflow: ellipsis` on a single line with `min-width:0` on the flex child), or paginate. Never let content silently clip.\n- **Sticky vs fixed:** `sticky` flows with content then pins (section headers, sub-nav); `fixed` leaves flow entirely (toolbars, FABs). Fixed elements must not cover content — pad the scroll container for their height.\n- **Content-out vs canvas-in:** design *content-out* (let real content determine size, then constrain) rather than *canvas-in* (fix a frame and pour content in). Content-out survives translation, long names, dynamic data, and zoom.\n\n## 9. Cross-device & touch realities\n\n- **Use `dvh`\u002F`svh`\u002F`lvh`, not `vh`.** Mobile browser chrome shrinks\u002Fgrows the viewport; `100vh` overflows behind the URL bar. `100dvh` (dynamic) tracks the visible area; `svh`\u002F`lvh` give the small\u002Flarge extremes when you need stability.\n- **Touch targets ≥ 44×44px** (Apple HIG) \u002F 48×48px (Material) with spacing between them — fingers aren't cursors. Don't pack tappable rows tighter than `--row` 44px on touch.\n- **Thumb zones.** On phones, the bottom third is the easy-reach zone; the top is a stretch. Put primary actions (compose, next, pay) at the bottom — bottom bars and FABs exist for this. Reserve the top for back\u002Ftitle\u002Fsecondary.\n- **Hover is not guaranteed.** Don't hide critical info or actions behind `:hover` — touch has no hover. Gate hover-only affordances with `@media (hover: hover)` and provide a tap path.\n- **Respect motion preference.** Wrap transitions\u002Fparallax in `@media (prefers-reduced-motion: reduce)` and disable them — vestibular safety, not polish.\n- **Orientation & foldables.** Test portrait *and* landscape; don't assume tall. Avoid layouts that only work at one orientation; intrinsic grids handle both for free.\n\n```css\n.sheet { block-size: 100dvh; }                          \u002F* mobile-safe full height *\u002F\n@media (hover: hover) { .row:hover .actions { opacity: 1; } } \u002F* reveal only where hover exists *\u002F\n@media (prefers-reduced-motion: reduce) { * { animation: none !important; transition: none !important; } }\n```\n\n## 10. Do \u002F Don't\n\n**Do:** establish one clear primary element per screen · group with whitespace before borders · keep gaps between groups larger than within · align every element to a shared edge or grid · constrain text to a 60–75ch measure · use `clamp()`\u002F`min()`\u002F`max()` and `auto-fit minmax()` for fluidity · let components respond via container queries · use logical properties · reserve image space with `aspect-ratio`.\n\n**Don't:** center everything (ragged-left lists\u002Fforms must left-align) · make every element compete (no hierarchy) · mix alignment edges within a group · fight the grid with one-off margins and absolute positioning · set fixed heights on text containers (causes overflow\u002Fclip on zoom or translation) · ignore reflow at 200%\u002F400% zoom · use color as the *only* signal · cram everything above the fold.\n\n## 11. Common mistakes (and the fix)\n\n1. **Centering everything.** Looks tidy empty, falls apart with real content. → Left-align lists, forms, multi-line text; reserve center for short isolated content.\n2. **No hierarchy \u002F everything bold.** Nothing stands out. → Pick ONE primary, demote the rest with size\u002Fweight\u002Fcolor\u002Fspace.\n3. **Inconsistent alignment.** A single stray edge reads as broken. → Snap everything to a shared grid; audit by squinting for misaligned edges.\n4. **Fighting the grid.** Pixel-pushed margins and absolute positioning to force a look. → Express intent in Grid\u002FFlex; if you're nudging by 1px constantly, the structure is wrong.\n5. **Fixed heights on dynamic content.** Truncation, clipping, overlap when text grows, translates, or zooms. → Use `min-height`, let content size the box, handle overflow explicitly.\n6. **Ignoring reflow \u002F zoom.** Layout breaks at 200% zoom or 320px width. → Test at 320px and 400% zoom; use relative units and intrinsic layouts so it reflows, not scrolls in two axes.\n7. **Equal inner\u002Fouter spacing.** Groups dissolve. → Make outer gaps visibly larger than inner.\n8. **Viewport-only thinking.** Components that look right full-width break in a sidebar. → Make components respond to their container, not the page.\n9. **`100vh` on mobile.** Content hides behind the URL bar \u002F overflows. → Use `100dvh` (or `svh`\u002F`lvh`).\n10. **Magic-number spacing.** Random `13px`\u002F`27px` margins → no rhythm, impossible to maintain. → Spacing from a token scale only (multiples of a 4px base).\n11. **Min-width auto overflow.** A wide table or `\u003Cpre>` blows out a flex\u002Fgrid layout. → `min-width:0` \u002F `min-inline-size:0` on the variable-width child.\n12. **Tiny touch targets.** Sub-44px tap zones, packed tight → misfires on phones. → ≥44–48px with spacing; bigger in the thumb zone.\n","# Layout & Composition\n\nComposition is the deliberate arrangement of elements so the eye lands where you want, groups what belongs together, and never has to guess what matters. Hierarchy is the *what*; layout is the *where*. This skill is the bible for both. Apply it to any screen — marketing page, dense dashboard, settings form, mobile flow.\n\n## 1. Visual hierarchy — ranking the eye's path\n\nThe eye does not read a screen top-to-bottom; it ranks elements by salience and jumps to the loudest. You control the ranking with these levers, roughly in order of power:\n\n| Lever | How it raises rank | Watch out for |\n|---|---|---|\n| **Size \u002F scale** | Bigger = more important. The strongest, fastest signal. | One hero only. Two \"biggest\" things = no hero. |\n| **Weight** | Bolder text\u002Fheavier shapes advance. | Don't bold everything — bold loses meaning if overused. |\n| **Color & saturation** | Saturated\u002Fwarm advances; muted\u002Fcool recedes. One accent = one action. | Color alone fails for ~8% (colorblind) + low-vision. Pair with shape\u002Ftext. |\n| **Contrast** | High contrast vs background pulls focus. | Body text needs ≥4.5:1; large\u002FUI ≥3:1 (WCAG AA). |\n| **Position** | Top-left (LTR) reads first; center = focal; corners = utility. | Don't bury the primary action below the fold. |\n| **Whitespace \u002F isolation** | Space *around* an element isolates it → it reads as important. | The single most underused lever. |\n\n**Establish three tiers explicitly.** Primary (the one thing — hero, the CTA), secondary (supporting — subhead, secondary buttons), tertiary (metadata, captions, legal). If you can't point at the one primary element, the screen has no hierarchy. A **focal point** is created by *contrast against context*: a saturated button on a calm page, a large number on a card of small labels. Isolation beats decoration — give the focal point room before you give it a glow.\n\n**Don't stack levers redundantly.** Size *and* weight *and* color *and* a box on the same element is shouting — the eye can't rank four equally-loud things. One or two levers per tier is enough: a heading earns rank from size alone; a CTA from color + isolation. Reserve the loudest combination for the single primary element so it has nothing to compete with.\n\n**Squint test.** Blur your eyes (or drop the design to 10% size). The element that still reads is your primary; if several do, or none does, the hierarchy is flat. This is the fastest hierarchy audit you have — run it on every screen before shipping.\n\n```css\n\u002F* Type scale carries 80% of hierarchy. Use a ratio, not arbitrary px. *\u002F\n:root {\n  --step--1: clamp(0.83rem, 0.8rem + 0.15vw, 0.9rem);\n  --step-0:  clamp(1rem,   0.95rem + 0.25vw, 1.125rem);  \u002F* body *\u002F\n  --step-1:  clamp(1.33rem, 1.2rem + 0.6vw, 1.6rem);\n  --step-2:  clamp(1.77rem, 1.5rem + 1.3vw, 2.4rem);\n  --step-3:  clamp(2.37rem, 1.9rem + 2.3vw, 3.6rem);      \u002F* hero *\u002F\n}\n```\n\n## 2. Gestalt principles — how the eye groups\n\nGestalt is *perception of grouping*. The brain auto-clusters before it reads. Use it to make structure feel obvious without borders.\n\n| Principle | The eye perceives… | Concrete UI use |\n|---|---|---|\n| **Proximity** | Near things as one group. | Label sits 4px above its input, 24px from the next field → reads as one unit. The biggest grouping tool you have. |\n| **Similarity** | Like-looking things as same kind. | All destructive actions red; all links one color → role learned once. |\n| **Common region** | Things in a shared boundary as a set. | A card `background` + `border-radius` groups its contents, even with little spacing. |\n| **Closure** | Implied\u002Fincomplete shapes as whole. | A 3-sided card edge, a progress ring, an icon outline read as complete. |\n| **Continuity** | Aligned elements as a connected flow. | A shared left edge guides the eye down a list\u002Fform effortlessly. |\n| **Figure \u002F ground** | One layer as subject, rest as backdrop. | Modal + dim scrim; the dialog is figure, page is ground. Elevation = z-shadow. |\n| **Common fate** | Things moving together as a group. | Accordion rows sliding in unison read as one section; a staggered list reads as items. |\n\n**Rule:** spacing *between* groups must be visibly larger than spacing *within* a group. If inner and outer gaps are equal, proximity breaks and everything reads as one undifferentiated wall.\n\n**Worked example — a form field.** Label `--s-1` (4px) above its input; help text `--s-1` below; the whole field block separated from the next by `--s-6` (24px). Now the eye reads three fields, not nine loose elements — and you've used zero borders. The same ratio drives list rows, nav sections, and card stacks: tight within, loose between.\n\n**Stacking contexts and figure\u002Fground in practice.** Elevation (`box-shadow`) and a higher `z-index` push an element forward as *figure*; a dim scrim (`background: rgb(0 0 0 \u002F .5)`) pushes everything else back as *ground*. Keep a small, named elevation scale (e.g. `--e-1` card, `--e-2` dropdown, `--e-3` modal) rather than ad-hoc shadows, so depth reads as a system and z-index wars don't start.\n\n## 3. Alignment, balance, rhythm\n\n- **Alignment.** Every element should align to *something* — a grid line, a sibling's edge, a shared baseline. **Edge alignment** (shared left\u002Fright) is the workhorse; **center alignment** suits short, symmetric, isolated content (hero, empty state) but fails for ragged left edges (lists, forms) because the eye loses its return point. **Optical alignment** overrides mathematical: nudge a play-triangle, a quote mark, or an arrow icon so it *looks* centered, not so its bounding box is. A single misaligned edge reads as broken even when nothing else is wrong.\n- **Proximity \u002F grouping** → see Gestalt §2. Group with space first, region (card\u002Fdivider) second.\n- **Balance.** **Symmetric** = formal, stable, calm (landing heroes, auth screens). **Asymmetric** = dynamic, modern; balance a large element against several small ones (visual weight, not mirror image). A dashboard is asymmetric by nature — balance a wide chart against a stacked column of stat cards.\n- **Tension** is intentional imbalance — an off-center subject, a diagonal, a deliberate overlap — used to draw the eye and add energy. Use sparingly; uncontrolled tension reads as a mistake.\n- **Rhythm & repetition.** Consistent spacing, recurring card shapes, a repeated type scale create rhythm the eye predicts and relaxes into. **Repetition** is what makes a design feel like a *system*; break it only to signal \"this is different.\"\n- **Contrast, scale, dominance.** Contrast (size\u002Fweight\u002Fcolor\u002Fspace) creates the difference that makes hierarchy legible. **Dominance** = one element clearly wins; without a dominant element, the composition has no entry point.\n\n**Grid as alignment backbone.** A column grid (commonly 12 columns on desktop, 4–8 on smaller) gives every element a legal edge to snap to, so alignment is enforced by structure rather than vigilance. Define it once with named lines or `repeat()` and place blocks on it. A **baseline grid** (vertical rhythm — line-heights and spacing as multiples of a base, e.g. 4px) does the same for the vertical axis: text baselines and block edges land on a predictable cadence, which is why a system *feels* tidy even when nothing is consciously noticed.\n\n```css\n.grid-12 { display: grid; grid-template-columns: repeat(12, 1fr); gap: var(--s-6); }\n.feature { grid-column: 1 \u002F 8; }   \u002F* span 7 cols *\u002F\n.aside   { grid-column: 8 \u002F -1; }  \u002F* fill to the last line *\u002F\n```\n\n## 4. Whitespace \u002F negative space\n\nWhitespace is not empty — it is an active grouping and hierarchy tool. **Macro whitespace** = space between major blocks\u002Fsections (sets page rhythm, signals importance, gives the page air). **Micro whitespace** = space between lines, words, list items, label-and-input (sets legibility and intra-group cohesion). More space *around* an element raises its perceived rank — luxury\u002Fpremium UIs are mostly whitespace.\n\nDensity is a deliberate choice, not an accident. Offer modes:\n\n| Mode | Use | Row height | Section gap |\n|---|---|---|---|\n| **Comfortable** | Marketing, reading, onboarding | 48–56px | 64–96px |\n| **Cozy** (default) | Most apps | 40–44px | 32–48px |\n| **Compact** | Data tables, power tools, IDEs | 28–32px | 16–24px |\n\n```css\n\u002F* Spacing token scale — one source of truth, multiples of a base. *\u002F\n:root { --s-1:4px; --s-2:8px; --s-3:12px; --s-4:16px; --s-6:24px; --s-8:32px; --s-12:48px; --s-16:64px; }\n[data-density=\"compact\"] { --row: 30px; --gap: var(--s-4); }\n[data-density=\"comfortable\"] { --row: 52px; --gap: var(--s-12); }\n```\n\nThe core law: **perceived grouping is a function of relative spacing.** Halve the gap inside a group and double it between groups before you reach for a single border.\n\n## 5. Scanning patterns\n\n- **F-pattern** — text-heavy pages (articles, search results, docs). Eyes scan the top line, drop down the left edge, scan again. Front-load headings and the start of each line with the meaningful word; never bury a verb at line-end.\n- **Z-pattern** — sparse pages (landing, hero, sign-up). Eye sweeps top-left → top-right (logo → nav\u002FCTA), diagonally to bottom-left, then bottom-right (final CTA). Place logo, primary nav, and the closing CTA on the Z's anchor points.\n- **Layer-cake** — alternating headings and content blocks; users scan headings\u002Fsubheads and dip into bodies that matter. Make headings genuinely scannable and self-describing.\n- **Spotted** — goal-directed scanning for a specific element (a price, a button, an error). Make the target visually distinct so the spotting succeeds fast.\n- **Reading direction \u002F RTL.** LTR primacy is top-left; for RTL (Arabic, Hebrew) it mirrors to top-right. Use **logical properties** (`margin-inline-start`, `inset-inline-end`) and `dir=\"rtl\"` so layout flips automatically — never hardcode `left`\u002F`right`.\n- **Above the fold** is fuzzy across devices but real: the first viewport must communicate what this is and offer the primary action or a clear scroll affordance. Don't cram everything above it — earn the scroll.\n\n**Match layout to the scan you expect.** A landing page is Z\u002Fspotted → big hero, sparse, one CTA on the diagonal. A docs page is F\u002Flayer-cake → strong left-aligned headings, scannable subheads, short line-start verbs. A data table is spotted → align numerics right, keep one accent for the cell that matters. Designing a content-heavy article like a sparse landing (centered, huge type) destroys the F-scan; designing a landing like an article (dense left rail of text) buries the CTA. The pattern is a constraint, not a decoration.\n\n## 6. Responsive layout patterns\n\nCatalog of recurring page skeletons and the responsive strategy each uses:\n\n| Pattern | Shape | Use |\n|---|---|---|\n| **Centered column** | `max-width` measure (60–75ch), auto margins | Reading, articles, settings |\n| **Sidebar + content** | Fixed\u002Fmin sidebar, fluid main | Docs, app shells, dashboards |\n| **Holy grail** | Header, footer, fluid center, two flank rails | Classic app shell |\n| **Split \u002F 50-50** | Two equal panes | Auth, compare, before\u002Fafter |\n| **Master–detail** | List rail + detail pane; collapses to stack on mobile | Mail, settings, chat |\n| **Card grid** | Auto-fitting responsive cards | Galleries, products, catalogs |\n\n**Responsive strategies** (Brad Frost): **mostly-fluid** (fluid grid, reflows then stacks — simplest, default for most); **column-drop** (full-width columns drop one-by-one as width shrinks); **layout-shifter** (layout meaningfully rearranges per breakpoint — most control, most maintenance); **off-canvas** (secondary nav\u002Fpanels slide off-screen, summoned on demand — mobile nav). **Intrinsic web design** (Jen Simmons): let content size itself — `auto-fit` + `minmax()`, `flex-wrap`, `min()\u002Fmax()\u002Fclamp()` — so the layout responds to *content and container*, not just a handful of device breakpoints. Prefer intrinsic methods; reach for `@media` breakpoints only where intrinsic rules can't express the change.\n\n**Breakpoints are content-driven, not device-driven.** Don't chase device widths (iPhone, iPad…) — they change yearly and you'll never cover them all. Add a breakpoint where *the layout breaks*: a line gets too long, a card too cramped, columns too narrow. Common anchors: ~`30rem`\u002F480px (phone→large phone), ~`48rem`\u002F768px (→tablet\u002Fstack-to-row), ~`64rem`\u002F1024px (→sidebar appears), ~`80rem`\u002F1280px (→max content width \u002F multi-column). Treat these as starting guesses you adjust by eye.\n\n**The `min()` column trick** prevents the classic `minmax()` overflow on tiny screens. `minmax(16rem, 1fr)` overflows below 16rem; `minmax(min(16rem, 100%), 1fr)` clamps to 100% and never blows out the viewport. Use it in every `auto-fit` grid.\n\n## 7. CSS implementation — Flexbox vs Grid, and recipes\n\n**Choose by dimensionality.** **Flexbox** = one axis, content-driven distribution (toolbars, button rows, tag lists, nav, anything that should wrap by content size). **Grid** = two axes, layout-driven structure (page skeletons, card galleries, forms, anything with row *and* column alignment). They compose — Grid for the page, Flex inside cells.\n\n```css\n\u002F* Sticky footer — page fills viewport, footer pinned to bottom. *\u002F\nbody { min-block-size: 100dvh; display: grid; grid-template-rows: auto 1fr auto; }\n\n\u002F* Perfectly centered card — modern, no margin hacks. *\u002F\n.center { display: grid; place-items: center; min-block-size: 100dvh; }\n\n\u002F* Responsive sidebar shell — sidebar shrinks to content, main takes the rest. *\u002F\n.shell { display: grid; grid-template-columns: minmax(200px, 18rem) 1fr; gap: var(--s-6); }\n@media (max-width: 48rem) { .shell { grid-template-columns: 1fr; } } \u002F* stack on mobile *\u002F\n\n\u002F* Intrinsic auto-grid gallery — NO media queries; cards reflow by available width. *\u002F\n.gallery {\n  display: grid;\n  grid-template-columns: repeat(auto-fit, minmax(min(16rem, 100%), 1fr));\n  gap: var(--s-6);\n}\n\n\u002F* Stack → row by content (the \"RAM\" \u002F Switcher pattern). *\u002F\n.cluster { display: flex; flex-wrap: wrap; gap: var(--s-4); }\n\n\u002F* Subgrid — align card internals (title\u002Fbody\u002Ffooter) across a row. *\u002F\n.card-row { display: grid; grid-template-columns: repeat(auto-fit, minmax(16rem,1fr)); gap: var(--s-6); }\n.card { display: grid; grid-row: span 3; grid-template-rows: subgrid; } \u002F* titles\u002Fbodies\u002Ffooters line up *\u002F\n```\n\n**Logical properties** (`block`\u002F`inline`, `inset-*`, `margin-inline`, `padding-block`) make layouts direction- and writing-mode-agnostic — default to them over physical `top\u002Fleft\u002Fwidth\u002Fheight`.\n\n**Container queries** make components responsive to *their container*, not the viewport — the same card adapts whether dropped in a sidebar or a full-width grid. This is component-level responsive design and the single biggest 2024+ shift.\n\n```css\n.card-wrap { container-type: inline-size; container-name: card; }\n@container card (min-width: 22rem) {\n  .card { grid-template-columns: 8rem 1fr; }   \u002F* media beside text when the container is wide *\u002F\n}\n```\n\n**`:has()` for layout reactions** — parent responds to children, no JS:\n\n```css\n.layout:has(> .sidebar) { grid-template-columns: 16rem 1fr; } \u002F* only when a sidebar exists *\u002F\n.field:has(:invalid) { border-color: var(--danger); }\n```\n\n**Worked recipe — full holy-grail app shell, intrinsic + container-aware.**\n\n```css\n.app-shell {\n  display: grid;\n  min-block-size: 100dvh;\n  grid-template:\n    \"header  header\" auto\n    \"sidebar main\"   1fr\n    \"footer  footer\" auto \u002F minmax(0, 16rem) 1fr;\n  gap: var(--s-4);\n}\n.app-shell > header { grid-area: header; }\n.app-shell > .sidebar { grid-area: sidebar; }\n.app-shell > main { grid-area: main; container-type: inline-size; min-inline-size: 0; }\n.app-shell > footer { grid-area: footer; }\n\n@media (max-width: 48rem) {                 \u002F* stack on small screens *\u002F\n  .app-shell { grid-template:\n    \"header\" auto \"main\" 1fr \"footer\" auto \u002F 1fr; }\n  .app-shell > .sidebar { display: none; }  \u002F* move to off-canvas drawer *\u002F\n}\n```\n\n`min-inline-size: 0` on `main` is load-bearing: grid\u002Fflex children default to `min-width: auto`, which lets long content (a wide table, a `\u003Cpre>`) refuse to shrink and blow out the layout. Set it to `0` (or `min-width:0`) on any flex\u002Fgrid child that holds variable-width content.\n\n## 8. Aspect ratio, overflow, sticky, safe areas\n\n```css\n.thumb { aspect-ratio: 16 \u002F 9; object-fit: cover; }     \u002F* reserve space, no layout shift *\u002F\n.scroll-x { overflow-x: auto; overscroll-behavior-x: contain; scroll-snap-type: x mandatory; }\n.sticky-head { position: sticky; inset-block-start: 0; z-index: 10; }  \u002F* table\u002Fsection headers *\u002F\n.app { padding: env(safe-area-inset-top) env(safe-area-inset-right)    \u002F* notches, home indicators *\u002F\n        env(safe-area-inset-bottom) env(safe-area-inset-left); }\n\n\u002F* Robust truncation: needs min-width:0 on the flex item or it never shrinks. *\u002F\n.truncate { min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }\n\u002F* Multi-line clamp (2 lines, then ellipsis). *\u002F\n.clamp-2 { display: -webkit-box; -webkit-line-clamp: 2; -webkit-box-orient: vertical; overflow: hidden; }\n```\n\n- **Overflow strategy:** decide per region — wrap (clusters), scroll (tables, horizontal card rails with snap), truncate (`text-overflow: ellipsis` on a single line with `min-width:0` on the flex child), or paginate. Never let content silently clip.\n- **Sticky vs fixed:** `sticky` flows with content then pins (section headers, sub-nav); `fixed` leaves flow entirely (toolbars, FABs). Fixed elements must not cover content — pad the scroll container for their height.\n- **Content-out vs canvas-in:** design *content-out* (let real content determine size, then constrain) rather than *canvas-in* (fix a frame and pour content in). Content-out survives translation, long names, dynamic data, and zoom.\n\n## 9. Cross-device & touch realities\n\n- **Use `dvh`\u002F`svh`\u002F`lvh`, not `vh`.** Mobile browser chrome shrinks\u002Fgrows the viewport; `100vh` overflows behind the URL bar. `100dvh` (dynamic) tracks the visible area; `svh`\u002F`lvh` give the small\u002Flarge extremes when you need stability.\n- **Touch targets ≥ 44×44px** (Apple HIG) \u002F 48×48px (Material) with spacing between them — fingers aren't cursors. Don't pack tappable rows tighter than `--row` 44px on touch.\n- **Thumb zones.** On phones, the bottom third is the easy-reach zone; the top is a stretch. Put primary actions (compose, next, pay) at the bottom — bottom bars and FABs exist for this. Reserve the top for back\u002Ftitle\u002Fsecondary.\n- **Hover is not guaranteed.** Don't hide critical info or actions behind `:hover` — touch has no hover. Gate hover-only affordances with `@media (hover: hover)` and provide a tap path.\n- **Respect motion preference.** Wrap transitions\u002Fparallax in `@media (prefers-reduced-motion: reduce)` and disable them — vestibular safety, not polish.\n- **Orientation & foldables.** Test portrait *and* landscape; don't assume tall. Avoid layouts that only work at one orientation; intrinsic grids handle both for free.\n\n```css\n.sheet { block-size: 100dvh; }                          \u002F* mobile-safe full height *\u002F\n@media (hover: hover) { .row:hover .actions { opacity: 1; } } \u002F* reveal only where hover exists *\u002F\n@media (prefers-reduced-motion: reduce) { * { animation: none !important; transition: none !important; } }\n```\n\n## 10. Do \u002F Don't\n\n**Do:** establish one clear primary element per screen · group with whitespace before borders · keep gaps between groups larger than within · align every element to a shared edge or grid · constrain text to a 60–75ch measure · use `clamp()`\u002F`min()`\u002F`max()` and `auto-fit minmax()` for fluidity · let components respond via container queries · use logical properties · reserve image space with `aspect-ratio`.\n\n**Don't:** center everything (ragged-left lists\u002Fforms must left-align) · make every element compete (no hierarchy) · mix alignment edges within a group · fight the grid with one-off margins and absolute positioning · set fixed heights on text containers (causes overflow\u002Fclip on zoom or translation) · ignore reflow at 200%\u002F400% zoom · use color as the *only* signal · cram everything above the fold.\n\n## 11. Common mistakes (and the fix)\n\n1. **Centering everything.** Looks tidy empty, falls apart with real content. → Left-align lists, forms, multi-line text; reserve center for short isolated content.\n2. **No hierarchy \u002F everything bold.** Nothing stands out. → Pick ONE primary, demote the rest with size\u002Fweight\u002Fcolor\u002Fspace.\n3. **Inconsistent alignment.** A single stray edge reads as broken. → Snap everything to a shared grid; audit by squinting for misaligned edges.\n4. **Fighting the grid.** Pixel-pushed margins and absolute positioning to force a look. → Express intent in Grid\u002FFlex; if you're nudging by 1px constantly, the structure is wrong.\n5. **Fixed heights on dynamic content.** Truncation, clipping, overlap when text grows, translates, or zooms. → Use `min-height`, let content size the box, handle overflow explicitly.\n6. **Ignoring reflow \u002F zoom.** Layout breaks at 200% zoom or 320px width. → Test at 320px and 400% zoom; use relative units and intrinsic layouts so it reflows, not scrolls in two axes.\n7. **Equal inner\u002Fouter spacing.** Groups dissolve. → Make outer gaps visibly larger than inner.\n8. **Viewport-only thinking.** Components that look right full-width break in a sidebar. → Make components respond to their container, not the page.\n9. **`100vh` on mobile.** Content hides behind the URL bar \u002F overflows. → Use `100dvh` (or `svh`\u002F`lvh`).\n10. **Magic-number spacing.** Random `13px`\u002F`27px` margins → no rhythm, impossible to maintain. → Spacing from a token scale only (multiples of a 4px base).\n11. **Min-width auto overflow.** A wide table or `\u003Cpre>` blows out a flex\u002Fgrid layout. → `min-width:0` \u002F `min-inline-size:0` on the variable-width child.\n12. **Tiny touch targets.** Sub-44px tap zones, packed tight → misfires on phones. → ≥44–48px with spacing; bigger in the thumb zone.\n",{"name":5,"tags":23,"description":7},[24,25,26,27,28],"design-systems","layout","composition","hierarchy","gestalt","main","4911ae44bbb35beef4511ba298475ba5a82b7e1c","design-system-skills\u002Flayout-and-composition",0,"https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta","https:\u002F\u002Fdocs.vanta.theft.studio","https:\u002F\u002Fgithub.com\u002Fjpoindexter","jason.theft.studio","Just some guy trying to build stuff","2026-11-12 17:11:35",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add jpoindexter\u002FVanta --skill layout-and-composition",{"tool":45,"command":46},"bunx","bunx skills add jpoindexter\u002FVanta --skill layout-and-composition",{"tool":48,"command":49},"pnpm","pnpm dlx skills add jpoindexter\u002FVanta --skill layout-and-composition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fdesign-system-skills\u002Flayout-and-composition\u002FSKILL.md",true,[],[54,61,68,75,82,88],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7582PEM7XM8B98VFRDV0C0J","write-changelog","Turn a range of commits into a user-facing changelog","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fopenclaw\u002Fskills\u002Fwrite-changelog\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7582KTQJMP5Y7GS83MS1C7Z","debug-flaky-test","Reproduce and isolate a flaky test before fixing it","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fopenclaw\u002Fskills\u002Fdebug-flaky-test\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7582HG7XFM4Z5NGG1YFECT8","triage-incident","First 10 minutes of an incident — stabilize, then diagnose","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fsrc\u002Fmigrate\u002F__fixtures__\u002Fhermes\u002Fskills\u002Ftriage-incident\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7582DQABK7A96XHMB770KQZ","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7582BBK8H0HGSXKK08FCXJ1","vanta-port-adapter","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Fvanta-port-adapter\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M75828P8PX5XSBMJ2BVVDA9Y","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fjpoindexter\u002FVanta\u002Fblob\u002Fmain\u002Fvanta-ts\u002Fskills-library\u002Ftest-driven-development\u002FSKILL.md",[],[]]