Create procedural art

Translate direction into a controllable visual system. The code is the medium; its output still needs art review.

Choose the rendering path

Read the art contract, target device, stack, and proof renders. Follow constraints such as code-only geometry, a shared rig, or a specific engine. Choose SVG, Canvas, shaders, mesh geometry, or an established library based on behavior and export.

Choose subject, visual grammar, and production constraints from the brief. Abstract graphics, lettering, environments, and representational subjects need different parameters and proofs.

Extending the established vector system can be enough for a static graphic. A bitmap texture belongs with image generation when requested and allowed. Do not hide raster images in a deliverable described as entirely procedural.

Build the visual grammar

Expose parameters representing art decisions: proportions, silhouette landmarks, contour variation, palette, material response, texture scale, light, camera, composition, and motion inputs. Separate shape, rendering, and behavior only where it makes requested variation easier.