genart-skill README

The project's README from github.com/camilleroux/genart-skill. As one markdown file: README.md.

genart — a generative art skill for Claude Code

Plugin version CI License: MIT

Create long-form generative art with AI assistance — deterministic, hash-seeded, ready for onchain platforms like Art Blocks, 256ART, Verse, Highlight, Plottables and bootloader.art — or for screens, via Artpoint.

This Claude Code plugin teaches Claude the working knowledge of the field: seeding a PRNG from a token hash, rendering the same composition at any resolution, designing traits and rarity tables, signalling preview capture, exporting for print and pen plotters, and where the ethical lines of generative art are. It covers creative coding with Canvas 2D, p5.js, three.js/WebGL and SVG — and ships runnable tools to verify that a sketch really is deterministic before you mint it.

Made by a generative artist, for generative artists using AI as a studio assistant — not as the artist.

Contact sheet of six seeds from Impossible Machine, each labelled with its token hash

Six seeds of Impossible Machine (Camille Roux) — hand-drawn technical blueprints, one hash each. The edition-level view the scripts are there to give you: same code, same rules, one sheet per seed.

Install

/plugin marketplace add camilleroux/genart-skill
/plugin install genart@camilleroux-genart

Then just talk about your sketch — the skill loads on its own. Or invoke it with /genart.

What's in it

One skill, genart, with reference sheets loaded on demand:

Runnable scripts

Two scripts ship with the plugin and run in place — Claude (or you) never copies them into a project, so updating the plugin updates them everywhere:

node "$CLAUDE_PLUGIN_ROOT/scripts/check.mjs"  myproject          # determinism checks
node "$CLAUDE_PLUGIN_ROOT/scripts/render.mjs" myproject --hash 0x…      # one PNG
node "$CLAUDE_PLUGIN_ROOT/scripts/render.mjs" myproject --grid 50       # contact sheet
node "$CLAUDE_PLUGIN_ROOT/scripts/render.mjs" myproject --census 5000   # rarity, measured
node "$CLAUDE_PLUGIN_ROOT/scripts/render.mjs" myproject --batch 50      # individual PNGs

render.mjs --hash is what lets Claude close the visual loop on its own: edit the sketch, render a seed, look at the PNG, adjust. The grid and the census are the edition-level views — what the rarity table actually produces.

What check.mjs prints on a sketch that holds:

myproject  (size 600, 3 runs)

repeatability
  ok   0xa3f1a3f1a3… → 06669011
  ok   0x77c277c277… → 7e5f6b7f

distinctness
  ok   two different hashes produce two different renders

global state (A, B, A in one page)
  ok   A=06669011 B=7e5f6b7f A'=06669011

features
  ok   stable across 3 runs: {"Palette":"Ash","Density":"Sparse"}

all checks passed

And on the same sketch with one Math.random() left in — the broken variant CI derives from the fixture on every push, and requires to fail:

repeatability
 FAIL  0xa3f1a3f1a3… → e8dec1f3 / b40e8a1f / dc9b8f1f
 FAIL  0x77c277c277… → 32fa5f55 / e04d40ad / a55fea14

global state (A, B, A in one page)
 FAIL  A=e127ff40 B=55a66c50 A'=05545a48

features
 FAIL  changed between runs: {"Palette":"Ash",…} vs {"Palette":"Ember",…} vs {"Palette":"Verdant",…}

4 failure(s)

distinctness still passes there: Math.random() does produce two different images. Each check covers what it covers, and no more.

They need Playwright in your project (npm i -D playwright && npx playwright install chromium — they print this if it is missing). The plugin itself stays dependency-free: no package.json, nothing embedded.

The contract a sketch must follow (three lines of shim for any platform) and what the checks can and cannot prove are in references/verification.md.

How the platform sheets work

They contain no version numbers, no figures and no field names — only the stable mental model of each platform, the canonical doc URLs, and the questions to ask those docs. Claude fetches the real documentation before writing platform code.

That is deliberate. A copied value goes stale in months and is then worse than nothing, because you believe it. A link stays right.

On determinism claims

Nothing here can prove cross-machine determinism, and this plugin does not claim to. In WebGL, shader compilers, float precision, rasterisers and MSAA differ between GPUs; in JS, transcendental functions differ between engines. What is actually checkable is same-machine reproducibility, perceptual stability across sizes, and feature stability. references/verification.md is explicit about where the line falls.

Maintenance

CI runs the scripts against a known-good fixture on every push (and against a broken variant derived from it, which must fail), and checks monthly that the URLs in the sheets still resolve — confirmed 404/DNS only, bot walls don't count — opening an issue when one dies. The sheets contain no volatile facts, so dead links are the only thing that rots.

Show what you make

If you mint something with it, I would genuinely like to see it — open a Discussion with a render and the platform you released on, or post it and tag @camillerouxart. Pieces made with the skill get shared onward.

Reference sheets are the easiest thing to contribute: a platform that is missing, a doc URL that moved, a mental model that is wrong. Issues and PRs welcome — the editorial rules are short.

If it saved you an afternoon, a ⭐ is how the next artist finds it.

Author

Built and maintained by Camille Roux — generative/algorithmic artist. Maintainer of awesome-generative-art, the curated list of generative art platforms, libraries and resources.

Follow the art: art.camilleroux.com · X · Instagram · Farcaster · Bluesky · Mastodon · TikTok

License

MIT.

genart-skill (camilleroux/genart-skill)

nft
Searching Database…

What is this?genart is a Claude Code plugin that teaches Claude the technical and ethical groundwork of generative art — seeding a PRNG from a token hash, deterministic rendering, trait and rarity design — and ships scripts to verify a sketch is actually deterministic before you mint it onchain.
Is this a standalone app or a Claude Code plugin?It is a Claude Code plugin (a skill), not a separate app. It loads automatically when you talk about your sketch inside Claude Code, or you can invoke it directly with /genart.
How do I start using it?Install the plugin in Claude Code, then just talk about your sketch — the skill loads on its own, or you can call it explicitly with /genart.
Do I need anything besides Claude Code to run the verification scripts?Yes — check.mjs and render.mjs need Playwright installed in your own project (npm i -D playwright && npx playwright install chromium); the plugin itself ships with no package.json and no embedded dependencies.
Can it guarantee my art looks identical on someone else's computer?No — cross-machine determinism can't be proven. WebGL shader compilers, float precision and rasterisers differ between GPUs, and transcendental functions differ between JS engines, so only same-machine reproducibility and feature/perceptual stability are actually checkable.
What creative coding tools does it cover?Canvas 2D, p5.js, three.js/WebGL and SVG — the sketch can be built with any of these, as long as it follows the three-line determinism shim described in verification.md.
Which onchain platforms does it know about?Art Blocks, 256ART, Verse, Highlight, Plottables, bootloader.art, self-hosted setups, and Artpoint for screen-based (non-mint) pieces.
What do the two runnable scripts actually do?render.mjs --hash renders a given seed to a PNG so Claude can look at the result and iterate, while check.mjs runs reproducibility and feature-stability checks and fails on things like a stray Math.random() call.
Why don't the platform reference sheets include concrete specs?They deliberately contain no version numbers or field names, only the stable mental model and canonical doc URLs, so Claude fetches the real, current documentation instead of relying on values that go stale and become misleading.
Size
0.7 MB
Stars
152
Age
1mo
Commits · 90 Days