agentleFS
Sign inStart free
epicsagasepicsagas/Velith/skills/book-illustrate/SKILL.md

book-illustrate

Skill40 starsChanged 2 months agoApache-2.0View on GitHub

Alias for /book-visuals limited to diffusion illustrations (scene, header, spot art). Kept for compatibility; new work should use /book-visuals, which also covers diagrams, charts, technical drawings, photos, and the art bible.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    If art-bible.md does not exist or has no ## Look lock, run /book-visuals plan then /book-visuals lock first.

    line 11
  2. Very specific:

    Run node ${CLAUDE_PLUGIN_ROOT}/velith.mjs images check [project-dir] and have art-director do the consistency review.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Interior Illustrations

This command is now a thin entry point into the book visual system. Run the illustration subset of /book-visuals:

  1. If art-bible.md does not exist or has no ## Look lock, run /book-visuals plan then /book-visuals lock first. Illustrations produced without a locked look will not match each other or the cover.
  2. Invoke illustrator for the chapters in scope. It chooses moments, compiles model-agnostic prompts via velith.mjs images compile, generates if an image tool is available and --execute was given, runs vision QA, and places references.
  3. Run node ${CLAUDE_PLUGIN_ROOT}/velith.mjs images check [project-dir] and have art-director do the consistency review.

Full reference, image types, constraints, and directory layout: ${CLAUDE_PLUGIN_ROOT}/skills/book-visuals/SKILL.md.

Legacy note: projects that kept illustrations in publish/illustrations/ still build; images check reports them as unmanaged until they are moved to visuals/illustrations/ and added to the manifest.

Post-completion

node ${CLAUDE_PLUGIN_ROOT}/velith.mjs scan [project-dir]

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.

Check your setup, free