agentleFS
markmhendricksonmarkmhendrickson/neotoma/.claude/skills/draft-illustration/SKILL.md

draft-illustration

Skill38 starsChanged 2 months agoMITView on GitHub

Blog Post Visual Style (Cross-Repo)

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill whenever you create or generate hero images, OG/social preview images, or any post artwork so that assets have the same …

    line 26
  2. Distinctive:

    All hero and post imagery MUST follow this style.

    line 30
  3. Distinctive:

    When generating a new hero or post image, use a prompt that enforces the style.

    line 48
  4. Distinctive:

    All three must share the same visual style (black background, white line-art, no typography).

    line 68
  5. Very specific:

    If the repo has no docs, apply only the Visual style (mandatory) and use sensible paths (e.g.

    line 80
  6. Very specific:

    Add layout hint: when the repo uses it (e.g.

    line 86
  7. Distinctive:

    Do not: add text, logos, or colors that break the black-background / white-line-art rule.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Source: foundation/.cursor/skills/draft-illustration/SKILL.md -->

name: draft-illustration description: Apply consistent visual style for blog post hero and social images across repos. Use when creating or generating hero images, OG images, or post artwork so all assets share the same look. triggers:

  • draft illustration
  • blog post image
  • hero image
  • post visual style
  • hero style
  • OG image
  • create post image
  • same visual style
  • draft-illustration
  • /draft-illustration

Blog Post Visual Style (Cross-Repo)

Use this skill whenever you create or generate hero images, OG/social preview images, or any post artwork so that assets have the same visual style across repositories. The style is mandatory for blog/post imagery; repo-specific paths and scripts are documented per project.

Visual style (mandatory)

All hero and post imagery MUST follow this style. Apply it when prompting image generation (e.g. GenerateImage, DALL·E, Midjourney) or when briefing a designer.

Visual rules:

RuleRequirement
BackgroundSolid black only. No gradients, no white sections, no mixed backgrounds.
ForegroundWhite line-art. Subtle edge shading for dimensionality is encouraged; large filled areas and color gradients are not.
Line workPolished, refined white outlines with consistent stroke weight. Lines should feel engraved or blueprint-quality — smooth curves, clean joints, slight dimensional depth on edges. Not sketchy or rough.
ColorMonochromatic black and white only. No gray tones or other colors outside of subtle edge shading for depth.
CompositionScene-based or centered. Objects may sit on surfaces with perspective (e.g. an angled desk, a platform). Generous negative (black) space around the subject.
AestheticPolished, dimensional, iconic. Technical engraving or refined blueprint feel. Not flat/clip-art, not photorealistic. Symbolic objects should feel like they have weight and presence.
TypographyNone. No text, labels, or captions within the image.

Focal brand: When the post is about a specific product or brand (e.g. Notion, Claude, OpenAI), focus the hero on that brand using recognizable shapes or motifs in the same white line-art style. No logos or wordmarks; the image should read as "this post is about X" at a glance.

Prompt template for image generation

When generating a new hero or post image, use a prompt that enforces the style. Example structure:

[Subject or theme]. Pure black background. White line-art with polished, refined outlines and subtle edge shading for dimensionality. Engraving or blueprint quality — smooth curves, clean joints, slight depth on edges. Objects may sit on a surface with perspective. Iconic, symbolic, not photorealistic. No text or labels. Generous negative (black) space around the subject.

Replace [Subject or theme] with the post topic (e.g. "Agent memory and a source of truth", "Three robot faces in wax-seal stamps on a desk", "Calendar grid connected to a mesh network").

Style references: know-which-of-your-agents-wrote-what-hero.png (wax seals with dimensional depth on angled desk), the-argument-cagan-already-won-hero.png (geometric Atlas figure with polished wireframe).

Asset variants (when a repo supports them)

Some repos (e.g. markmhendrickson website) expect multiple composed assets from the same style. Create separate compositions for each aspect ratio; do not just crop one image.

AssetAspectTypical use
HeroFlexible (keep-proportions)Full-width on post page
Square thumbnail1:1Listings, cards, prev/next
OG / social1200×630 landscapeTwitter, LinkedIn, etc.

All three must share the same visual style (black background, white line-art, no typography). Prefer a script or export step to generate OG from a composed 1200×630 source when the repo provides one.

Repo-specific paths and scripts

Each repository may define where to store assets and which scripts to run. Check that repo's docs (e.g. README.md, content/posts/README.md, or foundation adapter config) for:

  • Image directory — e.g. public/images/posts/, static/images/posts/
  • Naming — e.g. {slug}-hero.png, {slug}-hero-square.png, {slug}-hero-og.png, og/{slug}-1200x630.jpg
  • Layout hint — e.g. {slug}-hero-style.txt with keep-proportions for uncropped display
  • Scripts — e.g. generate-hero-square-from-hero.mjs, npm run generate:og:post -- <slug>, regenerate-hero-assets-centered.mjs
  • Cache — e.g. python3 execution/scripts/generate_posts_cache.py after adding or changing assets

If the repo has no docs, apply only the Visual style (mandatory) and use sensible paths (e.g. images/posts/, slug-based filenames).

Checklist when creating post images

  1. Generate or obtain the hero (and optional square/OG) using the mandatory visual style and prompt template above.
  2. Save assets in the repo's configured directory with the repo's naming convention.
  3. Add layout hint when the repo uses it (e.g. keep-proportions in -hero-style.txt).
  4. Run repo scripts for derived assets (square crop, OG export) and cache regeneration when documented.
  5. Do not add text, logos, or colors that break the black-background / white-line-art rule.

Reference

Canonical style reference: Hero Image Style Guide in the markmhendrickson website posts README (execution/website/markmhendrickson/react-app/src/content/posts/README.md). This skill is the foundation-level summary so the same style can be applied in any repo without reading that file.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.