cd /news/ai-tools/genart-skill-a-generative-art-skill-… · home topics ai-tools article
[ARTICLE · art-114582] src=github.com ↗ pub= topic=ai-tools verified=true sentiment=· neutral

Genart-skill: a generative art skill for Claude Code

Camille Roux released genart-skill, a plugin for Anthropic's Claude Code that teaches the AI assistant the working knowledge of generative art, including deterministic hash-seeded PRNGs, resolution-independent rendering, trait and rarity design, and platform-specific requirements for Art Blocks, 256ART, Verse, Highlight, Plottables, and bootloader.art. The plugin ships runnable scripts for determinism checks and batch rendering, and it explicitly avoids embedding volatile platform facts, instead linking to canonical documentation to prevent staleness.

read3 min views2 publishedAug 28, 2026
Genart-skill: a generative art skill for Claude Code
Image: Michielbdejong (auto-discovered)

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

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.

/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

.

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, boot.art, self-hosted

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.

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

.

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.

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.

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.

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

MIT.

── more in #ai-tools 4 stories · sorted by recency
── more on @camille roux 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/genart-skill-a-gener…] indexed:0 read:3min 2026-08-28 ·