generative-art-deployment

Deploy generative artworks to web galleries, print production, exhibitions, and archives.

Updated May 16, 2026
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill generative-art-deployment-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generative-art-deployment
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/generative-art-deployment
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill generative-art-deployment-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving generative art from a development sketch to a finished exhibition, print, or archive involves many failure points: wrong resolutions for print, missing seeds that break reproducibility, gallery pieces that crash without network, and archives that cannot be re-rendered. This Skill provides the pipelines, checklists, and metadata schemas to ship algorithmic artwork reliably across every target. ## Core Features & Use Cases - Multi-target deployment: Covers web galleries (HTML/JS/WebGL), physical print (300 DPI TIFF with bleed and ICC color profiles), LED installations, NFT/on-chain outputs, and social media formats. - Deterministic rendering pipelines: Batch-render seeded outputs with Node.js scripts and enforce reproducibility via recorded seeds, parameters, and SHA-256 checksums. - Exhibition and archival tooling: Includes kiosk-mode setup scripts, installation checklists, archive package structures, and reproducibility contracts. - Use Case: An artist preparing a gallery show uses this Skill to render a 100-piece seeded series at 4K, generate per-work metadata.json files, set up a Chromium kiosk display with crash recovery, and package a lossless TIFF archive with vendored dependencies. ## Quick Start Deploy my p5.js generative art series as a web gallery with print-ready 300 DPI renders and a reproducible archive package.

Frequently Asked Questions about generative-art-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I render generative art for print at 300 DPI?▼

Multiply the target print dimensions in inches by 300 to get pixel dimensions, then add a 0.125-inch bleed on each side. Export as lossless TIFF with an embedded sRGB or Adobe RGB ICC profile using PIL's ImageCms for color management.

How do I make a p5.js sketch reproducible with seeds?▼

Call randomSeed() and noiseSeed() with the same integer seed in setup() before generating any random values. Record the seed, parameters, runtime versions, and a SHA-256 checksum in a reproducibility contract so the exact output can be re-rendered later.

How do I set up a kiosk mode display for an art installation?▼

Launch Chromium with the --kiosk flag, disable power management and screen savers via xset, and hide the cursor with unclutter. Add a watchdog or supervisor process for crash recovery and ensure all assets are local so the piece works without network.

What resolution do I need for large format art prints?▼

At 300 DPI, an A3 print requires 3510 × 4950 pixels and a 24×36 poster requires 7200 × 10800 pixels. Always render at maximum resolution and keep lossless TIFF or PNG masters alongside any compressed versions.

Why does my generative artwork fail during exhibition?▼

Common causes are missing network connectivity, screen savers activating, cursor visibility, and unhandled crashes. The installation checklist requires offline-capable assets, disabled power management, hidden cursor, autostart on boot, and tested power-failure recovery.

What should a generative art archive package contain?▼

Include the original source code, high-resolution lossless renders, a metadata.json with seeds and parameters, vendored dependencies like p5.min.js, and documentation of the artistic process. A README explaining how to run the piece ensures long-term reproducibility.