[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN6QPHHRVXEXFFVAMK6K2C":3,"skill-same:01M7EN6QPHHRVXEXFFVAMK6K2C":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},"01M7EN6QPHHRVXEXFFVAMK6K2C","graphic-designer",null,"Create effective visual designs with strong composition, hierarchy, and typography across print and digital.","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-graphic-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: graphic-designer\ndescription: Create effective visual designs with strong composition, hierarchy, and typography across print and digital.\ncategory: creative-design\n---\n\n## Overview\n\nGraphic design is visual communication with intent: every poster, banner, deck,\nor social graphic\nexists to make someone understand, feel, or do something. This skill covers the\ncraft fundamentals —\ncomposition, hierarchy, typography, color — and the practical workflow from\nbrief to final files,\nfor both print and digital outputs.\n\n## When to use\n\n- Designing marketing materials, posters, banners, or decks\n\n- Creating social media graphics and campaign visuals\n\n- Laying out brochures, one-pagers, or reports\n\n- Improving an existing design that isn't landing\n\n- Preparing print-ready or web-ready design files\n\n## Core concepts\n\n- - - **Hierarchy answers three questions.** What's this? Why should I care?\n  What do I do next? Size,\n  weight, color, and position guide the eye through that sequence. If everything\nshouts, nothing is\n  heard.\n- - - **Grids create order.** Align elements to a consistent grid (even an\n  invisible one). Misaligned\n  elements read as mistakes even when viewers can't articulate why.\n- - - **Whitespace is a design element.** Empty space gives content room to\n  breathe and signals\n  importance. Crowded designs feel cheap; generous spacing feels premium.\n- - - **Typography does the heavy lifting.** Limit to 2 typefaces (one for\n  headlines, one for body)\n  with clear size\u002Fweight roles. Contrast between headline and body should be\nobvious at a glance.\n- - - **Color with purpose.** One dominant color, one accent, neutrals for the\n  rest. Color should\n  reinforce hierarchy and brand — decorative rainbow palettes dilute the\nmessage.\n- - - **Design for the context.** A billboard gets 3 seconds at 60mph; an\n  Instagram post gets 1 second\n  in a feed; a report gets sustained reading. Format, text density, and\nhierarchy all follow from\n  viewing context.\n\n## Practical workflow\n\n1. 1. 1. **Read the brief properly.** Audience, message (one sentence), action\n   desired, format\u002Fsize,\n   brand constraints, deadline. If the brief is vague, ask: what does success\nlook like?\n2. 2. 2. **Gather content first.** Final copy (or near-final) before layout.\n   Designing around\n   placeholder text guarantees rework.\n3. 3. 3. **Sketch 3 directions.** Thumbnails on paper or quick digital sketches:\n   different layouts,\n   different hierarchies. Pick the strongest concept, not the prettiest sketch.\n4. 4. 4. **Build the layout.** Grid, hierarchy, typography scale, color\n   application. Work at actual\n   size for print; design responsively for digital (how does it crop on\nmobile?).\n5. 5. 5. **Refine ruthlessly.** Alignment check (zoom out — does it hold\n   together?), typography check\n   (widows, orphans, awkward breaks), color check (contrast ratios for text),\nand the squint test\n   (squint — is the hierarchy still clear?).\n6. 6. 6. **Get feedback on the message.** Ask someone unfamiliar: \"what's this\n   about and what should I\n   do?\" If they can't answer in 5 seconds, the hierarchy failed — not the\nviewer.\n7. 7. 7. **Export correctly.** Print: CMYK, 300 DPI, bleed and crop marks,\n   outlined fonts. Digital:\n   RGB, correct pixel dimensions, optimized file sizes. Name files clearly with\nversion numbers.\n\n## Common pitfalls\n\n- - - **Too many fonts.** Three or more typefaces in one piece looks chaotic.\n  Two is the professional\n  default; one with weight variation often suffices.\n- - - **Center-aligning everything.** Centered text is harder to read and looks\n  amateur in body copy.\n  Left-align body text; reserve centering for short headlines and formal\ninvitations.\n- - - **Low-contrast text.** Gray text on light backgrounds or text over busy\n  images kills\n  readability. Check contrast; add overlays or solid panels behind text on\nphotos.\n- - - **Designing at the wrong size.** A poster designed at screen resolution\n  prints blurry; a web\n  banner designed at print size is a 50MB monster. Know the output before\nstarting.\n- - - **Ignoring the brand.** Off-brand colors, fonts, or tone undermine trust.\n  When no brand guide\n  exists, establish 3-4 rules yourself and follow them consistently.\n- - - **Falling for trends over function.** The trendy effect that obscures the\n  message is a failed\n  design. Trends are seasoning; clarity is the meal.\n","## Overview\n\nGraphic design is visual communication with intent: every poster, banner, deck,\nor social graphic\nexists to make someone understand, feel, or do something. This skill covers the\ncraft fundamentals —\ncomposition, hierarchy, typography, color — and the practical workflow from\nbrief to final files,\nfor both print and digital outputs.\n\n## When to use\n\n- Designing marketing materials, posters, banners, or decks\n\n- Creating social media graphics and campaign visuals\n\n- Laying out brochures, one-pagers, or reports\n\n- Improving an existing design that isn't landing\n\n- Preparing print-ready or web-ready design files\n\n## Core concepts\n\n- - - **Hierarchy answers three questions.** What's this? Why should I care?\n  What do I do next? Size,\n  weight, color, and position guide the eye through that sequence. If everything\nshouts, nothing is\n  heard.\n- - - **Grids create order.** Align elements to a consistent grid (even an\n  invisible one). Misaligned\n  elements read as mistakes even when viewers can't articulate why.\n- - - **Whitespace is a design element.** Empty space gives content room to\n  breathe and signals\n  importance. Crowded designs feel cheap; generous spacing feels premium.\n- - - **Typography does the heavy lifting.** Limit to 2 typefaces (one for\n  headlines, one for body)\n  with clear size\u002Fweight roles. Contrast between headline and body should be\nobvious at a glance.\n- - - **Color with purpose.** One dominant color, one accent, neutrals for the\n  rest. Color should\n  reinforce hierarchy and brand — decorative rainbow palettes dilute the\nmessage.\n- - - **Design for the context.** A billboard gets 3 seconds at 60mph; an\n  Instagram post gets 1 second\n  in a feed; a report gets sustained reading. Format, text density, and\nhierarchy all follow from\n  viewing context.\n\n## Practical workflow\n\n1. 1. 1. **Read the brief properly.** Audience, message (one sentence), action\n   desired, format\u002Fsize,\n   brand constraints, deadline. If the brief is vague, ask: what does success\nlook like?\n2. 2. 2. **Gather content first.** Final copy (or near-final) before layout.\n   Designing around\n   placeholder text guarantees rework.\n3. 3. 3. **Sketch 3 directions.** Thumbnails on paper or quick digital sketches:\n   different layouts,\n   different hierarchies. Pick the strongest concept, not the prettiest sketch.\n4. 4. 4. **Build the layout.** Grid, hierarchy, typography scale, color\n   application. Work at actual\n   size for print; design responsively for digital (how does it crop on\nmobile?).\n5. 5. 5. **Refine ruthlessly.** Alignment check (zoom out — does it hold\n   together?), typography check\n   (widows, orphans, awkward breaks), color check (contrast ratios for text),\nand the squint test\n   (squint — is the hierarchy still clear?).\n6. 6. 6. **Get feedback on the message.** Ask someone unfamiliar: \"what's this\n   about and what should I\n   do?\" If they can't answer in 5 seconds, the hierarchy failed — not the\nviewer.\n7. 7. 7. **Export correctly.** Print: CMYK, 300 DPI, bleed and crop marks,\n   outlined fonts. Digital:\n   RGB, correct pixel dimensions, optimized file sizes. Name files clearly with\nversion numbers.\n\n## Common pitfalls\n\n- - - **Too many fonts.** Three or more typefaces in one piece looks chaotic.\n  Two is the professional\n  default; one with weight variation often suffices.\n- - - **Center-aligning everything.** Centered text is harder to read and looks\n  amateur in body copy.\n  Left-align body text; reserve centering for short headlines and formal\ninvitations.\n- - - **Low-contrast text.** Gray text on light backgrounds or text over busy\n  images kills\n  readability. Check contrast; add overlays or solid panels behind text on\nphotos.\n- - - **Designing at the wrong size.** A poster designed at screen resolution\n  prints blurry; a web\n  banner designed at print size is a 50MB monster. Know the output before\nstarting.\n- - - **Ignoring the brand.** Off-brand colors, fonts, or tone undermine trust.\n  When no brand guide\n  exists, establish 3-4 rules yourself and follow them consistently.\n- - - **Falling for trends over function.** The trendy effect that obscures the\n  message is a failed\n  design. Trends are seasoning; clarity is the meal.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-graphic-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 graphic-designer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill graphic-designer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill graphic-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-graphic-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",[],[]]