math-tasks/assets/items/asteroids/CLAUDE.md

58 lines
2.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Asteroid Asset Generation Rules
## Style overview
The set has two tiers:
**Single-piece asteroids (asteroid1asteroid9)** — each is a standalone rock with its own unique shape and crack color. They serve as style sources for multi-piece variants.
**Multi-piece asteroids (asteroid10asteroid14)** — compact clusters of 3 pieces tightly pressed together. Each one inherits its style from a corresponding single-piece asteroid.
## Style map
| File | Shape type | Crack color | Style source |
|------|-----------|-------------|--------------|
| asteroid1 | round sphere | orange/amber | — |
| asteroid3 | flat angular boulder | red glowing | — |
| asteroid5 | tall elongated shard | purple/magenta | — |
| asteroid7 | flat horizontal disc | pink/purple | — |
| asteroid9 | tall spire with spikes | cyan/blue | — |
| asteroid11 | 3-piece cluster | red (from asteroid3) | asteroid3 |
| asteroid12 | 3-piece cluster | orange/golden (from asteroid1) | asteroid1 — **ideal composition reference** |
| asteroid13 | 3-piece cluster | purple/magenta (from asteroid5) | asteroid5 |
## Rules for generating new multi-piece asteroids
### Composition
- Always 3 pieces of **different sizes** tightly pressed together
- Pieces must touch each other — no gaps, no space between them
- The cluster must read as one compact object, not a scattered group
- Vary the arrangement: triangle, stacked, side-by-side — avoid repeating the same layout
### Style
- Use `--ref` with the corresponding single-piece asteroid (not asteroid12)
- Do not use `--template illustration` — it makes cracks too prominent and overrides the source style
- Use the default `--template general`
- Crack color, surface texture, and painting style must come from the reference
### What to avoid
- No floating debris or separate small fragments
- No explosion effects
- No atmospheric glow, energy bursts, or lightning spread outward from the object
- No changing the crack color relative to the reference (e.g. if the ref has red cracks, the output must have red cracks — not orange, not purple)
## Generation command pattern
```bash
node .claude/skills/gen-image/banatie-gen.mjs \
--prompt "three dark rocky asteroid pieces of different sizes tightly pressed together, <crack description from ref>, painterly art style, white background, compact cluster no gaps between stones, varied shapes and sizes" \
--output assets/items/asteroids/asteroidN.png \
--ref assets/items/asteroids/asteroidX.png
```
Where `asteroidX` is the style source from the table above.
## Approved reference for composition
**asteroid12.png** is the approved example of correct multi-piece composition: compact, no gaps, pieces vary in size, reads as one unit. Use it as a visual benchmark when evaluating new generations — but do NOT add it as `--ref` alongside the style source, as it will pull the style toward orange/golden.