Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Illustrator

ASecurity

Create custom illustrations with consistent style, composition, and narrative for brands and products.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill illustrator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Illustrator?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Illustrator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-illustrator/badge)](https://www.skillsdirectory.com/skills/aicodedecode-illustrator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: illustrator
description: Create custom illustrations with consistent style, composition, and narrative for brands and products.
category: creative-design
---

## Overview

Custom illustration gives brands a visual voice stock imagery never can:
distinctive, ownable, and
emotionally precise. This skill covers illustration for product and brand
contexts — developing a
consistent style, composing scenes that communicate, and building illustration
systems that scale
across a team or product.

## When to use

- Developing an illustration style for a brand or product

- Creating spot illustrations, hero art, or editorial images

- Building an illustration library or system

- Briefing and art-directing illustrators

- Choosing between custom illustration and stock/AI imagery

## Core concepts

- - - **Style is a set of decisions.** Every illustration style is defined by:
  line (weight, presence,
  quality), shape language (geometric vs organic), color (palette size, flat vs
gradient), texture,
  perspective, and character proportions. Document these and the style becomes
repeatable.
- - - **Concept before rendering.** The idea carries the illustration.
  Thumbnails exploring 3-5
  concepts beat one beautifully rendered obvious idea. What's the visual
metaphor? What's the story
  in one frame?
- - - **Composition guides the eye.** Rule of thirds, leading lines, focal point
  with supporting
  elements, generous negative space. The viewer should land on the key element
in under 2 seconds.
- - - **Consistency across pieces.** Same line weights, same palette, same
  character construction,
  same level of detail. An illustration library where each piece looks like a
different artist is a
  failed system.
- - - **Spot vs scene vs hero.** Spot illustrations (small, simple, one idea)
  for UI empty states and
  accents; scenes for storytelling; hero art for emotional impact. Match
complexity to context — UI
  spots must read at small sizes.
- - - **Inclusive representation.** Diverse skin tones, body types, ages,
  abilities, and contexts —
  done thoughtfully, not as tokenism. Build diversity into character libraries
from the start.

## Practical workflow

1. 1. 1. **Define the style.** Based on brand personality: choose the
   line/shape/color/texture
   decisions. Create 2-3 style explorations at different complexity levels; pick
one and document
   the rules.
2. 2. 2. **Build the foundations.** Color palette (limited — 5-8 colors),
   character construction guides
   (proportions, faces, poses), common objects and environments. These are the
system's atoms.
3. 3. 3. **Thumbnail concepts.** For each brief: 3-5 rough thumbnails exploring
   different metaphors and
   compositions. Get concept approval before rendering — reworking a sketch
takes minutes, reworking
   finals takes days.
4. 4. 4. **Refine the chosen direction.** Tight sketch → color → detail. Check
   at actual usage size
   throughout (that hero will also appear as a thumbnail).
5. 5. 5. **Build the library.** Organize by category (people, objects, scenes,
   spots), with consistent
   naming. Include variations (skin tones, poses) where the system supports it.
6. 6. 6. **Write usage guidelines.** Where illustrations go, sizing rules, what
   not to do (don't
   stretch, don't recolor, don't combine styles), and how to request new pieces.
7. 7. 7. **Plan for scale.** Template files, documented styles, and either
   training for team members or
   a clear briefing process for external illustrators.

## Common pitfalls

- - - **Style drift.** Each new illustration subtly different until the library
  is incoherent. The
  style guide exists to prevent this — enforce it.
- - - **Over-detailing small illustrations.** Intricate scenes that become mud
  at UI sizes. Design
  spots to read at 48px; simplify ruthlessly.
- - - **The generic tech illustration.** Faceless purple people floating with
  oversized phones — the
  cliché of the 2020s. If your illustrations are interchangeable with every SaaS
company, the style
  has failed its job.
- - - **No concept.** Pretty rendering of an obvious or confusing idea. Spend
  half the time on what to
  draw, not how.
- - - **Inconsistent characters.** Same "character" with different proportions
  across pieces breaks
  believability. Construction guides aren't optional.
- - - **Ignoring context.** A detailed hero illustration crammed into a 200px
  card, or a tiny spot
  lost on a full-bleed page. Design for the actual placement.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →