Generate hand-drawn 16:9 article illustrations with the Grav character IP, sparse annotations, and absurd but clear visual metaphors.
5cf4dfeGenerate 16:9 landscape hand-drawn illustrations for articles, blog posts, and technical content. Each illustration captures one cognitive anchor point from an article and turns it into a clean, absurd, memorable whiteboard-sketch explanation.
The skill uses a recurring character IP called Grav: a small, round, always-floating figure with dot eyes and a thin antenna. Grav participates in the core action of every illustration — never just decoration.
Repository: vipin-si/article-illustrations
Read the article and identify cognitive anchor points — core judgments, turning points, input/output loops, before/after contrasts, and common pitfalls. Don't distribute illustrations evenly; prioritize moments that benefit from visual explanation.
For each illustration, define:
Use the generate_image tool with the built-in prompt template. Each image follows strict style rules:
Verify each image against the QA checklist: correct format, Grav present and active, original metaphor, clean composition, sparse annotations, correct color usage.
Analyze this article and create a shot list of 5 illustrations.
Don't generate images yet — just plan which cognitive anchor points
deserve illustrations and what each image should convey.
<paste article>
Generate 4 Grav-style illustrations for this article.
Requirements: 16:9 landscape, pure white background, black hand-drawn
line art, sparse red/orange/blue English annotations.
<paste article>
Generate one 16:9 illustration for this concept:
"Trust isn't declared — it's built one piece of evidence at a time."
Grav must perform the core action. Maximum 5 annotation labels.
This illustration is on the right track, but Grav feels like decoration.
Keep the core meaning but regenerate: make Grav the one actually
driving the structure.
| Element | Rule | |:--------|:-----| | Background | Pure white — no cream, texture, gradients, or shadows | | Line art | Black, hand-drawn, slightly wobbly, not mechanical | | Whitespace | Main subject 40–60% of canvas, 35%+ empty space | | Annotations | Handwritten English, 2–5 words each, max 5–8 per image | | Color: Black | Main line art, characters, structures, objects | | Color: Red | Key highlights, problems, warnings, results | | Color: Orange | Main flow, paths, arrows, direction | | Color: Blue | Supplementary notes, feedback, system state | | Prohibited | Green, purple, yellow, pink, gradients, drop shadows, 3D, realistic UI |
Problem: Illustration looks like a PPT slide Solution: Remove 30% of elements, increase whitespace, make it weirder
Problem: Grav is just standing next to the action Solution: Redesign so Grav IS the mechanism — becomes the funnel, dangles from the lever, is suspended inside the machine
Problem: Same metaphor as a previous illustration Solution: Replace the physical object entirely — same concept, different analogy
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/article-illustrations · pinned to the source commit
# Run from your project root
git clone https://github.com/sickn33/agentic-awesome-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 5cf4dfeb13ea966daa1e117897689cd7991e3f44
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/agentic-awesome-skills-claude/skills/article-illustrations" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/sickn33/agentic-awesome-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 5cf4dfeb13ea966daa1e117897689cd7991e3f44
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/agentic-awesome-skills-claude/skills/article-illustrations" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/article-illustrations
Scanner static-checks@0.1.0 · commit 5cf4dfeb13ea. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.