Menü
Use when adding an entry to docs/effects.md for a new visual effect
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when adding a new transform effect, creating a post-process shader, or planning effect implementation. Provides the complete checklist of files and commonly-missed steps.
Use when exploring a vague idea, finding inspiration, or researching a technique before planning. Triggers on "I want to add...", "what if...", "research", "look up", or when uncertain about what to build.
Use when creating a git commit for staged or unstaged changes. Triggers on "commit this", "save my changes", or when implementation work completes and needs version control.
Use when creating a tagged release with changelog. Triggers on "release", "tag a release", "cut a release", or when ready to publish a new version.
Use when reviewing an implemented feature against its plan document. Triggers after implementation completes, on "review this", or when checking if code matches specification.
Use when planning a new feature before implementation. Triggers on "plan", "design", "architect", or when describing a feature to build.
| name | write-effect-description |
| description | Use when adding an entry to docs/effects.md for a new visual effect |
One sentence, 20 words max, describing what the viewer SEES — not what the shader does.
For new effects: check for image.png in the repo root first. If it exists, read it with the Read tool. If it does not exist, ask the user to provide a file path to a screenshot. Ground the description in what you actually see — not what the shader code implies.
This applies only when adding a new effect to the inventory. Rewrites of existing descriptions do not require a screenshot.
Utility/technical effects (Gamma, FXAA, Clarity, Chromatic Aberration, Solid Color) may use terse, technical descriptions. The one-sentence-analogy treatment applies only to creative visual effects — not correction or signal-processing tools.
| Bad (too long / listy) | Good (single impression) |
|---|---|
| Overlapping planes of scrolling characters dissolving into abstract texture — rows drift at different speeds, letters flicker and swap, and an optional LCD stripe grid turns everything into a glowing monitor closeup | Scrolling character grids layered at different depths, dissolving into flickering abstract texture |
| Colored bars scrolling and crowding together toward a focal point, switchable between venetian blinds, a spinning spoke fan, and concentric rings — with a snap mode that makes them lurch like a stuck reel | Colored bars crowding toward a focal point like a stuck projector reel lurching forward |
| Ray-sphere intersection with spherical UV tiling and facet normal perturbation | Spinning mirror ball throwing dancing light spots across the walls |
| Golden-angle Vogel disc blur with brightness weighting for bright pixel emphasis | Dreamy out-of-focus blur where bright spots become soft glowing circles |
| Computes voronoi geometry with multiple blendable cell-based effects | Jittering cells with glowing seams and ridged surfaces like magnified soap film |
| Edge detection with directional strokes and paper texture overlay | Hand-drawn graphite shading on rough paper |
| Old tube monitor with visible phosphor dots, curved glass, dim edges, and faint horizontal scan lines | Curved glass tube TV with visible phosphor RGB dots and dark scanlines like a retro arcade cabinet |
| Renders image as text characters (# @ * .) based on brightness | Image rebuilt in blocky terminal characters like a green-screen computer printout |
| Tiles the image into repeating square or hexagonal grids | Honeycomb of tiny kaleidoscopes where each cell mirrors and folds the image inward |
