.claude/skills/cover-image/SKILL.md
Generate elegant cover images for articles. Analyzes content and creates eye-catching hand-drawn style cover images with multiple style options. Use when user asks to "generate cover image", "create article cover", or "make a cover for article".
npx skillsauth add shalevamin/The-_Ultimate_agents cover-imageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate hand-drawn style cover images for articles with multiple style options.
# From markdown file (auto-select style based on content)
/cover-image path/to/article.md
# Specify a style
/cover-image path/to/article.md --style blueprint
/cover-image path/to/article.md --style warm
/cover-image path/to/article.md --style dark-atmospheric
# Without title text
/cover-image path/to/article.md --no-title
# Combine options
/cover-image path/to/article.md --style minimal --no-title
# From direct text input
/cover-image
[paste content or describe topic]
# Direct input with style
/cover-image --style playful
[paste content]
| Option | Description |
|--------|-------------|
| --style <name> | Specify cover style (see Style Gallery below) |
| --aspect <ratio> | Aspect ratio: 2.35:1 (cinematic, default), 16:9 (widescreen), 1:1 (social) |
| --lang <code> | Output language for title text (en, zh, ja, etc.) |
| --no-title | Generate cover without title text (visual only) |
| Style | Description |
|-------|-------------|
| elegant (Default) | Refined, sophisticated, understated |
| flat-doodle | Bold outlines, pastel colors, cute rounded shapes |
| blueprint | Technical schematics, engineering precision |
| bold-editorial | Magazine cover impact, dramatic typography |
| chalkboard | Black chalkboard, colorful chalk drawings |
| dark-atmospheric | Cinematic dark mode, glowing accents |
| editorial-infographic | Magazine explainer, visual storytelling |
| fantasy-animation | Ghibli/Disney inspired, whimsical charm |
| intuition-machine | Technical briefing, bilingual labels |
| minimal | Ultra-clean, zen-like, focused |
| nature | Organic, calm, earthy |
| notion | Clean SaaS dashboard, productivity styling |
| pixel-art | Retro 8-bit, nostalgic gaming aesthetic |
| playful | Fun, creative, whimsical |
| retro | Halftone dots, vintage badges, classic |
| sketch-notes | Hand-drawn, educational, warm |
| vector-illustration | Flat vector, black outlines, retro colors |
| vintage | Aged paper, historical, expedition style |
| warm | Friendly, approachable, human-centered |
| watercolor | Soft hand-painted, natural warmth |
Detailed style definitions: references/styles/<style>.md
When no --style is specified, system analyzes content to select best style:
| Content Signals | Selected Style |
|----------------|----------------|
| Architecture, system design, engineering | blueprint |
| Product launch, keynote, marketing, brand | bold-editorial |
| Education, classroom, tutorial, teaching | chalkboard |
| Entertainment, creative, premium, cinematic | dark-atmospheric |
| Technology explainer, science, research | editorial-infographic |
| Storytelling, children, fantasy, magical | fantasy-animation |
| Technical docs, academic, bilingual | intuition-machine |
| Personal story, emotion, growth, life | warm |
| Simple, zen, focus, essential | minimal |
| Fun, easy, beginner, casual | playful |
| Nature, eco, wellness, health, organic | nature |
| Pop culture, 80s/90s nostalgia, badges | retro |
| Product, SaaS, dashboard, productivity | notion |
| Productivity, workflow, app, tools, cute | flat-doodle |
| Gaming, retro tech, developer, 8-bit | pixel-art |
| Educational, tutorial, knowledge sharing | sketch-notes |
| Creative proposals, brand, toy-like | vector-illustration |
| History, exploration, heritage, biography | vintage |
| Lifestyle, travel, food, personal | watercolor |
| Business, professional, strategy, analysis | elegant |
Each session creates an independent directory named by content slug:
cover-image/{topic-slug}/
├── source-{slug}.{ext} # Source files (text, images, etc.)
├── prompts/
│ └── cover.md
└── cover.png
Slug Generation:
future-of-aiIf cover-image/{topic-slug}/ already exists:
{topic-slug}-YYYYMMDD-HHMMSSai-future exists → ai-future-20260118-143052Copy all sources with naming source-{slug}.{ext}:
source-article.md (main text content)source-logo.png (image from conversation)Multiple sources supported: text, images, files from conversation.
Save source content (if not already a file):
source.md in target directoryExtract key information:
Language detection:
Style selection:
--style specified, use that styleelegant if no clear signalsAspect ratio:
--aspect specified, use that ratioPurpose: Let user confirm all options in a single step before generation.
IMPORTANT: Present ALL options in a single confirmation step using AskUserQuestion. Do NOT interrupt workflow with multiple separate confirmations.
Determine which questions to ask:
| Question | When to Ask |
|----------|-------------|
| Style | Always (required) |
| Aspect ratio | Always (offer common options) |
| Language | Only if source_language ≠ user_language |
Present options (use AskUserQuestion with all applicable questions):
Question 1 (Style) - always:
Question 2 (Aspect) - always:
Question 3 (Language) - only if source ≠ user language:
Language handling:
Create a cover image concept based on selected style:
Title (if included, max 8 characters):
--no-title flag is usedVisual Elements:
Save prompt to prompts/cover.md with confirmed options.
All prompts are written in the user's confirmed language preference.
Prompt Format:
Cover theme: [topic in 2-3 words]
Style: [selected style name]
Aspect ratio: [confirmed aspect ratio]
[If title included:]
Title text: [8 characters or less, in confirmed language]
Subtitle: [optional, in confirmed language]
Visual composition:
- Main visual: [description matching style]
- Layout: [positioning based on title inclusion and aspect ratio]
- Decorative elements: [style-appropriate elements]
Color scheme:
- Primary: [style primary color]
- Background: [style background color]
- Accent: [style accent color]
Style notes: [specific style characteristics to emphasize]
[If no title:]
Note: No title text, pure visual illustration only.
Image Generation Skill Selection:
Generation: Call selected image generation skill with prompt file, output path, and confirmed aspect ratio.
Cover Image Generated!
Topic: [topic]
Style: [style name]
Aspect: [aspect ratio]
Title: [cover title] (or "No title - visual only")
Language: [confirmed language]
Location: [output path]
Preview the image to verify it matches your expectations.
Custom styles and configurations via EXTEND.md.
Check paths (priority order):
.content-gen-skills/cover-image/EXTEND.md (project)~/.content-gen-skills/cover-image/EXTEND.md (user)If found, load before Step 1. Extension content overrides defaults.
development
Use when building cross-platform applications with Flutter 3+ and Dart. Invoke for widget development, Riverpod/Bloc state management, GoRouter navigation, platform-specific implementations, performance optimization.
testing
Use when fine-tuning LLMs, training custom models, or adapting foundation models for specific tasks. Invoke for configuring LoRA/QLoRA adapters, preparing JSONL training datasets, setting hyperparameters for fine-tuning runs, adapter training, transfer learning, finetuning with Hugging Face PEFT, OpenAI fine-tuning, instruction tuning, RLHF, DPO, or quantizing and deploying fine-tuned models. Trigger terms include: LoRA, QLoRA, PEFT, finetuning, fine-tuning, adapter tuning, LLM training, model training, custom model.
tools
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
tools
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.