Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill algorithmic-art74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Philosophy creation workflow
Craftsmanship emphasis repeated
0%
100%
Philosophy length
0%
100%
Named movement
0%
100%
Algorithmic focus
100%
100%
randomSeed usage
0%
100%
noiseSeed usage
0%
100%
Seed in params object
0%
0%
Algorithm inline
100%
100%
Without context: $0.3902 · 2m 32s · 15 turns · 21 in / 8,905 out tokens
With context: $1.3636 · 7m 20s · 25 turns · 28 in / 29,574 out tokens
Interactive HTML artifact structure
Poppins or Lora font
0%
100%
Light color scheme
100%
100%
Seed display element
100%
100%
Previous and Next seed buttons
100%
100%
Random seed button
0%
100%
Jump-to-seed input
100%
100%
Regenerate button
0%
100%
Reset button
0%
100%
Download PNG button
100%
100%
Seed before Parameters in sidebar
100%
100%
p5.js from cdnjs CDN
100%
100%
Without context: $0.6010 · 2m 46s · 18 turns · 25 in / 12,380 out tokens
With context: $0.7810 · 3m 22s · 23 turns · 277 in / 14,166 out tokens
Parameter design and conceptual encoding
Canvas 1200x1200
100%
100%
Parameters beyond seed
100%
100%
Conceptual encoding — not literal
100%
100%
Philosophy non-redundant
90%
100%
Self-contained HTML
100%
76%
p5.js setup and draw
0%
100%
Parameters from philosophy
66%
100%
Algorithm expresses philosophy
92%
100%
Without context: $1.2953 · 8m 27s · 14 turns · 20 in / 32,915 out tokens
With context: $1.2224 · 6m 31s · 21 turns · 183 in / 26,024 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.