@bgicli/bgicli 2.2.8 → 2.2.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/data/skills/anthropic-algorithmic-art/SKILL.md +405 -0
- package/data/skills/anthropic-canvas-design/SKILL.md +130 -0
- package/data/skills/anthropic-claude-api/SKILL.md +243 -0
- package/data/skills/anthropic-doc-coauthoring/SKILL.md +375 -0
- package/data/skills/anthropic-docx/SKILL.md +590 -0
- package/data/skills/anthropic-frontend-design/SKILL.md +42 -0
- package/data/skills/anthropic-internal-comms/SKILL.md +32 -0
- package/data/skills/anthropic-mcp-builder/SKILL.md +236 -0
- package/data/skills/anthropic-pdf/SKILL.md +314 -0
- package/data/skills/anthropic-pptx/SKILL.md +232 -0
- package/data/skills/anthropic-skill-creator/SKILL.md +485 -0
- package/data/skills/anthropic-webapp-testing/SKILL.md +96 -0
- package/data/skills/anthropic-xlsx/SKILL.md +292 -0
- package/data/skills/arxiv-database/SKILL.md +362 -0
- package/data/skills/astropy/SKILL.md +329 -0
- package/data/skills/ctx-advanced-evaluation/SKILL.md +402 -0
- package/data/skills/ctx-bdi-mental-states/SKILL.md +311 -0
- package/data/skills/ctx-context-compression/SKILL.md +272 -0
- package/data/skills/ctx-context-degradation/SKILL.md +206 -0
- package/data/skills/ctx-context-fundamentals/SKILL.md +201 -0
- package/data/skills/ctx-context-optimization/SKILL.md +195 -0
- package/data/skills/ctx-evaluation/SKILL.md +251 -0
- package/data/skills/ctx-filesystem-context/SKILL.md +287 -0
- package/data/skills/ctx-hosted-agents/SKILL.md +260 -0
- package/data/skills/ctx-memory-systems/SKILL.md +225 -0
- package/data/skills/ctx-multi-agent-patterns/SKILL.md +257 -0
- package/data/skills/ctx-project-development/SKILL.md +291 -0
- package/data/skills/ctx-tool-design/SKILL.md +271 -0
- package/data/skills/dhdna-profiler/SKILL.md +162 -0
- package/data/skills/generate-image/SKILL.md +183 -0
- package/data/skills/geomaster/SKILL.md +365 -0
- package/data/skills/get-available-resources/SKILL.md +275 -0
- package/data/skills/hamelsmu-build-review-interface/SKILL.md +96 -0
- package/data/skills/hamelsmu-error-analysis/SKILL.md +164 -0
- package/data/skills/hamelsmu-eval-audit/SKILL.md +183 -0
- package/data/skills/hamelsmu-evaluate-rag/SKILL.md +177 -0
- package/data/skills/hamelsmu-generate-synthetic-data/SKILL.md +131 -0
- package/data/skills/hamelsmu-validate-evaluator/SKILL.md +212 -0
- package/data/skills/hamelsmu-write-judge-prompt/SKILL.md +144 -0
- package/data/skills/hf-cli/SKILL.md +174 -0
- package/data/skills/hf-mcp/SKILL.md +178 -0
- package/data/skills/hugging-face-dataset-viewer/SKILL.md +121 -0
- package/data/skills/hugging-face-datasets/SKILL.md +542 -0
- package/data/skills/hugging-face-evaluation/SKILL.md +651 -0
- package/data/skills/hugging-face-jobs/SKILL.md +1042 -0
- package/data/skills/hugging-face-model-trainer/SKILL.md +717 -0
- package/data/skills/hugging-face-paper-pages/SKILL.md +239 -0
- package/data/skills/hugging-face-paper-publisher/SKILL.md +624 -0
- package/data/skills/hugging-face-tool-builder/SKILL.md +110 -0
- package/data/skills/hugging-face-trackio/SKILL.md +115 -0
- package/data/skills/hugging-face-vision-trainer/SKILL.md +593 -0
- package/data/skills/huggingface-gradio/SKILL.md +245 -0
- package/data/skills/matlab/SKILL.md +376 -0
- package/data/skills/modal/SKILL.md +381 -0
- package/data/skills/openai-cloudflare-deploy/SKILL.md +224 -0
- package/data/skills/openai-develop-web-game/SKILL.md +149 -0
- package/data/skills/openai-doc/SKILL.md +80 -0
- package/data/skills/openai-figma/SKILL.md +42 -0
- package/data/skills/openai-figma-implement-design/SKILL.md +264 -0
- package/data/skills/openai-gh-address-comments/SKILL.md +25 -0
- package/data/skills/openai-gh-fix-ci/SKILL.md +69 -0
- package/data/skills/openai-imagegen/SKILL.md +174 -0
- package/data/skills/openai-jupyter-notebook/SKILL.md +107 -0
- package/data/skills/openai-linear/SKILL.md +87 -0
- package/data/skills/openai-netlify-deploy/SKILL.md +247 -0
- package/data/skills/openai-notion-knowledge-capture/SKILL.md +56 -0
- package/data/skills/openai-notion-meeting-intelligence/SKILL.md +60 -0
- package/data/skills/openai-notion-research-documentation/SKILL.md +59 -0
- package/data/skills/openai-notion-spec-to-implementation/SKILL.md +58 -0
- package/data/skills/openai-openai-docs/SKILL.md +69 -0
- package/data/skills/openai-pdf/SKILL.md +67 -0
- package/data/skills/openai-playwright/SKILL.md +147 -0
- package/data/skills/openai-render-deploy/SKILL.md +479 -0
- package/data/skills/openai-screenshot/SKILL.md +267 -0
- package/data/skills/openai-security-best-practices/SKILL.md +86 -0
- package/data/skills/openai-security-ownership-map/SKILL.md +206 -0
- package/data/skills/openai-security-threat-model/SKILL.md +81 -0
- package/data/skills/openai-sentry/SKILL.md +123 -0
- package/data/skills/openai-sora/SKILL.md +178 -0
- package/data/skills/openai-speech/SKILL.md +144 -0
- package/data/skills/openai-spreadsheet/SKILL.md +145 -0
- package/data/skills/openai-transcribe/SKILL.md +81 -0
- package/data/skills/openai-vercel-deploy/SKILL.md +77 -0
- package/data/skills/openai-yeet/SKILL.md +28 -0
- package/data/skills/pennylane/SKILL.md +224 -0
- package/data/skills/polars-bio/SKILL.md +374 -0
- package/data/skills/primekg/SKILL.md +97 -0
- package/data/skills/pymatgen/SKILL.md +689 -0
- package/data/skills/qiskit/SKILL.md +273 -0
- package/data/skills/qutip/SKILL.md +316 -0
- package/data/skills/recursive-decomposition/SKILL.md +185 -0
- package/data/skills/rowan/SKILL.md +427 -0
- package/data/skills/scholar-evaluation/SKILL.md +298 -0
- package/data/skills/sentry-create-alert/SKILL.md +210 -0
- package/data/skills/sentry-fix-issues/SKILL.md +126 -0
- package/data/skills/sentry-pr-code-review/SKILL.md +105 -0
- package/data/skills/sentry-python-sdk/SKILL.md +317 -0
- package/data/skills/sentry-setup-ai-monitoring/SKILL.md +217 -0
- package/data/skills/stable-baselines3/SKILL.md +297 -0
- package/data/skills/sympy/SKILL.md +498 -0
- package/data/skills/trailofbits-ask-questions-if-underspecified/SKILL.md +85 -0
- package/data/skills/trailofbits-audit-context-building/SKILL.md +302 -0
- package/data/skills/trailofbits-differential-review/SKILL.md +220 -0
- package/data/skills/trailofbits-insecure-defaults/SKILL.md +117 -0
- package/data/skills/trailofbits-modern-python/SKILL.md +333 -0
- package/data/skills/trailofbits-property-based-testing/SKILL.md +123 -0
- package/data/skills/trailofbits-semgrep-rule-creator/SKILL.md +172 -0
- package/data/skills/trailofbits-sharp-edges/SKILL.md +292 -0
- package/data/skills/trailofbits-variant-analysis/SKILL.md +142 -0
- package/data/skills/transformers.js/SKILL.md +637 -0
- package/data/skills/writing/SKILL.md +419 -0
- package/dist/bgi.js +66 -2
- package/package.json +1 -1
|
@@ -0,0 +1,405 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: algorithmic-art
|
|
3
|
+
description: 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.
|
|
4
|
+
license: Complete terms in LICENSE.txt
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms).
|
|
8
|
+
|
|
9
|
+
This happens in two steps:
|
|
10
|
+
1. Algorithmic Philosophy Creation (.md file)
|
|
11
|
+
2. Express by creating p5.js generative art (.html + .js files)
|
|
12
|
+
|
|
13
|
+
First, undertake this task:
|
|
14
|
+
|
|
15
|
+
## ALGORITHMIC PHILOSOPHY CREATION
|
|
16
|
+
|
|
17
|
+
To begin, create an ALGORITHMIC PHILOSOPHY (not static images or templates) that will be interpreted through:
|
|
18
|
+
- Computational processes, emergent behavior, mathematical beauty
|
|
19
|
+
- Seeded randomness, noise fields, organic systems
|
|
20
|
+
- Particles, flows, fields, forces
|
|
21
|
+
- Parametric variation and controlled chaos
|
|
22
|
+
|
|
23
|
+
### THE CRITICAL UNDERSTANDING
|
|
24
|
+
- What is received: Some subtle input or instructions by the user to take into account, but use as a foundation; it should not constrain creative freedom.
|
|
25
|
+
- What is created: An algorithmic philosophy/generative aesthetic movement.
|
|
26
|
+
- What happens next: The same version receives the philosophy and EXPRESSES IT IN CODE - creating p5.js sketches that are 90% algorithmic generation, 10% essential parameters.
|
|
27
|
+
|
|
28
|
+
Consider this approach:
|
|
29
|
+
- Write a manifesto for a generative art movement
|
|
30
|
+
- The next phase involves writing the algorithm that brings it to life
|
|
31
|
+
|
|
32
|
+
The philosophy must emphasize: Algorithmic expression. Emergent behavior. Computational beauty. Seeded variation.
|
|
33
|
+
|
|
34
|
+
### HOW TO GENERATE AN ALGORITHMIC PHILOSOPHY
|
|
35
|
+
|
|
36
|
+
**Name the movement** (1-2 words): "Organic Turbulence" / "Quantum Harmonics" / "Emergent Stillness"
|
|
37
|
+
|
|
38
|
+
**Articulate the philosophy** (4-6 paragraphs - concise but complete):
|
|
39
|
+
|
|
40
|
+
To capture the ALGORITHMIC essence, express how this philosophy manifests through:
|
|
41
|
+
- Computational processes and mathematical relationships?
|
|
42
|
+
- Noise functions and randomness patterns?
|
|
43
|
+
- Particle behaviors and field dynamics?
|
|
44
|
+
- Temporal evolution and system states?
|
|
45
|
+
- Parametric variation and emergent complexity?
|
|
46
|
+
|
|
47
|
+
**CRITICAL GUIDELINES:**
|
|
48
|
+
- **Avoid redundancy**: Each algorithmic aspect should be mentioned once. Avoid repeating concepts about noise theory, particle dynamics, or mathematical principles unless adding new depth.
|
|
49
|
+
- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final algorithm should appear as though it took countless hours to develop, was refined with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like "meticulously crafted algorithm," "the product of deep computational expertise," "painstaking optimization," "master-level implementation."
|
|
50
|
+
- **Leave creative space**: Be specific about the algorithmic direction, but concise enough that the next Claude has room to make interpretive implementation choices at an extremely high level of craftsmanship.
|
|
51
|
+
|
|
52
|
+
The philosophy must guide the next version to express ideas ALGORITHMICALLY, not through static images. Beauty lives in the process, not the final frame.
|
|
53
|
+
|
|
54
|
+
### PHILOSOPHY EXAMPLES
|
|
55
|
+
|
|
56
|
+
**"Organic Turbulence"**
|
|
57
|
+
Philosophy: Chaos constrained by natural law, order emerging from disorder.
|
|
58
|
+
Algorithmic expression: Flow fields driven by layered Perlin noise. Thousands of particles following vector forces, their trails accumulating into organic density maps. Multiple noise octaves create turbulent regions and calm zones. Color emerges from velocity and density - fast particles burn bright, slow ones fade to shadow. The algorithm runs until equilibrium - a meticulously tuned balance where every parameter was refined through countless iterations by a master of computational aesthetics.
|
|
59
|
+
|
|
60
|
+
**"Quantum Harmonics"**
|
|
61
|
+
Philosophy: Discrete entities exhibiting wave-like interference patterns.
|
|
62
|
+
Algorithmic expression: Particles initialized on a grid, each carrying a phase value that evolves through sine waves. When particles are near, their phases interfere - constructive interference creates bright nodes, destructive creates voids. Simple harmonic motion generates complex emergent mandalas. The result of painstaking frequency calibration where every ratio was carefully chosen to produce resonant beauty.
|
|
63
|
+
|
|
64
|
+
**"Recursive Whispers"**
|
|
65
|
+
Philosophy: Self-similarity across scales, infinite depth in finite space.
|
|
66
|
+
Algorithmic expression: Branching structures that subdivide recursively. Each branch slightly randomized but constrained by golden ratios. L-systems or recursive subdivision generate tree-like forms that feel both mathematical and organic. Subtle noise perturbations break perfect symmetry. Line weights diminish with each recursion level. Every branching angle the product of deep mathematical exploration.
|
|
67
|
+
|
|
68
|
+
**"Field Dynamics"**
|
|
69
|
+
Philosophy: Invisible forces made visible through their effects on matter.
|
|
70
|
+
Algorithmic expression: Vector fields constructed from mathematical functions or noise. Particles born at edges, flowing along field lines, dying when they reach equilibrium or boundaries. Multiple fields can attract, repel, or rotate particles. The visualization shows only the traces - ghost-like evidence of invisible forces. A computational dance meticulously choreographed through force balance.
|
|
71
|
+
|
|
72
|
+
**"Stochastic Crystallization"**
|
|
73
|
+
Philosophy: Random processes crystallizing into ordered structures.
|
|
74
|
+
Algorithmic expression: Randomized circle packing or Voronoi tessellation. Start with random points, let them evolve through relaxation algorithms. Cells push apart until equilibrium. Color based on cell size, neighbor count, or distance from center. The organic tiling that emerges feels both random and inevitable. Every seed produces unique crystalline beauty - the mark of a master-level generative algorithm.
|
|
75
|
+
|
|
76
|
+
*These are condensed examples. The actual algorithmic philosophy should be 4-6 substantial paragraphs.*
|
|
77
|
+
|
|
78
|
+
### ESSENTIAL PRINCIPLES
|
|
79
|
+
- **ALGORITHMIC PHILOSOPHY**: Creating a computational worldview to be expressed through code
|
|
80
|
+
- **PROCESS OVER PRODUCT**: Always emphasize that beauty emerges from the algorithm's execution - each run is unique
|
|
81
|
+
- **PARAMETRIC EXPRESSION**: Ideas communicate through mathematical relationships, forces, behaviors - not static composition
|
|
82
|
+
- **ARTISTIC FREEDOM**: The next Claude interprets the philosophy algorithmically - provide creative implementation room
|
|
83
|
+
- **PURE GENERATIVE ART**: This is about making LIVING ALGORITHMS, not static images with randomness
|
|
84
|
+
- **EXPERT CRAFTSMANSHIP**: Repeatedly emphasize the final algorithm must feel meticulously crafted, refined through countless iterations, the product of deep expertise by someone at the absolute top of their field in computational aesthetics
|
|
85
|
+
|
|
86
|
+
**The algorithmic philosophy should be 4-6 paragraphs long.** Fill it with poetic computational philosophy that brings together the intended vision. Avoid repeating the same points. Output this algorithmic philosophy as a .md file.
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
## DEDUCING THE CONCEPTUAL SEED
|
|
91
|
+
|
|
92
|
+
**CRITICAL STEP**: Before implementing the algorithm, identify the subtle conceptual thread from the original request.
|
|
93
|
+
|
|
94
|
+
**THE ESSENTIAL PRINCIPLE**:
|
|
95
|
+
The concept is a **subtle, niche reference embedded within the algorithm itself** - not always literal, always sophisticated. Someone familiar with the subject should feel it intuitively, while others simply experience a masterful generative composition. The algorithmic philosophy provides the computational language. The deduced concept provides the soul - the quiet conceptual DNA woven invisibly into parameters, behaviors, and emergence patterns.
|
|
96
|
+
|
|
97
|
+
This is **VERY IMPORTANT**: The reference must be so refined that it enhances the work's depth without announcing itself. Think like a jazz musician quoting another song through algorithmic harmony - only those who know will catch it, but everyone appreciates the generative beauty.
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
101
|
+
## P5.JS IMPLEMENTATION
|
|
102
|
+
|
|
103
|
+
With the philosophy AND conceptual framework established, express it through code. Pause to gather thoughts before proceeding. Use only the algorithmic philosophy created and the instructions below.
|
|
104
|
+
|
|
105
|
+
### ⚠️ STEP 0: READ THE TEMPLATE FIRST ⚠️
|
|
106
|
+
|
|
107
|
+
**CRITICAL: BEFORE writing any HTML:**
|
|
108
|
+
|
|
109
|
+
1. **Read** `templates/viewer.html` using the Read tool
|
|
110
|
+
2. **Study** the exact structure, styling, and Anthropic branding
|
|
111
|
+
3. **Use that file as the LITERAL STARTING POINT** - not just inspiration
|
|
112
|
+
4. **Keep all FIXED sections exactly as shown** (header, sidebar structure, Anthropic colors/fonts, seed controls, action buttons)
|
|
113
|
+
5. **Replace only the VARIABLE sections** marked in the file's comments (algorithm, parameters, UI controls for parameters)
|
|
114
|
+
|
|
115
|
+
**Avoid:**
|
|
116
|
+
- ❌ Creating HTML from scratch
|
|
117
|
+
- ❌ Inventing custom styling or color schemes
|
|
118
|
+
- ❌ Using system fonts or dark themes
|
|
119
|
+
- ❌ Changing the sidebar structure
|
|
120
|
+
|
|
121
|
+
**Follow these practices:**
|
|
122
|
+
- ✅ Copy the template's exact HTML structure
|
|
123
|
+
- ✅ Keep Anthropic branding (Poppins/Lora fonts, light colors, gradient backdrop)
|
|
124
|
+
- ✅ Maintain the sidebar layout (Seed → Parameters → Colors? → Actions)
|
|
125
|
+
- ✅ Replace only the p5.js algorithm and parameter controls
|
|
126
|
+
|
|
127
|
+
The template is the foundation. Build on it, don't rebuild it.
|
|
128
|
+
|
|
129
|
+
---
|
|
130
|
+
|
|
131
|
+
To create gallery-quality computational art that lives and breathes, use the algorithmic philosophy as the foundation.
|
|
132
|
+
|
|
133
|
+
### TECHNICAL REQUIREMENTS
|
|
134
|
+
|
|
135
|
+
**Seeded Randomness (Art Blocks Pattern)**:
|
|
136
|
+
```javascript
|
|
137
|
+
// ALWAYS use a seed for reproducibility
|
|
138
|
+
let seed = 12345; // or hash from user input
|
|
139
|
+
randomSeed(seed);
|
|
140
|
+
noiseSeed(seed);
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
**Parameter Structure - FOLLOW THE PHILOSOPHY**:
|
|
144
|
+
|
|
145
|
+
To establish parameters that emerge naturally from the algorithmic philosophy, consider: "What qualities of this system can be adjusted?"
|
|
146
|
+
|
|
147
|
+
```javascript
|
|
148
|
+
let params = {
|
|
149
|
+
seed: 12345, // Always include seed for reproducibility
|
|
150
|
+
// colors
|
|
151
|
+
// Add parameters that control YOUR algorithm:
|
|
152
|
+
// - Quantities (how many?)
|
|
153
|
+
// - Scales (how big? how fast?)
|
|
154
|
+
// - Probabilities (how likely?)
|
|
155
|
+
// - Ratios (what proportions?)
|
|
156
|
+
// - Angles (what direction?)
|
|
157
|
+
// - Thresholds (when does behavior change?)
|
|
158
|
+
};
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
**To design effective parameters, focus on the properties the system needs to be tunable rather than thinking in terms of "pattern types".**
|
|
162
|
+
|
|
163
|
+
**Core Algorithm - EXPRESS THE PHILOSOPHY**:
|
|
164
|
+
|
|
165
|
+
**CRITICAL**: The algorithmic philosophy should dictate what to build.
|
|
166
|
+
|
|
167
|
+
To express the philosophy through code, avoid thinking "which pattern should I use?" and instead think "how to express this philosophy through code?"
|
|
168
|
+
|
|
169
|
+
If the philosophy is about **organic emergence**, consider using:
|
|
170
|
+
- Elements that accumulate or grow over time
|
|
171
|
+
- Random processes constrained by natural rules
|
|
172
|
+
- Feedback loops and interactions
|
|
173
|
+
|
|
174
|
+
If the philosophy is about **mathematical beauty**, consider using:
|
|
175
|
+
- Geometric relationships and ratios
|
|
176
|
+
- Trigonometric functions and harmonics
|
|
177
|
+
- Precise calculations creating unexpected patterns
|
|
178
|
+
|
|
179
|
+
If the philosophy is about **controlled chaos**, consider using:
|
|
180
|
+
- Random variation within strict boundaries
|
|
181
|
+
- Bifurcation and phase transitions
|
|
182
|
+
- Order emerging from disorder
|
|
183
|
+
|
|
184
|
+
**The algorithm flows from the philosophy, not from a menu of options.**
|
|
185
|
+
|
|
186
|
+
To guide the implementation, let the conceptual essence inform creative and original choices. Build something that expresses the vision for this particular request.
|
|
187
|
+
|
|
188
|
+
**Canvas Setup**: Standard p5.js structure:
|
|
189
|
+
```javascript
|
|
190
|
+
function setup() {
|
|
191
|
+
createCanvas(1200, 1200);
|
|
192
|
+
// Initialize your system
|
|
193
|
+
}
|
|
194
|
+
|
|
195
|
+
function draw() {
|
|
196
|
+
// Your generative algorithm
|
|
197
|
+
// Can be static (noLoop) or animated
|
|
198
|
+
}
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
### CRAFTSMANSHIP REQUIREMENTS
|
|
202
|
+
|
|
203
|
+
**CRITICAL**: To achieve mastery, create algorithms that feel like they emerged through countless iterations by a master generative artist. Tune every parameter carefully. Ensure every pattern emerges with purpose. This is NOT random noise - this is CONTROLLED CHAOS refined through deep expertise.
|
|
204
|
+
|
|
205
|
+
- **Balance**: Complexity without visual noise, order without rigidity
|
|
206
|
+
- **Color Harmony**: Thoughtful palettes, not random RGB values
|
|
207
|
+
- **Composition**: Even in randomness, maintain visual hierarchy and flow
|
|
208
|
+
- **Performance**: Smooth execution, optimized for real-time if animated
|
|
209
|
+
- **Reproducibility**: Same seed ALWAYS produces identical output
|
|
210
|
+
|
|
211
|
+
### OUTPUT FORMAT
|
|
212
|
+
|
|
213
|
+
Output:
|
|
214
|
+
1. **Algorithmic Philosophy** - As markdown or text explaining the generative aesthetic
|
|
215
|
+
2. **Single HTML Artifact** - Self-contained interactive generative art built from `templates/viewer.html` (see STEP 0 and next section)
|
|
216
|
+
|
|
217
|
+
The HTML artifact contains everything: p5.js (from CDN), the algorithm, parameter controls, and UI - all in one file that works immediately in claude.ai artifacts or any browser. Start from the template file, not from scratch.
|
|
218
|
+
|
|
219
|
+
---
|
|
220
|
+
|
|
221
|
+
## INTERACTIVE ARTIFACT CREATION
|
|
222
|
+
|
|
223
|
+
**REMINDER: `templates/viewer.html` should have already been read (see STEP 0). Use that file as the starting point.**
|
|
224
|
+
|
|
225
|
+
To allow exploration of the generative art, create a single, self-contained HTML artifact. Ensure this artifact works immediately in claude.ai or any browser - no setup required. Embed everything inline.
|
|
226
|
+
|
|
227
|
+
### CRITICAL: WHAT'S FIXED VS VARIABLE
|
|
228
|
+
|
|
229
|
+
The `templates/viewer.html` file is the foundation. It contains the exact structure and styling needed.
|
|
230
|
+
|
|
231
|
+
**FIXED (always include exactly as shown):**
|
|
232
|
+
- Layout structure (header, sidebar, main canvas area)
|
|
233
|
+
- Anthropic branding (UI colors, fonts, gradients)
|
|
234
|
+
- Seed section in sidebar:
|
|
235
|
+
- Seed display
|
|
236
|
+
- Previous/Next buttons
|
|
237
|
+
- Random button
|
|
238
|
+
- Jump to seed input + Go button
|
|
239
|
+
- Actions section in sidebar:
|
|
240
|
+
- Regenerate button
|
|
241
|
+
- Reset button
|
|
242
|
+
|
|
243
|
+
**VARIABLE (customize for each artwork):**
|
|
244
|
+
- The entire p5.js algorithm (setup/draw/classes)
|
|
245
|
+
- The parameters object (define what the art needs)
|
|
246
|
+
- The Parameters section in sidebar:
|
|
247
|
+
- Number of parameter controls
|
|
248
|
+
- Parameter names
|
|
249
|
+
- Min/max/step values for sliders
|
|
250
|
+
- Control types (sliders, inputs, etc.)
|
|
251
|
+
- Colors section (optional):
|
|
252
|
+
- Some art needs color pickers
|
|
253
|
+
- Some art might use fixed colors
|
|
254
|
+
- Some art might be monochrome (no color controls needed)
|
|
255
|
+
- Decide based on the art's needs
|
|
256
|
+
|
|
257
|
+
**Every artwork should have unique parameters and algorithm!** The fixed parts provide consistent UX - everything else expresses the unique vision.
|
|
258
|
+
|
|
259
|
+
### REQUIRED FEATURES
|
|
260
|
+
|
|
261
|
+
**1. Parameter Controls**
|
|
262
|
+
- Sliders for numeric parameters (particle count, noise scale, speed, etc.)
|
|
263
|
+
- Color pickers for palette colors
|
|
264
|
+
- Real-time updates when parameters change
|
|
265
|
+
- Reset button to restore defaults
|
|
266
|
+
|
|
267
|
+
**2. Seed Navigation**
|
|
268
|
+
- Display current seed number
|
|
269
|
+
- "Previous" and "Next" buttons to cycle through seeds
|
|
270
|
+
- "Random" button for random seed
|
|
271
|
+
- Input field to jump to specific seed
|
|
272
|
+
- Generate 100 variations when requested (seeds 1-100)
|
|
273
|
+
|
|
274
|
+
**3. Single Artifact Structure**
|
|
275
|
+
```html
|
|
276
|
+
<!DOCTYPE html>
|
|
277
|
+
<html>
|
|
278
|
+
<head>
|
|
279
|
+
<!-- p5.js from CDN - always available -->
|
|
280
|
+
<script src="https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.7.0/p5.min.js"></script>
|
|
281
|
+
<style>
|
|
282
|
+
/* All styling inline - clean, minimal */
|
|
283
|
+
/* Canvas on top, controls below */
|
|
284
|
+
</style>
|
|
285
|
+
</head>
|
|
286
|
+
<body>
|
|
287
|
+
<div id="canvas-container"></div>
|
|
288
|
+
<div id="controls">
|
|
289
|
+
<!-- All parameter controls -->
|
|
290
|
+
</div>
|
|
291
|
+
<script>
|
|
292
|
+
// ALL p5.js code inline here
|
|
293
|
+
// Parameter objects, classes, functions
|
|
294
|
+
// setup() and draw()
|
|
295
|
+
// UI handlers
|
|
296
|
+
// Everything self-contained
|
|
297
|
+
</script>
|
|
298
|
+
</body>
|
|
299
|
+
</html>
|
|
300
|
+
```
|
|
301
|
+
|
|
302
|
+
**CRITICAL**: This is a single artifact. No external files, no imports (except p5.js CDN). Everything inline.
|
|
303
|
+
|
|
304
|
+
**4. Implementation Details - BUILD THE SIDEBAR**
|
|
305
|
+
|
|
306
|
+
The sidebar structure:
|
|
307
|
+
|
|
308
|
+
**1. Seed (FIXED)** - Always include exactly as shown:
|
|
309
|
+
- Seed display
|
|
310
|
+
- Prev/Next/Random/Jump buttons
|
|
311
|
+
|
|
312
|
+
**2. Parameters (VARIABLE)** - Create controls for the art:
|
|
313
|
+
```html
|
|
314
|
+
<div class="control-group">
|
|
315
|
+
<label>Parameter Name</label>
|
|
316
|
+
<input type="range" id="param" min="..." max="..." step="..." value="..." oninput="updateParam('param', this.value)">
|
|
317
|
+
<span class="value-display" id="param-value">...</span>
|
|
318
|
+
</div>
|
|
319
|
+
```
|
|
320
|
+
Add as many control-group divs as there are parameters.
|
|
321
|
+
|
|
322
|
+
**3. Colors (OPTIONAL/VARIABLE)** - Include if the art needs adjustable colors:
|
|
323
|
+
- Add color pickers if users should control palette
|
|
324
|
+
- Skip this section if the art uses fixed colors
|
|
325
|
+
- Skip if the art is monochrome
|
|
326
|
+
|
|
327
|
+
**4. Actions (FIXED)** - Always include exactly as shown:
|
|
328
|
+
- Regenerate button
|
|
329
|
+
- Reset button
|
|
330
|
+
- Download PNG button
|
|
331
|
+
|
|
332
|
+
**Requirements**:
|
|
333
|
+
- Seed controls must work (prev/next/random/jump/display)
|
|
334
|
+
- All parameters must have UI controls
|
|
335
|
+
- Regenerate, Reset, Download buttons must work
|
|
336
|
+
- Keep Anthropic branding (UI styling, not art colors)
|
|
337
|
+
|
|
338
|
+
### USING THE ARTIFACT
|
|
339
|
+
|
|
340
|
+
The HTML artifact works immediately:
|
|
341
|
+
1. **In claude.ai**: Displayed as an interactive artifact - runs instantly
|
|
342
|
+
2. **As a file**: Save and open in any browser - no server needed
|
|
343
|
+
3. **Sharing**: Send the HTML file - it's completely self-contained
|
|
344
|
+
|
|
345
|
+
---
|
|
346
|
+
|
|
347
|
+
## VARIATIONS & EXPLORATION
|
|
348
|
+
|
|
349
|
+
The artifact includes seed navigation by default (prev/next/random buttons), allowing users to explore variations without creating multiple files. If the user wants specific variations highlighted:
|
|
350
|
+
|
|
351
|
+
- Include seed presets (buttons for "Variation 1: Seed 42", "Variation 2: Seed 127", etc.)
|
|
352
|
+
- Add a "Gallery Mode" that shows thumbnails of multiple seeds side-by-side
|
|
353
|
+
- All within the same single artifact
|
|
354
|
+
|
|
355
|
+
This is like creating a series of prints from the same plate - the algorithm is consistent, but each seed reveals different facets of its potential. The interactive nature means users discover their own favorites by exploring the seed space.
|
|
356
|
+
|
|
357
|
+
---
|
|
358
|
+
|
|
359
|
+
## THE CREATIVE PROCESS
|
|
360
|
+
|
|
361
|
+
**User request** → **Algorithmic philosophy** → **Implementation**
|
|
362
|
+
|
|
363
|
+
Each request is unique. The process involves:
|
|
364
|
+
|
|
365
|
+
1. **Interpret the user's intent** - What aesthetic is being sought?
|
|
366
|
+
2. **Create an algorithmic philosophy** (4-6 paragraphs) describing the computational approach
|
|
367
|
+
3. **Implement it in code** - Build the algorithm that expresses this philosophy
|
|
368
|
+
4. **Design appropriate parameters** - What should be tunable?
|
|
369
|
+
5. **Build matching UI controls** - Sliders/inputs for those parameters
|
|
370
|
+
|
|
371
|
+
**The constants**:
|
|
372
|
+
- Anthropic branding (colors, fonts, layout)
|
|
373
|
+
- Seed navigation (always present)
|
|
374
|
+
- Self-contained HTML artifact
|
|
375
|
+
|
|
376
|
+
**Everything else is variable**:
|
|
377
|
+
- The algorithm itself
|
|
378
|
+
- The parameters
|
|
379
|
+
- The UI controls
|
|
380
|
+
- The visual outcome
|
|
381
|
+
|
|
382
|
+
To achieve the best results, trust creativity and let the philosophy guide the implementation.
|
|
383
|
+
|
|
384
|
+
---
|
|
385
|
+
|
|
386
|
+
## RESOURCES
|
|
387
|
+
|
|
388
|
+
This skill includes helpful templates and documentation:
|
|
389
|
+
|
|
390
|
+
- **templates/viewer.html**: REQUIRED STARTING POINT for all HTML artifacts.
|
|
391
|
+
- This is the foundation - contains the exact structure and Anthropic branding
|
|
392
|
+
- **Keep unchanged**: Layout structure, sidebar organization, Anthropic colors/fonts, seed controls, action buttons
|
|
393
|
+
- **Replace**: The p5.js algorithm, parameter definitions, and UI controls in Parameters section
|
|
394
|
+
- The extensive comments in the file mark exactly what to keep vs replace
|
|
395
|
+
|
|
396
|
+
- **templates/generator_template.js**: Reference for p5.js best practices and code structure principles.
|
|
397
|
+
- Shows how to organize parameters, use seeded randomness, structure classes
|
|
398
|
+
- NOT a pattern menu - use these principles to build unique algorithms
|
|
399
|
+
- Embed algorithms inline in the HTML artifact (don't create separate .js files)
|
|
400
|
+
|
|
401
|
+
**Critical reminder**:
|
|
402
|
+
- The **template is the STARTING POINT**, not inspiration
|
|
403
|
+
- The **algorithm is where to create** something unique
|
|
404
|
+
- Don't copy the flow field example - build what the philosophy demands
|
|
405
|
+
- But DO keep the exact UI structure and Anthropic branding from the template
|
|
@@ -0,0 +1,130 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: canvas-design
|
|
3
|
+
description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
|
|
4
|
+
license: Complete terms in LICENSE.txt
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.
|
|
8
|
+
|
|
9
|
+
Complete this in two steps:
|
|
10
|
+
1. Design Philosophy Creation (.md file)
|
|
11
|
+
2. Express by creating it on a canvas (.pdf file or .png file)
|
|
12
|
+
|
|
13
|
+
First, undertake this task:
|
|
14
|
+
|
|
15
|
+
## DESIGN PHILOSOPHY CREATION
|
|
16
|
+
|
|
17
|
+
To begin, create a VISUAL PHILOSOPHY (not layouts or templates) that will be interpreted through:
|
|
18
|
+
- Form, space, color, composition
|
|
19
|
+
- Images, graphics, shapes, patterns
|
|
20
|
+
- Minimal text as visual accent
|
|
21
|
+
|
|
22
|
+
### THE CRITICAL UNDERSTANDING
|
|
23
|
+
- What is received: Some subtle input or instructions by the user that should be taken into account, but used as a foundation; it should not constrain creative freedom.
|
|
24
|
+
- What is created: A design philosophy/aesthetic movement.
|
|
25
|
+
- What happens next: Then, the same version receives the philosophy and EXPRESSES IT VISUALLY - creating artifacts that are 90% visual design, 10% essential text.
|
|
26
|
+
|
|
27
|
+
Consider this approach:
|
|
28
|
+
- Write a manifesto for an art movement
|
|
29
|
+
- The next phase involves making the artwork
|
|
30
|
+
|
|
31
|
+
The philosophy must emphasize: Visual expression. Spatial communication. Artistic interpretation. Minimal words.
|
|
32
|
+
|
|
33
|
+
### HOW TO GENERATE A VISUAL PHILOSOPHY
|
|
34
|
+
|
|
35
|
+
**Name the movement** (1-2 words): "Brutalist Joy" / "Chromatic Silence" / "Metabolist Dreams"
|
|
36
|
+
|
|
37
|
+
**Articulate the philosophy** (4-6 paragraphs - concise but complete):
|
|
38
|
+
|
|
39
|
+
To capture the VISUAL essence, express how the philosophy manifests through:
|
|
40
|
+
- Space and form
|
|
41
|
+
- Color and material
|
|
42
|
+
- Scale and rhythm
|
|
43
|
+
- Composition and balance
|
|
44
|
+
- Visual hierarchy
|
|
45
|
+
|
|
46
|
+
**CRITICAL GUIDELINES:**
|
|
47
|
+
- **Avoid redundancy**: Each design aspect should be mentioned once. Avoid repeating points about color theory, spatial relationships, or typographic principles unless adding new depth.
|
|
48
|
+
- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final work should appear as though it took countless hours to create, was labored over with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like "meticulously crafted," "the product of deep expertise," "painstaking attention," "master-level execution."
|
|
49
|
+
- **Leave creative space**: Remain specific about the aesthetic direction, but concise enough that the next Claude has room to make interpretive choices also at a extremely high level of craftmanship.
|
|
50
|
+
|
|
51
|
+
The philosophy must guide the next version to express ideas VISUALLY, not through text. Information lives in design, not paragraphs.
|
|
52
|
+
|
|
53
|
+
### PHILOSOPHY EXAMPLES
|
|
54
|
+
|
|
55
|
+
**"Concrete Poetry"**
|
|
56
|
+
Philosophy: Communication through monumental form and bold geometry.
|
|
57
|
+
Visual expression: Massive color blocks, sculptural typography (huge single words, tiny labels), Brutalist spatial divisions, Polish poster energy meets Le Corbusier. Ideas expressed through visual weight and spatial tension, not explanation. Text as rare, powerful gesture - never paragraphs, only essential words integrated into the visual architecture. Every element placed with the precision of a master craftsman.
|
|
58
|
+
|
|
59
|
+
**"Chromatic Language"**
|
|
60
|
+
Philosophy: Color as the primary information system.
|
|
61
|
+
Visual expression: Geometric precision where color zones create meaning. Typography minimal - small sans-serif labels letting chromatic fields communicate. Think Josef Albers' interaction meets data visualization. Information encoded spatially and chromatically. Words only to anchor what color already shows. The result of painstaking chromatic calibration.
|
|
62
|
+
|
|
63
|
+
**"Analog Meditation"**
|
|
64
|
+
Philosophy: Quiet visual contemplation through texture and breathing room.
|
|
65
|
+
Visual expression: Paper grain, ink bleeds, vast negative space. Photography and illustration dominate. Typography whispered (small, restrained, serving the visual). Japanese photobook aesthetic. Images breathe across pages. Text appears sparingly - short phrases, never explanatory blocks. Each composition balanced with the care of a meditation practice.
|
|
66
|
+
|
|
67
|
+
**"Organic Systems"**
|
|
68
|
+
Philosophy: Natural clustering and modular growth patterns.
|
|
69
|
+
Visual expression: Rounded forms, organic arrangements, color from nature through architecture. Information shown through visual diagrams, spatial relationships, iconography. Text only for key labels floating in space. The composition tells the story through expert spatial orchestration.
|
|
70
|
+
|
|
71
|
+
**"Geometric Silence"**
|
|
72
|
+
Philosophy: Pure order and restraint.
|
|
73
|
+
Visual expression: Grid-based precision, bold photography or stark graphics, dramatic negative space. Typography precise but minimal - small essential text, large quiet zones. Swiss formalism meets Brutalist material honesty. Structure communicates, not words. Every alignment the work of countless refinements.
|
|
74
|
+
|
|
75
|
+
*These are condensed examples. The actual design philosophy should be 4-6 substantial paragraphs.*
|
|
76
|
+
|
|
77
|
+
### ESSENTIAL PRINCIPLES
|
|
78
|
+
- **VISUAL PHILOSOPHY**: Create an aesthetic worldview to be expressed through design
|
|
79
|
+
- **MINIMAL TEXT**: Always emphasize that text is sparse, essential-only, integrated as visual element - never lengthy
|
|
80
|
+
- **SPATIAL EXPRESSION**: Ideas communicate through space, form, color, composition - not paragraphs
|
|
81
|
+
- **ARTISTIC FREEDOM**: The next Claude interprets the philosophy visually - provide creative room
|
|
82
|
+
- **PURE DESIGN**: This is about making ART OBJECTS, not documents with decoration
|
|
83
|
+
- **EXPERT CRAFTSMANSHIP**: Repeatedly emphasize the final work must look meticulously crafted, labored over with care, the product of countless hours by someone at the top of their field
|
|
84
|
+
|
|
85
|
+
**The design philosophy should be 4-6 paragraphs long.** Fill it with poetic design philosophy that brings together the core vision. Avoid repeating the same points. Keep the design philosophy generic without mentioning the intention of the art, as if it can be used wherever. Output the design philosophy as a .md file.
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## DEDUCING THE SUBTLE REFERENCE
|
|
90
|
+
|
|
91
|
+
**CRITICAL STEP**: Before creating the canvas, identify the subtle conceptual thread from the original request.
|
|
92
|
+
|
|
93
|
+
**THE ESSENTIAL PRINCIPLE**:
|
|
94
|
+
The topic is a **subtle, niche reference embedded within the art itself** - not always literal, always sophisticated. Someone familiar with the subject should feel it intuitively, while others simply experience a masterful abstract composition. The design philosophy provides the aesthetic language. The deduced topic provides the soul - the quiet conceptual DNA woven invisibly into form, color, and composition.
|
|
95
|
+
|
|
96
|
+
This is **VERY IMPORTANT**: The reference must be refined so it enhances the work's depth without announcing itself. Think like a jazz musician quoting another song - only those who know will catch it, but everyone appreciates the music.
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## CANVAS CREATION
|
|
101
|
+
|
|
102
|
+
With both the philosophy and the conceptual framework established, express it on a canvas. Take a moment to gather thoughts and clear the mind. Use the design philosophy created and the instructions below to craft a masterpiece, embodying all aspects of the philosophy with expert craftsmanship.
|
|
103
|
+
|
|
104
|
+
**IMPORTANT**: For any type of content, even if the user requests something for a movie/game/book, the approach should still be sophisticated. Never lose sight of the idea that this should be art, not something that's cartoony or amateur.
|
|
105
|
+
|
|
106
|
+
To create museum or magazine quality work, use the design philosophy as the foundation. Create one single page, highly visual, design-forward PDF or PNG output (unless asked for more pages). Generally use repeating patterns and perfect shapes. Treat the abstract philosophical design as if it were a scientific bible, borrowing the visual language of systematic observation—dense accumulation of marks, repeated elements, or layered patterns that build meaning through patient repetition and reward sustained viewing. Add sparse, clinical typography and systematic reference markers that suggest this could be a diagram from an imaginary discipline, treating the invisible subject with the same reverence typically reserved for documenting observable phenomena. Anchor the piece with simple phrase(s) or details positioned subtly, using a limited color palette that feels intentional and cohesive. Embrace the paradox of using analytical visual language to express ideas about human experience: the result should feel like an artifact that proves something ephemeral can be studied, mapped, and understood through careful attention. This is true art.
|
|
107
|
+
|
|
108
|
+
**Text as a contextual element**: Text is always minimal and visual-first, but let context guide whether that means whisper-quiet labels or bold typographic gestures. A punk venue poster might have larger, more aggressive type than a minimalist ceramics studio identity. Most of the time, font should be thin. All use of fonts must be design-forward and prioritize visual communication. Regardless of text scale, nothing falls off the page and nothing overlaps. Every element must be contained within the canvas boundaries with proper margins. Check carefully that all text, graphics, and visual elements have breathing room and clear separation. This is non-negotiable for professional execution. **IMPORTANT: Use different fonts if writing text. Search the `./canvas-fonts` directory. Regardless of approach, sophistication is non-negotiable.**
|
|
109
|
+
|
|
110
|
+
Download and use whatever fonts are needed to make this a reality. Get creative by making the typography actually part of the art itself -- if the art is abstract, bring the font onto the canvas, not typeset digitally.
|
|
111
|
+
|
|
112
|
+
To push boundaries, follow design instinct/intuition while using the philosophy as a guiding principle. Embrace ultimate design freedom and choice. Push aesthetics and design to the frontier.
|
|
113
|
+
|
|
114
|
+
**CRITICAL**: To achieve human-crafted quality (not AI-generated), create work that looks like it took countless hours. Make it appear as though someone at the absolute top of their field labored over every detail with painstaking care. Ensure the composition, spacing, color choices, typography - everything screams expert-level craftsmanship. Double-check that nothing overlaps, formatting is flawless, every detail perfect. Create something that could be shown to people to prove expertise and rank as undeniably impressive.
|
|
115
|
+
|
|
116
|
+
Output the final result as a single, downloadable .pdf or .png file, alongside the design philosophy used as a .md file.
|
|
117
|
+
|
|
118
|
+
---
|
|
119
|
+
|
|
120
|
+
## FINAL STEP
|
|
121
|
+
|
|
122
|
+
**IMPORTANT**: The user ALREADY said "It isn't perfect enough. It must be pristine, a masterpiece if craftsmanship, as if it were about to be displayed in a museum."
|
|
123
|
+
|
|
124
|
+
**CRITICAL**: To refine the work, avoid adding more graphics; instead refine what has been created and make it extremely crisp, respecting the design philosophy and the principles of minimalism entirely. Rather than adding a fun filter or refactoring a font, consider how to make the existing composition more cohesive with the art. If the instinct is to call a new function or draw a new shape, STOP and instead ask: "How can I make what's already here more of a piece of art?"
|
|
125
|
+
|
|
126
|
+
Take a second pass. Go back to the code and refine/polish further to make this a philosophically designed masterpiece.
|
|
127
|
+
|
|
128
|
+
## MULTI-PAGE OPTION
|
|
129
|
+
|
|
130
|
+
To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.
|