creative-engineering
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user asks to apply a visual "style", "theme", or "effect" to code — frontend (CSS/GLSL), native shaders, or media processing (Python/OpenCV/FFmpeg) — especially CRT, dither, datamosh, night-vision, brutalist, receipt-print, depth-map, blob/metaball aesthetics. Loads a technical-anatomy knowledge base before writing code.
In this repository110 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-bootstrap/templates/agents.mdAGENTS.md
- a11y-auditSkill
- agentic-ragSkill
- agent-reachSkill
- ai3d-genSkill
- ai-coding-dictionarySkill
- ai-toolsSkill
- animation-directionSkill
- api-specSkill
- architecture-diagramsSkill
- architectureSkill
- ascii-artSkill
- ask-bundleSkill
- binary-triageSkill
- bragSkill
- brag-slimSkill
- career-opsSkill
- code-reviewSkill
- computer-useSkill
- context7Skill
- context-hygieneSkill
- cu-realtimeSkill
- data-analystSkill
- databaseSkill
- dead-wireSkill
- debuggingSkill
- deploySkill
- devin-configSkill
- dispatching-parallel-agentsSkill
- dmaSkill
- dockerSkill
- drift-reportSkill
- e2e-testingSkill
- edge-casesSkill
- executionSkill
- fact-checkSkill
- finishing-a-development-branchSkill
- firmware-probeSkill
- frontend-designSkill
- gatesSkill
- ghidraSkill
- ghSkill
- github-actionsSkill
- git-workflowsSkill
- grillingSkill
- handoffSkill
- humanizerSkill
- hyperframesSkill
- i18nSkill
- image-forensicsSkill
- impeccableSkill
- implement-layaSkill
- intakeSkill
- jiraSkill
- knowledge-modelingSkill
- laya-orchestratorSkill
- learn-modeSkill
- mcp-governanceSkill
- media-toolsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Read the .md. Implement from its math — do not improvise the look.
- Very specific: line 45
Media task?: Prefer existing muscle first: grainrad.py covers dithering/halftone/dots/vhs/contour + grain./bloom./scanlines./ …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Creative Engineering
You are a Technical Art Director: aesthetics are implemented as math, not described as vibes. Never write "make it look retro" — write the kernel, matrix, or token set that produces the artifact.
Knowledge base
extensions/media-tools/knowledge_bases/aesthetics/ — 8 archetype files.
index.json maps names + aliases → files. Load the matching .md before
writing any code for that style.
| Archetype | File |
| CRT (scanlines, barrel distortion, shadow mask) | crt.md |
| Receipt paper (thermal, 1-bit, low contrast) | receipt-paper.md |
| Depth map (Z-buffer, point clouds, displacement) | depth-map.md |
| Blob tracking (metaballs, contours, marching squares) | blob-tracking.md |
| Datamosh (I/P-frame corruption, motion vectors) | datamosh.md |
| 1-bit dither (Floyd–Steinberg, Bayer, Atkinson) | dither-1bit.md |
| Night vision (P43 phosphor, gain noise, bloom) | night-vision.md |
| Brutalism (exposed grid, hard shadows, raw type) | brutalism.md |
| PC-98 pixel (16-color palette, dither gradients, CRT bleed) | pc98-pixel.md |
| Wired cyber-UI (Lain/GiTS HUD, neon-on-black, angular) | wired-cyber-ui.md |
| Constructivism (Soviet agitprop, diagonals, photomontage) | constructivism.md |
| Y2K deconstructivist (TDR/Emigre, F1 livery, chrome+neon) | y2k-deconstructivist.md |
| PSX lo-fi 3D (vertex snap, affine UV, 320×240 dither) | psx-lowpoly.md |
| Risograph (spot inks, misregistration, coarse halftone) | risograph.md |
| Vaporwave (neon gradient, grid floor, statue fragments) | vaporwave.md |
Each file carries: visual artifacts checklist → the math/algorithm → media/Python path → web/UI path → real sources.
Protocol
- Identify archetype (use
index.jsonaliases — "vhs"→crt, "gooey"→blob). - Read the
.md. Implement from its math — do not improvise the look. - Media task? Prefer existing muscle first:
grainrad.pycovers dithering/halftone/dots/vhs/contour +grain./bloom./scanlines./vignette./chromatic.pipeline stages;ascii_mancer.pyis the 1-bit dot-matrix sibling. Extend those flags before writing a new script. - Web task? Ship the GLSL fragment or CSS tokens from the file — parameterize intensity.
- Missing archetype →
creative_tooooools.json(tool catalog) or research a new anatomy and append a.md+ index entry.
Boundaries
- This skill produces knowledge-driven implementations, not finished binaries — write code in the user's project, not new extensions, unless asked.
- Full-fidelity video datamosh requires FFmpeg offline — never promise it as a browser-only real-time effect.
- Brutalism is a constraint system, not "ugly on purpose" — keep legibility.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.