article-illustrations
Generate hand-drawn 16:9 article illustrations with the Grav character IP, sparse annotations, and absurd but clear visual metaphors.
Best use case
article-illustrations is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate hand-drawn 16:9 article illustrations with the Grav character IP, sparse annotations, and absurd but clear visual metaphors.
Teams using article-illustrations should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/article-illustrations/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How article-illustrations Compares
| Feature / Agent | article-illustrations | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate hand-drawn 16:9 article illustrations with the Grav character IP, sparse annotations, and absurd but clear visual metaphors.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Article Illustrations — Grav Hand-Drawn Style ## Overview Generate 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](https://github.com/vipin-si/article-illustrations) ## When to Use This Skill - Use when writing articles, blog posts, or documentation that need inline illustrations - Use when you want to turn abstract concepts into concrete visual metaphors - Use when you want a consistent visual language across multiple articles - Use when you need hand-drawn explanation sketches, not PPT infographics ## How It Works ### Step 1: Digest the Article 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. ### Step 2: Plan a Shot List For each illustration, define: - **Placement**: After which section - **Theme**: What this image is about - **Core Meaning**: The one idea it conveys - **Structure Type**: One of 8 composition patterns (Workflow, System Closeup, Before/After, Role States, Conceptual Metaphor, Layered Method, Map Route, Mini Comic) - **Grav's Action**: What Grav is doing in the scene - **Annotation Labels**: 3–5 short English labels ### Step 3: Generate Images Use the `generate_image` tool with the built-in prompt template. Each image follows strict style rules: - Pure white background, no textures - Black hand-drawn line art with slight wobble - Sparse red/orange/blue handwritten annotations - Grav always floating (never touching surfaces) - One core idea per image - 40–60% canvas usage, 35%+ whitespace ### Step 4: QA Check Verify each image against the QA checklist: correct format, Grav present and active, original metaphor, clean composition, sparse annotations, correct color usage. ## Examples ### Example 1: Plan illustrations for an article ``` 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> ``` ### Example 2: Generate illustrations directly ``` 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> ``` ### Example 3: Single concept illustration ``` 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. ``` ### Example 4: Iterate on a result ``` 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. ``` ## Visual Style | 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 | ## Character: Grav - Small round body (pebble/potato shape) - Two dot eyes (slightly asymmetric) - One thin bent antenna with tiny circle tip - Thin stick legs that dangle without touching surfaces - Always hovering — visible gap between Grav and any surface - Expression: calm, focused, deadpan - Role: active participant in the system, never decoration ## Best Practices - ✅ Start with a shot list before generating images - ✅ Invent a new metaphor for every illustration — never reuse compositions - ✅ Make Grav the action protagonist, not a bystander - ✅ Keep it absurd but structurally clear - ✅ Use color sparingly — when in doubt, use black - ❌ Don't make PPT infographics or formal flowcharts - ❌ Don't add title bars or decorative frames - ❌ Don't let Grav touch the ground or stand on surfaces - ❌ Don't make Grav cute, smiling, or emoji-like ## Limitations - Requires access to an image-generation tool that can follow composition, line-art, and annotation constraints. - The recurring Grav character style can drift between generations; verify every output against the QA checklist. - Text in generated images may be misspelled or distorted, so short labels and post-generation review are required. - The style is intended for explanatory article illustrations, not photorealistic product imagery or brand-final artwork. ## Common Pitfalls - **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 ## Additional Resources - [Full skill with prompt templates and QA checklist](https://github.com/vipin-si/article-illustrations) - [Example illustrations](https://github.com/vipin-si/article-illustrations#examples)
Related Skills
x-article-publisher-skill
Publish articles to X/Twitter
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zipai-optimizer
Ultra-dense token optimizer skill for prompt caching, log pruning, AST-based inspection, and minified JSON payloads.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
zapier-make-patterns
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.
youtube-summarizer
Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks
youtube-full
Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.
youtube-automation
Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.