[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMM6E8JTW9JSWZV573APQ7":3,"skill-same:01M7EMM6E8JTW9JSWZV573APQ7":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},"01M7EMM6E8JTW9JSWZV573APQ7","color-theory",null,"Apply color theory with palette building, harmony, psychology, contrast, and accessibility standards.","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-color-theory\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: color-theory\ndescription: Apply color theory with palette building, harmony, psychology, contrast, and accessibility standards.\ncategory: creative-design\n---\n\n## Overview\n\nColor is the fastest emotional signal in design — processed before words, before layout, before\nmeaning. Used well, it guides attention, encodes meaning, and makes brands unforgettable. Used\ncarelessly, it confuses and excludes. This skill covers color theory fundamentals, palette\nconstruction, psychological and cultural dimensions, and accessibility requirements.\n\n## When to use\n\n- Building a color palette for a brand or product\n\n- Choosing UI colors (actions, states, feedback, data visualization)\n\n- Fixing color contrast and accessibility issues\n\n- Understanding color psychology for marketing or branding\n\n- Reviewing designs for color harmony and consistency\n\n## Core concepts\n\n- - **The HSB mental model.** Hue (which color), Saturation (intensity), Brightness (light\u002Fdark).\n  Professionals think in HSB: harmonious palettes share saturation\u002Fbrightness relationships even\n  when hues differ.\n- - **Harmony structures.** Complementary (opposites — high energy), analogous (neighbors — calm,\n  cohesive), triadic (three equidistant — vibrant but balanced), monochromatic (one hue — elegant,\n  safe). Pick one structure per palette; don't mix structures.\n- - **The 60-30-10 rule.** 60% dominant neutral\u002Fbackground, 30% secondary, 10% accent. The accent is\n  precious — spend it on the one thing that matters most (the CTA, the alert).\n- - **Color has jobs.** In UI: brand expression, hierarchy (what's important), state\n  (success\u002Ferror\u002Fwarning\u002Finfo), and data encoding. Assign each color a job; a color doing three jobs\n  is doing none well.\n- - **Psychology is contextual.** Blue = trust (finance, tech), red = urgency (sales, errors), green\n  = go\u002Fsuccess — but culture and context modulate everything (red means luck in China, mourning in\n  parts of Africa). Know your audience.\n- - **Accessibility is math.** WCAG: 4.5:1 contrast for normal text, 3:1 for large text and UI\n  components. Never encode meaning in color alone — pair with icons, labels, or patterns (8% of men\n  have color vision deficiency).\n\n## Practical workflow\n\n1. 1. **Define color's jobs.** List what color must do: brand recognition, primary actions, feedback\n   states, data categories, backgrounds. Each job gets a dedicated color family.\n2. 2. **Start with neutrals.** Build the grayscale\u002Framp first — most of any interface is neutrals. A\n   refined neutral scale (with subtle warmth or coolness) elevates the whole design.\n3. 3. **Choose the primary.** The brand\u002Faction color: distinctive in the competitive landscape,\n   works at large and small sizes, passes contrast on its backgrounds. Test it as a button, a link,\n   and a background.\n4. 4. **Build the supporting palette.** Secondary colors, semantic colors\n   (success\u002Fwarning\u002Ferror\u002Finfo — test these for CVD distinguishability), and data visualization\n   palette (categorical: distinct hues; sequential: single-hue lightness steps).\n5. 5. **Check contrast systematically.** Every text\u002Fbackground and UI\u002Fbackground combination against\n   WCAG ratios. Fix failures by adjusting lightness, not by hoping.\n6. 6. **Test in context.** View the palette applied to real screens, in light and dark mode, and\n   through color-blindness simulators (deuteranopia, protanopia, tritanopia). Print a swatch sheet —\n   screens lie.\n7. 7. **Document with values.** Hex, RGB, and HSL\u002FHSB for each color; usage rules (when to use\n   which); don'ts. Name semantically for UI (surface, action, critical) so the palette survives\n   rebrands.\n\n## Common pitfalls\n\n- - **Rainbow interfaces.** Too many saturated colors competing. Restraint reads as premium; rainbow\n  reads as carnival.\n- - **Pure black and pure white.** #000 on #FFF causes halation and eye strain. Use off-blacks\n  (#111-#1a1a1a) and let backgrounds breathe.\n- - **Color-only meaning.** Red\u002Fgreen status dots with no labels exclude color-blind users. Always\n  add a second channel: icon, text, or pattern.\n- - **Inaccessible text.** Light gray body text on white — the most common accessibility failure on\n  the web. Check every combination, not just the obvious ones.\n- - **Gradients as a crutch.** Gradient backgrounds hiding weak composition or low-contrast text.\n  Gradients are fine as accents; they're not a substitute for hierarchy.\n- - **Ignoring dark mode.** Designing only for light and letting dark mode be an afterthought\n  produces muddy, low-contrast dark themes. Design both deliberately from the token level.\n","## Overview\n\nColor is the fastest emotional signal in design — processed before words, before layout, before\nmeaning. Used well, it guides attention, encodes meaning, and makes brands unforgettable. Used\ncarelessly, it confuses and excludes. This skill covers color theory fundamentals, palette\nconstruction, psychological and cultural dimensions, and accessibility requirements.\n\n## When to use\n\n- Building a color palette for a brand or product\n\n- Choosing UI colors (actions, states, feedback, data visualization)\n\n- Fixing color contrast and accessibility issues\n\n- Understanding color psychology for marketing or branding\n\n- Reviewing designs for color harmony and consistency\n\n## Core concepts\n\n- - **The HSB mental model.** Hue (which color), Saturation (intensity), Brightness (light\u002Fdark).\n  Professionals think in HSB: harmonious palettes share saturation\u002Fbrightness relationships even\n  when hues differ.\n- - **Harmony structures.** Complementary (opposites — high energy), analogous (neighbors — calm,\n  cohesive), triadic (three equidistant — vibrant but balanced), monochromatic (one hue — elegant,\n  safe). Pick one structure per palette; don't mix structures.\n- - **The 60-30-10 rule.** 60% dominant neutral\u002Fbackground, 30% secondary, 10% accent. The accent is\n  precious — spend it on the one thing that matters most (the CTA, the alert).\n- - **Color has jobs.** In UI: brand expression, hierarchy (what's important), state\n  (success\u002Ferror\u002Fwarning\u002Finfo), and data encoding. Assign each color a job; a color doing three jobs\n  is doing none well.\n- - **Psychology is contextual.** Blue = trust (finance, tech), red = urgency (sales, errors), green\n  = go\u002Fsuccess — but culture and context modulate everything (red means luck in China, mourning in\n  parts of Africa). Know your audience.\n- - **Accessibility is math.** WCAG: 4.5:1 contrast for normal text, 3:1 for large text and UI\n  components. Never encode meaning in color alone — pair with icons, labels, or patterns (8% of men\n  have color vision deficiency).\n\n## Practical workflow\n\n1. 1. **Define color's jobs.** List what color must do: brand recognition, primary actions, feedback\n   states, data categories, backgrounds. Each job gets a dedicated color family.\n2. 2. **Start with neutrals.** Build the grayscale\u002Framp first — most of any interface is neutrals. A\n   refined neutral scale (with subtle warmth or coolness) elevates the whole design.\n3. 3. **Choose the primary.** The brand\u002Faction color: distinctive in the competitive landscape,\n   works at large and small sizes, passes contrast on its backgrounds. Test it as a button, a link,\n   and a background.\n4. 4. **Build the supporting palette.** Secondary colors, semantic colors\n   (success\u002Fwarning\u002Ferror\u002Finfo — test these for CVD distinguishability), and data visualization\n   palette (categorical: distinct hues; sequential: single-hue lightness steps).\n5. 5. **Check contrast systematically.** Every text\u002Fbackground and UI\u002Fbackground combination against\n   WCAG ratios. Fix failures by adjusting lightness, not by hoping.\n6. 6. **Test in context.** View the palette applied to real screens, in light and dark mode, and\n   through color-blindness simulators (deuteranopia, protanopia, tritanopia). Print a swatch sheet —\n   screens lie.\n7. 7. **Document with values.** Hex, RGB, and HSL\u002FHSB for each color; usage rules (when to use\n   which); don'ts. Name semantically for UI (surface, action, critical) so the palette survives\n   rebrands.\n\n## Common pitfalls\n\n- - **Rainbow interfaces.** Too many saturated colors competing. Restraint reads as premium; rainbow\n  reads as carnival.\n- - **Pure black and pure white.** #000 on #FFF causes halation and eye strain. Use off-blacks\n  (#111-#1a1a1a) and let backgrounds breathe.\n- - **Color-only meaning.** Red\u002Fgreen status dots with no labels exclude color-blind users. Always\n  add a second channel: icon, text, or pattern.\n- - **Inaccessible text.** Light gray body text on white — the most common accessibility failure on\n  the web. Check every combination, not just the obvious ones.\n- - **Gradients as a crutch.** Gradient backgrounds hiding weak composition or low-contrast text.\n  Gradients are fine as accents; they're not a substitute for hierarchy.\n- - **Ignoring dark mode.** Designing only for light and letting dark mode be an afterthought\n  produces muddy, low-contrast dark themes. Design both deliberately from the token level.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-color-theory",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 color-theory",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill color-theory",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill color-theory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-color-theory\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",[],[]]