[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWCGQ49SYT8F8T4MBZVEHN":3,"skill-same:01M6JWCGQ49SYT8F8T4MBZVEHN":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6JWCGQ49SYT8F8T4MBZVEHN","hierarchy-spatial",null,"Use this skill when constructing visual hierarchy through layout, position, size, and whitespace — not type, not color. Trigger when laying out a page or section and deciding what gets the dominant region, where to place the focal element, how much breathing room to give it, and how secondary elements should arrange around it. Trigger when reviewing a layout that \"feels cramped\" or \"feels lost,\" when a hero's CTA is competing with surrounding content, or when a dashboard's primary KPI is the same size as everything else. Sub-aspect of the broader `hierarchy` principle; read that first if you haven't already.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-spatial\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"hierarchy","hierarchy spatial","Spatial","as","when","whitespace","section","hero","you","color","element","trigger","type","dashboard","elements","layout","arrange","visual","use","read","page","how","kpi","breathing room","2026-11-10 10:12:30",false,"---\nname: hierarchy-spatial\ndescription: 'Use this skill when constructing visual hierarchy through layout, position, size, and whitespace — not type, not color. Trigger when laying out a page or section and deciding what gets the dominant region, where to place the focal element, how much breathing room to give it, and how secondary elements should arrange around it. Trigger when reviewing a layout that \"feels cramped\" or \"feels lost,\" when a hero''s CTA is competing with surrounding content, or when a dashboard''s primary KPI is the same size as everything else. Sub-aspect of the broader `hierarchy` principle; read that first if you haven''t already.'\n---\n\n# Hierarchy through space\n\nSpatial hierarchy uses three tools: **position**, **size** (relative to neighbors), and **whitespace** (isolation around an element). Together they can carry a complete hierarchy without depending on typography or color. Spatial hierarchy is what makes a magazine spread or a museum poster work even before you read a word.\n\n## When this is the decisive sub-aspect\n\n- You're laying out a hero, dashboard, gallery, or any composition where placement and size are doing more work than type.\n- You're reviewing a screen where \"everything has the same weight\" — the typographic hierarchy is fine but the layout is flat.\n- You need to elevate one element among many roughly equivalent ones (a featured project, a recommended plan, a primary metric).\n- You're working in a constrained type system (one or two sizes) and need hierarchy from elsewhere.\n\n## Core ideas\n\n### Size relative to neighbors carries hierarchy\n\nAbsolute size matters less than *relative* size. A 200×200 card next to other 200×200 cards is neutral. The same card at 200×200 next to seven 100×100 cards is dominant. Scale operates *against the local norm*; design hierarchy by establishing a norm and then breaking it deliberately.\n\nIn CSS Grid, this is `grid-column: span N` and `grid-row: span N`:\n\n```html\n\u003Csection style=\"display: grid; grid-template-columns: repeat(4, 1fr); gap: 1rem;\">\n  \u003Carticle class=\"featured\" style=\"grid-column: span 2; grid-row: span 2;\">…primary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n\u003C\u002Fsection>\n```\n\nThe featured article occupies four times the area of its neighbors. The eye lands there first.\n\n### Position privileges (in left-to-right scripts)\n\nThe eye, given an unfamiliar uniform layout, falls back to the **Z-pattern** (Gutenberg Diagram): top-left → top-right → bottom-left → bottom-right. Use this:\n\n- **Top-left** is the *primary optical area*. A logo, page title, or brand mark goes here naturally.\n- **Top-right** is the *strong fallow*. Useful for a primary CTA or account chrome.\n- **Bottom-right** is the *terminal area*. The eye exits here; place the conversion CTA in conversion-focused layouts.\n- **Bottom-left** is the *weak fallow*. Recede secondary content here.\n\nWhen hierarchy is *strong*, this default is overridden by the dominant element. When hierarchy is *weak*, the Z-pattern takes over by default.\n\nIn RTL scripts, mirror the pattern.\n\n### Whitespace as a hierarchy signal\n\nWhitespace around an element communicates importance. A primary heading with 4rem of margin above and below reads as more significant than the same heading with 0.5rem of margin. The element seems to *occupy* its space, not merely *fill* it.\n\nThe rough rule: *the more space around an element, the more important it appears* — up to a point where excess space starts to read as accident or empty page.\n\nA worked example using a vertical rhythm:\n\n```css\n:root {\n  --rhythm-tight: 0.25rem;   \u002F* between label and input *\u002F\n  --rhythm-base:  1rem;      \u002F* between fields in a section *\u002F\n  --rhythm-loose: 2rem;      \u002F* between sections *\u002F\n  --rhythm-major: 4rem;      \u002F* between page regions *\u002F\n  --rhythm-hero:  8rem;      \u002F* hero\u002Fmarketing surfaces *\u002F\n}\n\n.field-group   > * + * { margin-top: var(--rhythm-tight); }\n.section       > * + * { margin-top: var(--rhythm-base); }\n.page          > section + section { margin-top: var(--rhythm-loose); }\n.page-region   { padding-block: var(--rhythm-major); }\n.hero-section  { padding-block: var(--rhythm-hero); }\n```\n\nFive rhythm levels, each ~2x the previous. The eye reads the spacing as nesting: the things closest are most related; the things farthest are most separate (Proximity); the things with the most surrounding space are most important (Hierarchy).\n\n### Aspect ratio and orientation\n\nA wide element reads as expansive (banner, hero); a tall element reads as deep (sidebar, column); a square element reads as neutral (card, tile). Choose aspect ratio to match the role:\n\n- **Hero \u002F banner \u002F page header** — wide (≥ 16:9 or 21:9). Establishes presence.\n- **Card \u002F tile** — square or 4:3 \u002F 3:4. Neutral; designed to repeat.\n- **Sidebar \u002F column** — tall and narrow. Recedes laterally.\n- **Modal \u002F dialog** — typically 4:3 or 3:2 — wide enough for content, tall enough to feel deliberate.\n\nMismatching aspect to role makes hierarchy fight the layout.\n\n### Centering and alignment as hierarchy signals\n\nCenter alignment is high-attention but inflexible (you can't add another centered thing without competition). Left alignment is lower-attention but extensible. Right alignment is rare and signals secondary action (e.g., toolbar overflow menu).\n\nA useful rule: **center the one element you want the user to look at first; left-align everything else.**\n\n```html\n\u003Csection class=\"hero\">\n  \u003Ch1 style=\"text-align: center;\">Run payroll in minutes\u003C\u002Fh1>      \u003C!-- centered: the focal element -->\n  \u003Cp   style=\"text-align: center;\">Not hours. Not the next morning.\u003C\u002Fp>  \u003C!-- centered: paired support -->\n  \u003Cdiv style=\"text-align: center;\">\u003Cbutton>Start free trial\u003C\u002Fbutton>\u003C\u002Fdiv>\n\u003C\u002Fsection>\n\n\u003Csection class=\"features\" style=\"margin-top: 6rem;\">\n  \u003Ch2>What you get\u003C\u002Fh2>           \u003C!-- left-aligned: secondary section -->\n  \u003Cul>\n    \u003Cli>Automatic tax calculations\u003C\u002Fli>\n    \u003Cli>Direct deposit to 50 states\u003C\u002Fli>\n    \u003Cli>Year-end W-2 \u002F 1099 generation\u003C\u002Fli>\n  \u003C\u002Ful>\n\u003C\u002Fsection>\n```\n\nThe hero is centered; the rest is left-aligned. The eye registers the difference and treats the hero as the moment.\n\n## Worked example: a marketing landing page\n\nCombining all the spatial hierarchy tools:\n\n```html\n\u003Cmain class=\"landing\">\n  \u003C!-- Hero: centered, generous space, dominant -->\n  \u003Csection style=\"padding: 8rem 1rem; text-align: center;\">\n    \u003Ch1 style=\"font-size: 4rem; max-width: 32ch; margin: 0 auto;\">\n      Run payroll in minutes, not hours\n    \u003C\u002Fh1>\n    \u003Cp style=\"font-size: 1.25rem; max-width: 50ch; margin: 1.5rem auto 0;\">\n      Built for small teams that don't have a dedicated finance person.\n    \u003C\u002Fp>\n    \u003Cdiv style=\"margin-top: 3rem;\">\n      \u003Cbutton class=\"primary\">Start free trial\u003C\u002Fbutton>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- Features: 3-up grid, left-aligned, recessed -->\n  \u003Csection style=\"padding: 4rem 1rem; max-width: 1100px; margin: 0 auto;\">\n    \u003Ch2>Designed for small teams\u003C\u002Fh2>\n    \u003Cdiv style=\"display: grid; grid-template-columns: repeat(3, 1fr); gap: 2rem; margin-top: 3rem;\">\n      \u003Carticle>\u003Ch3>Automatic taxes\u003C\u002Fh3>\u003Cp>...\u003C\u002Fp>\u003C\u002Farticle>\n      \u003Carticle>\u003Ch3>Direct deposit\u003C\u002Fh3>\u003Cp>...\u003C\u002Fp>\u003C\u002Farticle>\n      \u003Carticle>\u003Ch3>Year-end forms\u003C\u002Fh3>\u003Cp>...\u003C\u002Fp>\u003C\u002Farticle>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- Featured customer: dominant within its section -->\n  \u003Csection style=\"padding: 4rem 1rem; background: #f7f7f7;\">\n    \u003Cdiv style=\"display: grid; grid-template-columns: 2fr 1fr; gap: 4rem; max-width: 1100px; margin: 0 auto;\">\n      \u003Cblockquote style=\"font-size: 1.5rem; line-height: 1.5;\">\n        \"We went from spending two days on payroll each month to twenty minutes.\"\n      \u003C\u002Fblockquote>\n      \u003Cdiv>\n        \u003Cp>Clara Mendoza\u003C\u002Fp>\n        \u003Cp>COO, Bright Labs\u003C\u002Fp>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\u003C\u002Fmain>\n```\n\nThree spatial hierarchies: hero dominant via centering + space; features uniform via grid; testimonial dominant within its section via 2:1 split. The page reads top-to-bottom with clear focal moments.\n\n## Anti-patterns\n\n- **Equal-space everything.** Every section the same height, every gap the same size. The eye gets no rhythm; the whole page feels mechanical.\n- **Centered everything.** Centering for emphasis works because most content is left-aligned. Center every paragraph and the emphasis collapses.\n- **The fold panic.** Cramming the hero, three features, and a CTA \"above the fold\" because of an imagined scroll-aversion. Modern users scroll without resistance; let the hero breathe and the CTA earn its place.\n- **The wall of cards.** A grid of identical cards with no featured tile is a \"browsing\" composition, not a \"reading\" composition. If the user is supposed to act, elevate one card.\n- **Whitespace where attention should be.** Massive whitespace around a recessive element makes the eye land on emptiness. Whitespace amplifies attention; aim it at things that earn it.\n\n## Heuristics\n\n1. **Mass diagram.** Sketch the page as filled black blocks with no detail. The dominant block should be 2–4× any other. If all blocks are similar size, hierarchy is flat.\n2. **The 30-foot test.** Stand back from your screen at distance until labels are unreadable. The composition should still tell you what's important.\n3. **Trace the eye-path.** Draw the line your eye follows through the composition. It should land on the primary first, sweep through secondaries, and exit at a CTA or terminal. If your eye-path is chaotic or returns to the primary repeatedly, refine.\n\n## Related principles\n\n- **`hierarchy`** — parent skill. Read it for full framing.\n- **`hierarchy-typographic`** — type-driven hierarchy; combines with spatial.\n- **`proximity`** — spacing between elements (Gestalt grouping); compounds with spatial hierarchy.\n- **`alignment`** — spatial hierarchy operates on a grid; misalignment fights it.\n- **`gutenberg-diagram`** — the default eye-path when hierarchy is absent.\n- **`horror-vacui`** — the impulse to fill empty space; resist it on important surfaces.\n","# Hierarchy through space\n\nSpatial hierarchy uses three tools: **position**, **size** (relative to neighbors), and **whitespace** (isolation around an element). Together they can carry a complete hierarchy without depending on typography or color. Spatial hierarchy is what makes a magazine spread or a museum poster work even before you read a word.\n\n## When this is the decisive sub-aspect\n\n- You're laying out a hero, dashboard, gallery, or any composition where placement and size are doing more work than type.\n- You're reviewing a screen where \"everything has the same weight\" — the typographic hierarchy is fine but the layout is flat.\n- You need to elevate one element among many roughly equivalent ones (a featured project, a recommended plan, a primary metric).\n- You're working in a constrained type system (one or two sizes) and need hierarchy from elsewhere.\n\n## Core ideas\n\n### Size relative to neighbors carries hierarchy\n\nAbsolute size matters less than *relative* size. A 200×200 card next to other 200×200 cards is neutral. The same card at 200×200 next to seven 100×100 cards is dominant. Scale operates *against the local norm*; design hierarchy by establishing a norm and then breaking it deliberately.\n\nIn CSS Grid, this is `grid-column: span N` and `grid-row: span N`:\n\n```html\n\u003Csection style=\"display: grid; grid-template-columns: repeat(4, 1fr); gap: 1rem;\">\n  \u003Carticle class=\"featured\" style=\"grid-column: span 2; grid-row: span 2;\">…primary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n  \u003Carticle>…secondary…\u003C\u002Farticle>\n\u003C\u002Fsection>\n```\n\nThe featured article occupies four times the area of its neighbors. The eye lands there first.\n\n### Position privileges (in left-to-right scripts)\n\nThe eye, given an unfamiliar uniform layout, falls back to the **Z-pattern** (Gutenberg Diagram): top-left → top-right → bottom-left → bottom-right. Use this:\n\n- **Top-left** is the *primary optical area*. A logo, page title, or brand mark goes here naturally.\n- **Top-right** is the *strong fallow*. Useful for a primary CTA or account chrome.\n- **Bottom-right** is the *terminal area*. The eye exits here; place the conversion CTA in conversion-focused layouts.\n- **Bottom-left** is the *weak fallow*. Recede secondary content here.\n\nWhen hierarchy is *strong*, this default is overridden by the dominant element. When hierarchy is *weak*, the Z-pattern takes over by default.\n\nIn RTL scripts, mirror the pattern.\n\n### Whitespace as a hierarchy signal\n\nWhitespace around an element communicates importance. A primary heading with 4rem of margin above and below reads as more significant than the same heading with 0.5rem of margin. The element seems to *occupy* its space, not merely *fill* it.\n\nThe rough rule: *the more space around an element, the more important it appears* — up to a point where excess space starts to read as accident or empty page.\n\nA worked example using a vertical rhythm:\n\n```css\n:root {\n  --rhythm-tight: 0.25rem;   \u002F* between label and input *\u002F\n  --rhythm-base:  1rem;      \u002F* between fields in a section *\u002F\n  --rhythm-loose: 2rem;      \u002F* between sections *\u002F\n  --rhythm-major: 4rem;      \u002F* between page regions *\u002F\n  --rhythm-hero:  8rem;      \u002F* hero\u002Fmarketing surfaces *\u002F\n}\n\n.field-group   > * + * { margin-top: var(--rhythm-tight); }\n.section       > * + * { margin-top: var(--rhythm-base); }\n.page          > section + section { margin-top: var(--rhythm-loose); }\n.page-region   { padding-block: var(--rhythm-major); }\n.hero-section  { padding-block: var(--rhythm-hero); }\n```\n\nFive rhythm levels, each ~2x the previous. The eye reads the spacing as nesting: the things closest are most related; the things farthest are most separate (Proximity); the things with the most surrounding space are most important (Hierarchy).\n\n### Aspect ratio and orientation\n\nA wide element reads as expansive (banner, hero); a tall element reads as deep (sidebar, column); a square element reads as neutral (card, tile). Choose aspect ratio to match the role:\n\n- **Hero \u002F banner \u002F page header** — wide (≥ 16:9 or 21:9). Establishes presence.\n- **Card \u002F tile** — square or 4:3 \u002F 3:4. Neutral; designed to repeat.\n- **Sidebar \u002F column** — tall and narrow. Recedes laterally.\n- **Modal \u002F dialog** — typically 4:3 or 3:2 — wide enough for content, tall enough to feel deliberate.\n\nMismatching aspect to role makes hierarchy fight the layout.\n\n### Centering and alignment as hierarchy signals\n\nCenter alignment is high-attention but inflexible (you can't add another centered thing without competition). Left alignment is lower-attention but extensible. Right alignment is rare and signals secondary action (e.g., toolbar overflow menu).\n\nA useful rule: **center the one element you want the user to look at first; left-align everything else.**\n\n```html\n\u003Csection class=\"hero\">\n  \u003Ch1 style=\"text-align: center;\">Run payroll in minutes\u003C\u002Fh1>      \u003C!-- centered: the focal element -->\n  \u003Cp   style=\"text-align: center;\">Not hours. Not the next morning.\u003C\u002Fp>  \u003C!-- centered: paired support -->\n  \u003Cdiv style=\"text-align: center;\">\u003Cbutton>Start free trial\u003C\u002Fbutton>\u003C\u002Fdiv>\n\u003C\u002Fsection>\n\n\u003Csection class=\"features\" style=\"margin-top: 6rem;\">\n  \u003Ch2>What you get\u003C\u002Fh2>           \u003C!-- left-aligned: secondary section -->\n  \u003Cul>\n    \u003Cli>Automatic tax calculations\u003C\u002Fli>\n    \u003Cli>Direct deposit to 50 states\u003C\u002Fli>\n    \u003Cli>Year-end W-2 \u002F 1099 generation\u003C\u002Fli>\n  \u003C\u002Ful>\n\u003C\u002Fsection>\n```\n\nThe hero is centered; the rest is left-aligned. The eye registers the difference and treats the hero as the moment.\n\n## Worked example: a marketing landing page\n\nCombining all the spatial hierarchy tools:\n\n```html\n\u003Cmain class=\"landing\">\n  \u003C!-- Hero: centered, generous space, dominant -->\n  \u003Csection style=\"padding: 8rem 1rem; text-align: center;\">\n    \u003Ch1 style=\"font-size: 4rem; max-width: 32ch; margin: 0 auto;\">\n      Run payroll in minutes, not hours\n    \u003C\u002Fh1>\n    \u003Cp style=\"font-size: 1.25rem; max-width: 50ch; margin: 1.5rem auto 0;\">\n      Built for small teams that don't have a dedicated finance person.\n    \u003C\u002Fp>\n    \u003Cdiv style=\"margin-top: 3rem;\">\n      \u003Cbutton class=\"primary\">Start free trial\u003C\u002Fbutton>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- Features: 3-up grid, left-aligned, recessed -->\n  \u003Csection style=\"padding: 4rem 1rem; max-width: 1100px; margin: 0 auto;\">\n    \u003Ch2>Designed for small teams\u003C\u002Fh2>\n    \u003Cdiv style=\"display: grid; grid-template-columns: repeat(3, 1fr); gap: 2rem; margin-top: 3rem;\">\n      \u003Carticle>\u003Ch3>Automatic taxes\u003C\u002Fh3>\u003Cp>...\u003C\u002Fp>\u003C\u002Farticle>\n      \u003Carticle>\u003Ch3>Direct deposit\u003C\u002Fh3>\u003Cp>...\u003C\u002Fp>\u003C\u002Farticle>\n      \u003Carticle>\u003Ch3>Year-end forms\u003C\u002Fh3>\u003Cp>...\u003C\u002Fp>\u003C\u002Farticle>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- Featured customer: dominant within its section -->\n  \u003Csection style=\"padding: 4rem 1rem; background: #f7f7f7;\">\n    \u003Cdiv style=\"display: grid; grid-template-columns: 2fr 1fr; gap: 4rem; max-width: 1100px; margin: 0 auto;\">\n      \u003Cblockquote style=\"font-size: 1.5rem; line-height: 1.5;\">\n        \"We went from spending two days on payroll each month to twenty minutes.\"\n      \u003C\u002Fblockquote>\n      \u003Cdiv>\n        \u003Cp>Clara Mendoza\u003C\u002Fp>\n        \u003Cp>COO, Bright Labs\u003C\u002Fp>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\u003C\u002Fmain>\n```\n\nThree spatial hierarchies: hero dominant via centering + space; features uniform via grid; testimonial dominant within its section via 2:1 split. The page reads top-to-bottom with clear focal moments.\n\n## Anti-patterns\n\n- **Equal-space everything.** Every section the same height, every gap the same size. The eye gets no rhythm; the whole page feels mechanical.\n- **Centered everything.** Centering for emphasis works because most content is left-aligned. Center every paragraph and the emphasis collapses.\n- **The fold panic.** Cramming the hero, three features, and a CTA \"above the fold\" because of an imagined scroll-aversion. Modern users scroll without resistance; let the hero breathe and the CTA earn its place.\n- **The wall of cards.** A grid of identical cards with no featured tile is a \"browsing\" composition, not a \"reading\" composition. If the user is supposed to act, elevate one card.\n- **Whitespace where attention should be.** Massive whitespace around a recessive element makes the eye land on emptiness. Whitespace amplifies attention; aim it at things that earn it.\n\n## Heuristics\n\n1. **Mass diagram.** Sketch the page as filled black blocks with no detail. The dominant block should be 2–4× any other. If all blocks are similar size, hierarchy is flat.\n2. **The 30-foot test.** Stand back from your screen at distance until labels are unreadable. The composition should still tell you what's important.\n3. **Trace the eye-path.** Draw the line your eye follows through the composition. It should land on the primary first, sweep through secondaries, and exit at a CTA or terminal. If your eye-path is chaotic or returns to the primary repeatedly, refine.\n\n## Related principles\n\n- **`hierarchy`** — parent skill. Read it for full framing.\n- **`hierarchy-typographic`** — type-driven hierarchy; combines with spatial.\n- **`proximity`** — spacing between elements (Gestalt grouping); compounds with spatial hierarchy.\n- **`alignment`** — spatial hierarchy operates on a grid; misalignment fights it.\n- **`gutenberg-diagram`** — the default eye-path when hierarchy is absent.\n- **`horror-vacui`** — the impulse to fill empty space; resist it on important surfaces.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-spatial",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hierarchy-spatial",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hierarchy-spatial",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hierarchy-spatial","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-spatial\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcomposition-traditions.md","REFERENCE","参考文档",6753,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-spatial\u002Freferences\u002Fcomposition-traditions.md",[79,89,97,105,113,121],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]