agentleFS
enesozturkenesozturk/dimensional-drawing/skills/dimensional-drawing-motion/SKILL.md

dimensional-drawing-motion

Skill1.7k starsChanged 24 days agoMITView on GitHub

Turn a finished dimensional drawing sheet into a ~10 s Apple-style motion film — lines draw themselves in, the camera pulls back, layers lift into an exploded view, the full sheet resolves. Use after the dimensional-drawing skill, or when asked to animate a spec sheet or anatomy drawing.

1 other project uses a version of this, 1 of them edited.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 6 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the enesozturk/dimensional-drawing repository that our weekly crawl found: only 7 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about enesozturk/dimensional-drawing

The biggest 5 of 7 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 7
  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. forge-ui/forge★ 1993% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    Start from templates/scene-dialog.js + templates/base.css.

    line 10
  2. Very specific:

    Registration: Call at(start, stagger, dur) before drawing a group.

    line 38
  3. Distinctive:

    Check frames at the key beats (0, 1.2, 2.4, 3.3, 4.6, 5, 5.9, 6.6, 8, 10, 11 s scene time).

    line 51
  4. Distinctive:

    No music or voice unless asked.

    line 59

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dimensional drawing → motion

Animate a sheet made with the dimensional-drawing skill. The film reads like a pen drawing the sheet while a camera moves over it. Same rules as the drawing: monochrome, slots not content, variable codes, unbranded.

Start from templates/scene-dialog.js + templates/base.css. It is the reference film (11 s, 1920×1080, 60 fps). Adapt it; do not start blank.

Where it runs

You areUse
Claude on claude.ai with the Motion artifact typeadapters/claude-motion.md. This is the primary, tuned target.
Any other agent / no Claudeadapters/headless/: Playwright draws each frame, ffmpeg encodes. npm install, then node render.mjs --scene … --css … --out film.mp4.

The scene is the same file in both. It only needs a tiny kit (seg, lerp, eo, ei, eio, clamp01, stage, h, css, scene) and must be a pure function of time: render(t) sets every property from t alone, never from the previous frame. That is what lets a headless renderer jump to any frame.

Other animation libraries (Remotion, Motion Canvas, GSAP, Lottie…) are not tested. Porting is possible because the scene is pure, but check the library's license first (Remotion needs a company license above 3 people).

Choreography (reference timing, seconds)

Scene time is scaled with t = t / 0.85, so the numbers below run about 15 % faster on screen. Change that one factor to speed up or slow down the whole film.

  1. 0 – 2.3 · Close-up on the header. Camera at ~4.4× on the top-left of the plan. The outer border draws from the top-left corner, then the lead circle, the X-box, the title slot, the header divider, then the header dims (S1, Z1, S5, H1). Tiny drift (z 4.4 → 4.2) keeps it alive.
  2. 2.3 – 4.2 · Pull back to the plan view. Log-zoom to ~1.7×. While moving, the rest of the plan draws: trail control, body well, content slots, label/value slots, footer actions, centerlines, chained dims top/bottom/left/right, radius callouts, boxed notes, detail circles, view title.
  3. 4.2 – 7.2 · Layers lift. The camera eases left to where the exploded view lives. Copies of container → body → slots morph from the flat plan matrix to the axonometric matrix and rise to their z. Strokes first, fills after (fills fade in from a+0.55 to a+1.25); without that a white fill flashes over the drawing. Static bottom layers (viewport, scrim, shadow) draw in under them; leaders and layer labels follow.
  4. 7.2 – 9.2 · Pull back to the full sheet. Zoom to 1.0. The sheet border draws, then notes, tables and the detail views (header controls, footer actions, viewport placement, nested corner, field, radius details) each draw in a 0.3–0.5 s burst.
  5. 9.2 – end · Hold. Very slow push (z 0.998 → 0.988) so the last frame is not dead.

Total ~11 s. Keep films 8–15 s.

How the template works

  • One SVG, one camera. The sheet is drawn once in init at viewBox 0 0 1900 1060 (wider than the 1700 drawing so the final frame fills 16:9 with no side gutters). A wrapper .dw-cam gets translate(960 − cx·z, 540 − cy·z) scale(z) from camera keys DW_CAM = [{t, cx, cy, z}], interpolated with ease-in-out and log zoom (exp(lerp(log z0, log z1, p))), so zooms feel even.
  • Registration. Call at(start, stagger, dur) before drawing a group. Every element made by mk() after it gets a window [start + i·stagger, … + dur]. Group elements in drawing order: outline → structure → slots → dims → labels.
  • Two kinds of element.
    • d (drawn): solid strokes. pathLength=1, strokeDasharray: 1 2, strokeDashoffset: 1 → 0 with ease-in-out; fill fades in over the last 45 %.
    • f (faded): text, dashed slots, centerlines, envelopes, hatches. Opacity with ease-out. Dashed lines can't use the dash trick, so they fade.
  • Morph groups. mg(z, start) makes a group that lerps its matrix from flat = [k,0,0,k,PX,PY] (the plan) to iso = [.94s,.17s,−.34s,.47s,TX,TY] and subtracts z·v from ty. Set --u = 1/√|det M| each frame so stroke widths stay constant while the group scales.
  • Performance. Values are quantized to 1/400 and skipped when unchanged; fills of morph groups are queried once.

Adapting to a new component

  1. Copy the drawing sheet's geometry (plan origin PX, PY, scale k, the r()/dimH()/dimV()/rad()/nb()/detailRef()/table()/notes() calls) into init, keeping the template's helpers.
  2. Rewrite the at() timeline for the new plan: open on its most characteristic corner (header, handle, notch), let the rest of the plan draw while pulling back.
  3. List the layers for the exploded view (bottom static ones with G(z), lifting ones with mg(z, start)), 0.1 s apart.
  4. Retarget DW_CAM: close-up → plan center → exploded center → sheet center (950, 530, z ≈ 1).
  5. Check frames at the key beats (0, 1.2, 2.4, 3.3, 4.6, 5, 5.9, 6.6, 8, 10, 11 s scene time). Look for: elements popping instead of drawing, fills flashing, labels outside the frame mid-move, a busy first second.
  6. Render (Motion export, or render.mjs).

Style rules for motion

  • One thing leads at a time: the eye follows the pen. Dims come after the geometry they measure; labels after their leaders.
  • Ease-in-out for camera and strokes, ease-out for fades. No bounce, no overshoot, no color.
  • Background white, ink #111, grays only. Arimo/Helvetica caps lettering, same sizes as the sheet.
  • No music or voice unless asked.

Reply in one or two sentences with the film's length and what each beat shows.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.