[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESMW49CZB3K0XRB20K47CX":3,"skill-same:01M7ESMW49CZB3K0XRB20K47CX":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7ESMW49CZB3K0XRB20K47CX","layout-designer",null,"Compose strong layouts with grid systems, visual hierarchy, rhythm, and balance for any format.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-layout-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: layout-designer\ndescription: Compose strong layouts with grid systems, visual hierarchy, rhythm, and balance for any format.\ncategory: creative-design\n---\n\n## Overview\n\nLayout is the invisible architecture of design: the arrangement of elements that\nmakes content\nscannable, credible, and beautiful. Whether it's a magazine spread, a dashboard,\nor a poster, the\nsame principles apply — grid, hierarchy, rhythm, balance, and the deliberate use\nof space. This\nskill teaches layout as a systematic craft, not decoration.\n\n## When to use\n\n- Laying out editorial content (magazines, reports, books)\n\n- Designing posters, flyers, or marketing collateral\n\n- Structuring dashboards or data-dense interfaces\n\n- Improving a layout that feels cluttered or unbalanced\n\n- Setting up grid systems for multi-page documents\n\n## Core concepts\n\n- - - **The grid.** Columns, gutters, margins, and baselines create the\n  skeleton. A 12-column grid\n  handles most needs; the grid's job is consistency across pages and\nbreakpoints, not visible lines.\n- - - **Hierarchy: size, weight, position, color.** The eye enters at the\n  largest\u002Fboldest\u002Fmost\n  colorful element and follows the designed path. Every layout should have a\nclear entry point and a\n  clear next step.\n- - - **Rhythm and repetition.** Repeating spacing intervals, consistent image\n  treatments, and\n  recurring elements create rhythm — the visual equivalent of meter in poetry.\nRhythm makes\n  multi-page documents feel cohesive.\n- - - **Balance: symmetrical vs asymmetrical.** Symmetrical layouts feel stable\n  and formal;\n  asymmetrical layouts feel dynamic and modern. Both need visual weight\ndistributed deliberately — a\n  heavy element on one side needs counterweight.\n- - - **The fold and the scan.** People scan in F-patterns (text-heavy) or\n  Z-patterns (visual pages).\n  Put key information on the scan path; don't bury the headline below decorative\nelements.\n- - - **Breaking the grid.** Intentional grid-breaking creates emphasis — but it\n  only works when the\n  grid is otherwise respected. Random misalignment isn't \"breaking the grid,\"\nit's just\n  misalignment.\n\n## Practical workflow\n\n1. 1. 1. **Know the content and format.** What must be communicated, in what\n   order of importance?\n   What's the physical or screen format? Content hierarchy drives layout, never\nthe reverse.\n2. 2. 2. **Set up the grid.** Choose columns based on content complexity (2-3\n   for simple, up to 12 for\n   complex), set margins for the format (print needs more), establish a baseline\ngrid for text-heavy\n   work.\n3. 3. 3. **Block the hierarchy.** Before any styling: rough boxes showing\n   headline, key visual, body,\n   secondary info, CTA. Get the information architecture right in grayscale\nboxes.\n4. 4. 4. **Place the entry point.** The dominant element goes where the eye\n   lands first (top-left for\n   text cultures, center for visual pieces). Everything else supports or follows\nit.\n5. 5. 5. **Refine spacing.** Consistent spacing scale (4\u002F8\u002F16\u002F24\u002F32...), related\n   items grouped\n   (proximity = relationship), generous margins. Squint test: does the structure\nhold?\n6. 6. 6. **Check the details.** Alignment (everything aligns to something),\n   widows\u002Forphans in text,\n   image crops and captions, page numbers and running heads for documents, safe\nareas for print.\n7. 7. 7. **Review as a system.** For multi-page work: flip through quickly. Does\n   it feel like one\n   publication? Is there variety within consistency — or monotony?\n\n## Common pitfalls\n\n- - - **No clear hierarchy.** Everything similar in size and weight forces\n  readers to work out what's\n  important. That's the designer's job, not the reader's.\n- - - **Fear of whitespace.** Filling every corner because empty space feels\n  wasteful. Whitespace is\n  what makes the content legible and premium.\n- - - **Inconsistent alignment.** Elements almost-but-not-quite aligned — the\n  most common layout flaw.\n  Pick an edge and commit.\n- - - **Trapped whitespace.** Awkward gaps in the middle of layouts (often from\n  mismatched element\n  heights). Rebalance so space sits at edges, not stranded mid-page.\n- - - **Ignoring the gutter.** Content disappearing into book spines or getting\n  cropped at edges.\n  Respect margins and safe areas for the format.\n- - - **Template rigidity.** Using the same layout for every page\u002Fspread creates\n  monotony. Vary within\n  the system: full-bleed moments, quiet pages, asymmetric breaks — planned, not\nrandom.\n","## Overview\n\nLayout is the invisible architecture of design: the arrangement of elements that\nmakes content\nscannable, credible, and beautiful. Whether it's a magazine spread, a dashboard,\nor a poster, the\nsame principles apply — grid, hierarchy, rhythm, balance, and the deliberate use\nof space. This\nskill teaches layout as a systematic craft, not decoration.\n\n## When to use\n\n- Laying out editorial content (magazines, reports, books)\n\n- Designing posters, flyers, or marketing collateral\n\n- Structuring dashboards or data-dense interfaces\n\n- Improving a layout that feels cluttered or unbalanced\n\n- Setting up grid systems for multi-page documents\n\n## Core concepts\n\n- - - **The grid.** Columns, gutters, margins, and baselines create the\n  skeleton. A 12-column grid\n  handles most needs; the grid's job is consistency across pages and\nbreakpoints, not visible lines.\n- - - **Hierarchy: size, weight, position, color.** The eye enters at the\n  largest\u002Fboldest\u002Fmost\n  colorful element and follows the designed path. Every layout should have a\nclear entry point and a\n  clear next step.\n- - - **Rhythm and repetition.** Repeating spacing intervals, consistent image\n  treatments, and\n  recurring elements create rhythm — the visual equivalent of meter in poetry.\nRhythm makes\n  multi-page documents feel cohesive.\n- - - **Balance: symmetrical vs asymmetrical.** Symmetrical layouts feel stable\n  and formal;\n  asymmetrical layouts feel dynamic and modern. Both need visual weight\ndistributed deliberately — a\n  heavy element on one side needs counterweight.\n- - - **The fold and the scan.** People scan in F-patterns (text-heavy) or\n  Z-patterns (visual pages).\n  Put key information on the scan path; don't bury the headline below decorative\nelements.\n- - - **Breaking the grid.** Intentional grid-breaking creates emphasis — but it\n  only works when the\n  grid is otherwise respected. Random misalignment isn't \"breaking the grid,\"\nit's just\n  misalignment.\n\n## Practical workflow\n\n1. 1. 1. **Know the content and format.** What must be communicated, in what\n   order of importance?\n   What's the physical or screen format? Content hierarchy drives layout, never\nthe reverse.\n2. 2. 2. **Set up the grid.** Choose columns based on content complexity (2-3\n   for simple, up to 12 for\n   complex), set margins for the format (print needs more), establish a baseline\ngrid for text-heavy\n   work.\n3. 3. 3. **Block the hierarchy.** Before any styling: rough boxes showing\n   headline, key visual, body,\n   secondary info, CTA. Get the information architecture right in grayscale\nboxes.\n4. 4. 4. **Place the entry point.** The dominant element goes where the eye\n   lands first (top-left for\n   text cultures, center for visual pieces). Everything else supports or follows\nit.\n5. 5. 5. **Refine spacing.** Consistent spacing scale (4\u002F8\u002F16\u002F24\u002F32...), related\n   items grouped\n   (proximity = relationship), generous margins. Squint test: does the structure\nhold?\n6. 6. 6. **Check the details.** Alignment (everything aligns to something),\n   widows\u002Forphans in text,\n   image crops and captions, page numbers and running heads for documents, safe\nareas for print.\n7. 7. 7. **Review as a system.** For multi-page work: flip through quickly. Does\n   it feel like one\n   publication? Is there variety within consistency — or monotony?\n\n## Common pitfalls\n\n- - - **No clear hierarchy.** Everything similar in size and weight forces\n  readers to work out what's\n  important. That's the designer's job, not the reader's.\n- - - **Fear of whitespace.** Filling every corner because empty space feels\n  wasteful. Whitespace is\n  what makes the content legible and premium.\n- - - **Inconsistent alignment.** Elements almost-but-not-quite aligned — the\n  most common layout flaw.\n  Pick an edge and commit.\n- - - **Trapped whitespace.** Awkward gaps in the middle of layouts (often from\n  mismatched element\n  heights). Rebalance so space sits at edges, not stranded mid-page.\n- - - **Ignoring the gutter.** Content disappearing into book spines or getting\n  cropped at edges.\n  Respect margins and safe areas for the format.\n- - - **Template rigidity.** Using the same layout for every page\u002Fspread creates\n  monotony. Vary within\n  the system: full-bleed moments, quiet pages, asymmetric breaks — planned, not\nrandom.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-layout-designer",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill layout-designer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill layout-designer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill layout-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-layout-designer\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","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\u002FCSS, 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.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","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).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]