wire-art
Skill874 starsChanged 6 days agoMITView on GitHub
Draw Genex's canvas illustrations (loading, empty and being-made states) in its wireframe language - beam-scanned solids, flat marks extruded with depth, real tool logos - and explore them as rendered variants before code. Use when a surface needs a drawing, an icon with depth or a "making" state.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-event-typeSkill
- add-ipc-channelSkill
- add-plugin-toolSkill
- better-colorsSkill
- better-layoutSkill
- better-typographySkill
- better-uiSkill
- better-writingSkill
- breakSkill
- harness-incident-fixSkill
- run-area-testsSkill
- variantSkill
- verify-ui-via-dev-controlSkill
- add-event-typeSkill
- add-ipc-channelSkill
- add-plugin-toolSkill
- better-colorsSkill
- better-layoutSkill
- better-typographySkill
- better-uiSkill
- better-writingSkill
- breakSkill
- harness-incident-fixSkill
- run-area-testsSkill
- variantSkill
- verify-ui-via-dev-controlSkill
- wire-artSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 43
Test in tests/conformance/: bounds at every moment, size, still frames, determinism.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Wire art
Genex draws its illustrations on canvas in one wireframe language: the empty states
(ui/WireArt.tsx, ui/wire-computer.ts), the welcome (onboarding/ArtCanvas.tsx) and the
Assets making cards (making-shapes.ts, making-art.ts, panels/MakingArt.tsx). Reuse those
modules before writing new geometry. The owner chose this language; keep it, don't restyle it.
The look
- Lines, not pictures. Edges in a theme colour (an accent and ink mix, read from CSS), dimmed with depth, plus a faint nonzero fill of the faces for body. No gradients, no shadows, no photos, no emoji.
- Small subjects. A subject takes about half of its area and never crosses its edges or the card's chips and label. Prove the bounds in a unit test over every moment of the loop.
- Real forms. Solids are recognisable: a body scan of a person (level contours, believable proportions), the Utah teapot, cobblestones on a tilted plane for a texture. Offer several takes of a figure; the first one is rarely right.
- Marks with depth. A flat icon (image, video, sound, a vendor mark) is extruded into a few slices, brightest at the front, swaying slowly on its vertical axis: 2D with 3D. Keep it simple and rounded: an image is a rounded-corner picture, a video a rounded play shape, a sound a few waves. Vendor marks keep their own paths, unaltered.
- One motion that means something. A beam sweeps up and down the subject: below it is built, above it stays faint but visible. Waiting, failed or finished states are grey and still. Everything holds a still frame under Reduce Motion, when hidden, inert or off screen.
- Tools by their logos. Name the tool doing the work by its own mark on a small dark tile and its short name; never a borrowed mark for a plugin that ships none.
Building one
- Geometry is pure and deterministic: a function of
t(seconds) that returns line segments and polygons in the art's own pixel box, with no DOM. Samet, same frame;NaNstill draws. - Paint in alpha buckets (one stroke per bucket), glow only the brightest buckets with a small blur scaled to the backing store, and size the backing store to the shown size so canvas zoom stays sharp.
- Loop at 30 fps through the
MakingArt/WireArtloop: it already pauses for hidden documents, intersection, inert ancestors,data-motion="rest"and Reduce Motion. A rest frame never changes pose on a repaint. - Test in
tests/conformance/: bounds at every moment, size, still frames, determinism.
Designing one
Explore on the Design canvas before code: render several real variants per round (the actual
canvas drawing, not a sketch), publish every round to the canvas the owner is looking at, take
their notes, and implement only after they approve. Then check the rendered app in both themes
under docs/agent/design.md.
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.

