genart — a generative art skill for Claude Code

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.

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:

• determinism — PRNG choice, seeding from a hash, named sub-streams, the things that silently break reproducibility
• resolution — rendering the same piece at 400px and at 4000px
• features — designing traits and rarity tables that survive an edition
• ethics — originality, attribution, licences, AI disclosure
• tooling — debug GUI, keyboard shortcuts, PNG and video export
• verification — checking a sketch before minting, and what a test can't prove
• platforms — Art Blocks, 256ART, Verse, Highlight, Plottables, bootloader.art, self-hosted, Artpoint (art on screen)

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: