Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Add strategic color to features that are too monochromatic or lack visual interest.
Install I Colorize
$ npx skills add boussadjra/vuestrata --skill i-colorize -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boussadjra/vuestrata i-colorize --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/i-colorize .claude/skills/i-colorize && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "i-colorize" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorize into .claude/skills/i-colorize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-colorize", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorizeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boussadjra/vuestrata --skill i-colorize -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boussadjra/vuestrata i-colorize --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/i-colorize .agents/skills/i-colorize && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "i-colorize" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorize into .agents/skills/i-colorize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-colorize", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boussadjra/vuestrata --skill i-colorize -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boussadjra/vuestrata i-colorize --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/i-colorize .cursor/skills/i-colorize && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "i-colorize" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorize into .cursor/skills/i-colorize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-colorize", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boussadjra/vuestrata.git --path .github/skills/i-colorize--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boussadjra/vuestrata --skill i-colorize -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boussadjra/vuestrata i-colorize --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/i-colorize .gemini/skills/i-colorize && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "i-colorize" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorize into .gemini/skills/i-colorize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-colorize", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boussadjra/vuestrata i-colorizeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boussadjra/vuestrata --skill i-colorize -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/i-colorize .github/skills/i-colorize && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "i-colorize" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorize into .github/skills/i-colorize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-colorize", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boussadjra/vuestrata --skill i-colorize -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boussadjra/vuestrata i-colorize --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/i-colorize .opencode/skills/i-colorize && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "i-colorize" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-colorize into .opencode/skills/i-colorize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-colorize", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
i-colorize- GitHub stars
- 111
- Used in
- 4 other repos
- Token cost
- ~1.9k tokens
- SKILL.md length
- 939 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add strategic color to features that are too monochromatic or lack visual interest.
- Works in 2 steps: If you don't find exact information and… → Otherwise, if you can't fully infer or…
- Frontend & Design work in your project
- SKILL.md covers MANDATORY PREPARATION, Assess Color Opportunity, Plan Color Strategy and Introduce Color Strategically, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
I Colorize is an agent skill from boussadjra/vuestrata. Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. The repository describes itself as: A modern, production-ready Vue 3 template with multi-theme support, Reka UI wrappers, and enterprise-grade tooling. The licence is MIT.
When your agent uses it
- Frontend & Design work in your project
Example prompts
- “/i-colorize”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- If you don't find exact information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to…
- Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you…
What it can do on your machine
Read from SKILL.md and the folder at commit 73cbf9f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
I Colorize loads about 1.9k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 939 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from boussadjra/vuestrata at commit 73cbf9f, republished under its MIT licence (© boussadjra). 939 words, ~1,861 tokens.
Download SKILL.mdSave it as
.claude/skills/i-colorize/SKILL.md (or your agent's skills folder).- name
- i-colorize
- description
- Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
- user-invokable
- true
- argument-hint
- TARGET=<value>
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
MANDATORY PREPARATION
Context Gathering (Do This First)
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors.
Attempt to gather these from the current thread or codebase.
- If you don't find exact information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right.
- Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context.
Do NOT proceed until you have answers. Guessing leads to generic AI slop colors.
Use frontend-design skill
Use the i-frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.
Assess Color Opportunity
Analyze the current state and identify opportunities:
Understand current state:
- Color absence: Pure grayscale? Limited neutrals? One timid accent?
- Missed opportunities: Where could color add meaning, hierarchy, or delight?
- Context: What's appropriate for this domain and audience?
- Brand: Are there existing brand colors we should use?
Identify where color adds value:
- Semantic meaning: Success (green), error (red), warning (yellow/orange), info (blue)
- Hierarchy: Drawing attention to important elements
- Categorization: Different sections, types, or states
- Emotional tone: Warmth, energy, trust, creativity
- Wayfinding: Helping users navigate and understand structure
- Delight: Moments of visual interest and personality
If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
CRITICAL: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.
Plan Color Strategy
Create a purposeful color introduction plan:
- Color palette: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals)
- Dominant color: Which color owns 60% of colored elements?
- Accent colors: Which colors provide contrast and highlights? (30% and 10%)
- Application strategy: Where does each color appear and why?
IMPORTANT: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more.
Introduce Color Strategically
Add color systematically across these dimensions:
Semantic Color
State indicators:
- Success: Green tones (emerald, forest, mint)
- Error: Red/pink tones (rose, crimson, coral)
- Warning: Orange/amber tones
- Info: Blue tones (sky, ocean, indigo)
- Neutral: Gray/slate for inactive states
Status badges: Colored backgrounds or borders for states (active, pending, completed, etc.)
Progress indicators: Colored bars, rings, or charts showing completion or health
Accent Color Application
- Primary actions: Color the most important buttons/CTAs
- Links: Add color to clickable text (maintain accessibility)
- Icons: Colorize key icons for recognition and personality
- Headers/titles: Add color to section headers or key labels
- Hover states: Introduce color on interaction
Background & Surfaces
- Tinted backgrounds: Replace pure gray (
#f5f5f5) with warm neutrals (oklch(97% 0.01 60)) or cool tints (oklch(97% 0.01 250)) - Colored sections: Use subtle background colors to separate areas
- Gradient backgrounds: Add depth with subtle, intentional gradients (not generic purple-blue)
- Cards & surfaces: Tint cards or surfaces slightly for warmth
Use OKLCH for color: It's perceptually uniform, meaning equal steps in lightness look equal. Great for generating harmonious scales.
Data Visualization
- Charts & graphs: Use color to encode categories or values
- Heatmaps: Color intensity shows density or importance
- Comparison: Color coding for different datasets or timeframes
Show full SKILL.md (371 more words)Show less
Borders & Accents
- Accent borders: Add colored left/top borders to cards or sections
- Underlines: Color underlines for emphasis or active states
- Dividers: Subtle colored dividers instead of gray lines
- Focus rings: Colored focus indicators matching brand
Typography Color
- Colored headings: Use brand colors for section headings (maintain contrast)
- Highlight text: Color for emphasis or categories
- Labels & tags: Small colored labels for metadata or categories
Decorative Elements
- Illustrations: Add colored illustrations or icons
- Shapes: Geometric shapes in brand colors as background elements
- Gradients: Colorful gradient overlays or mesh backgrounds
- Blobs/organic shapes: Soft colored shapes for visual interest
Balance & Refinement
Ensure color addition improves rather than overwhelms:
Maintain Hierarchy
- Dominant color (60%): Primary brand color or most used accent
- Secondary color (30%): Supporting color for variety
- Accent color (10%): High contrast for key moments
- Neutrals (remaining): Gray/black/white for structure
Accessibility
- Contrast ratios: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components)
- Don't rely on color alone: Use icons, labels, or patterns alongside color
- Test for color blindness: Verify red/green combinations work for all users
Cohesion
- Consistent palette: Use colors from defined palette, not arbitrary choices
- Systematic application: Same color meanings throughout (green always = success)
- Temperature consistency: Warm palette stays warm, cool stays cool
NEVER:
- Use every color in the rainbow (choose 2-4 colors beyond neutrals)
- Apply color randomly without semantic meaning
- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead
- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication
- Use pure black (
#000) or pure white (#fff) for large areas - Violate WCAG contrast requirements
- Use color as the only indicator (accessibility issue)
- Make everything colorful (defeats the purpose)
- Default to purple-blue gradients (AI slop aesthetic)
Verify Color Addition
Test that colorization improves the experience:
- Better hierarchy: Does color guide attention appropriately?
- Clearer meaning: Does color help users understand states/categories?
- More engaging: Does the interface feel warmer and more inviting?
- Still accessible: Do all color combinations meet WCAG standards?
- Not overwhelming: Is color balanced and purposeful?
Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional.
© boussadjra, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/i-colorize of boussadjra/vuestrata.
Open the folder on GitHubat commit 73cbf9f
Used in 4 other repositories
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in boussadjra/vuestrata, which our catalogue first saw on October 7, 2026.
Compare with similar skills
I Colorize next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| I Colorize this skillboussadjra/vuestrata | 111 | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from boussadjra/vuestrata
All 21 skills in this repoI Delight
boussadjra/vuestrata
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use.
I Optimize
boussadjra/vuestrata
Improve interface performance across loading speed, rendering, animations, images, and bundle size.
I Frontend Design
boussadjra/vuestrata
Create distinctive, production-grade frontend interfaces with high design quality.
I Harden
boussadjra/vuestrata
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management.
I Onboard
boussadjra/vuestrata
Design or improve onboarding flows, empty states, and first-time user experiences.
I Teach Impeccable
boussadjra/vuestrata
One-time setup that gathers design context for your project and saves it to your AI config file.
Related
Categories
Questions about I Colorize
What does I Colorize do?
Add strategic color to features that are too monochromatic or lack visual interest. I Colorize is an agent skill from boussadjra/vuestrata. Add strategic color to features that are too monochromatic or lack visual interest.
When should I use I Colorize?
I Colorize fits situations like: frontend & Design work in your project.
How do I install I Colorize in Claude Code?
Run `npx skills add boussadjra/vuestrata --skill i-colorize -a claude-code`. Or copy the skill folder (.github/skills/i-colorize in boussadjra/vuestrata) into .claude/skills/i-colorize in your project. Claude Code loads it when a task matches its description.
How do I install I Colorize in Codex?
Run `npx skills add boussadjra/vuestrata --skill i-colorize -a codex`. Or copy the skill folder (.github/skills/i-colorize in boussadjra/vuestrata) into .agents/skills/i-colorize in your project. Codex loads it when a task matches its description.
Can I use I Colorize in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boussadjra/vuestrata --skill i-colorize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i-colorize, .gemini/skills/i-colorize, .github/skills/i-colorize and .opencode/skills/i-colorize in your project.
What does I Colorize need to run?
SKILL.md names no scripts, command-line tools or credentials: I Colorize is instructions for the agent only.
Does I Colorize access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is I Colorize safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does I Colorize use?
I Colorize is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does I Colorize use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to I Colorize?
Skills that share tags, products or a category with I Colorize: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains I Colorize?
boussadjra (a GitHub user) maintains it in boussadjra/vuestrata, which has 111 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 5, 2026.
Source: boussadjra/vuestrata on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.