cartoon-3d-short
Skill2.3k starsChanged 16 days agoMITView on GitHub
Make a ~55-70 s vertical cartoon story short in the "2D characters in a colourful 3D world" style (flat bean-head cartoon cards with ink outlines, painted 3D town/world with black ink lines, saturated sky, depth-of-field backgrounds, gliding cameras, voice narration, synthesized SFX + march-style music), rendered with three.js inside Remotion. Proven on "The Bridge That Fell for a Song" (2026-10-31). Use when the user asks for another video "like the bridge video", "like the soldiers/bridge short", "in that cartoon 3D style", a history/science story short with cartoon characters in 3D, or says "use the cartoon short skill".
4 other projects use a version of this, 3 of them edited; 2 of 3 edited versions we compared changed its rules; 2 new projects in the last 4 weeks, against 1 the 4 before.
How people change it
2 of 3 edited versions changed its rules.
Of the 3 edited versions we compared: 1 keep every rule, 2 made changes of their own.
Rules people drop
- Put them in the project folder, e.g.
~/bridge-short/voice/.dropped by 1 of 2 - Look checks. Run
node scripts/bridge-stills.mjs out/<name>/x_ 100,400 0.5.dropped by 1 of 2
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Rising: 2 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data
Most recently taken up by
- opradopedro/claude-skillsword for word, first seen Nov 16, 2026
- owlinthebarnai/video-studio-kitedited, first seen Nov 16, 2026
- VUXXE/cartoon-3d-shortedited, first seen Nov 15, 2026
- EssouliAnas/claude-animated-shortsedited, first seen Nov 8, 2026
Who's talking about mromidev/claude-animated-shorts
- Mr omi“How to Make Viral Animated Shorts Using Claude (Full Workflow)”YouTube · Nov 1, 2026 · 923k views
- Bhupesh Thukral“Make Animated Story Shorts With One Line to Claude (Free)”YouTube · Nov 6, 2026 · 7.1k views
- Dream AI Labs“조회수 3천만 쇼츠 스타일, Claude 무료 스킬로 직접 만들어 봤습니다”YouTube · Nov 6, 2026 · 6.8k views
- Adil Elali || عادل العلي“كلود صار يعمل أنميشن بتجيب ملايين المشاهدات”YouTube · Nov 7, 2026 · 5.2k views
- Ailization“Этот мультик целиком собрал Claude Code #Shorts”YouTube · Nov 5, 2026 · 3.5k views
The biggest 5 of 34 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 34
Talked about on YouTube, the web and GitHub (34 times).
On YouTube · 20
- Nov 1, 2026How to Make Viral Animated Shorts Using Claude (Full Workflow) — Mr omi923k views · 1.1k comments
- Nov 6, 2026Make Animated Story Shorts With One Line to Claude (Free) — Bhupesh Thukral7.1k views · 23 comments
- Nov 6, 2026조회수 3천만 쇼츠 스타일, Claude 무료 스킬로 직접 만들어 봤습니다 — Dream AI Labs6.8k views · 5 comments
- Nov 7, 2026كلود صار يعمل أنميشن بتجيب ملايين المشاهدات — Adil Elali || عادل العلي5.2k views · 11 comments
- Nov 5, 2026Этот мультик целиком собрал Claude Code #Shorts — Ailization3.5k views · 3 comments
15 more on YouTube
- Nov 3, 2026영상 AI 구독 없이 클로드로 애니 쇼츠 만들기 — 해봄연구소3.3k views · 1 comment
- Nov 2, 2026클로드 애니메이션 만들기 claude animated shorts 코드로 그린 애니 브로턴 현수교 붕괴 18분 — 츄즈잇 CHOO's IT2.2k views
- Nov 4, 2026Claude Can Now Make Cartoon Films (Free Skill) — Evolution with AI1.4k views
- Nov 8, 20263 GitHub-Repos, die Claude zum Videostudio machen #shorts — Onur Sinoplu481 views
- Nov 8, 2026Animasyon Reposuyla Codex ve Claude Code’la Shorts Ürettim — Cepksat392 views
- Nov 4, 2026Claude Made This Cartoon: Free Skill, Every Frame Is Code — Ivo Nikolov304 views
- Nov 4, 2026Claude Can Now Make Real Cartoon Animation (Free Skill, I Tested It) — Evolution with AIsays it tested it237 views · 2 comments
- Nov 3, 2026Make viral 3D animated shorts with Claude 🤖 — LookOnThisGit217 views · 2 comments
- Nov 9, 2026Start Your Cartoon Channel with Claude: Free Open-Source AI Animation 🎬 — Skyyskill Ai Academy215 views · 2 comments
- Nov 3, 2026不用 AI 视频生成器,也能做动画故事短片 #Shorts — jyfk-sys193 views
- Nov 8, 2026claude-animated-shorts GitHub Explained: Deterministic Animation with Remotion and WebGL — Alex Hitt78 views
- Nov 10, 2026무료로 조회수 터지는 3D 쇼츠 만드는 법 (주문·스킬 무료 공개) — 정기적 자동화57 views · 1 comment
- Nov 7, 2026AIが書くコードで67秒の縦アニメが完成|Claude Code 利用者向け claude-animated-shorts|three.js+Remotionを自分のPCで動かす — さつきのOSS研究室23 views · 1 comment
- Nov 9, 2026Claude Can Edit Videos Now? 6 Viral Claims, Explained — Clone.ai_creatives18 views
- Nov 7, 2026This Free Skill Makes Cartoon Shorts With Zero AI Video: claude-animated-shorts Explained — CommitCastTech14 views
On the web · 8
- Nov 10, 2026Claude Animated Shorts: o repositório grátis que transforma o Claude Code num estúdio de animação | Castilho IA — castilhoia.com
- Nov 9, 2026Some code still needs human review! But Claude can help. ... — linkedin.com
- Nov 8, 2026Free Claude skills that render finished video in code — sloptvnews.com
- Nov 4, 2026How to Make Viral Animated Shorts with Claude Code Using the Claude Animated Shorts Skill — AI Skills — aiskills.one
- Nov 4, 2026Claude Animated Shorts: What It Does, Setup & Verdict — morelime2.com
3 more on the web
- Nov 4, 2026Claude Animated Shorts (`mromidev/claude-animated-shorts`) Guide (2026): 3D Three.js + Remotion Cartoon Skill & Creator Workflow — waveweaver.io
- Nov 4, 2026Claude Animated Shorts: cartoon story shorts rendered in code · Devalley — devalley.app
- Nov 3, 2026今日のAIニュース10(11/3)|NTTデータ委託先の不正アクセス、社債購入者の情報にも影響|おじぎねこ🐱 — note.com
On GitHub · 6
- Nov 9, 2026Video tool skills: Remotion, video-use, HyperFrames, cartoon-3d-short (skills only) — ayanrindeisraeloluwabusayo-prog/website0 reactions
- Nov 9, 2026Promo kit — week of 09 Nov 2026 — pahadiji/star-catcher0 reactions
- Nov 7, 2026[GitHub Radar] 2026-11-07: 3 repo đáng xem — mrxcode-debug/pdt-github-hot-radar0 reactions
- Nov 6, 2026[Candidate] mromidev/claude-animated-shorts - cartoon-3d-short — ProSkillsMD/proskills0 reactions · 1 comment
- Nov 5, 2026agent-skills.github.mromidev.claude-animated-shorts: init at 0-unstable-2026-11-01 — sudosubin/agents.nix0 reactions
1 more on GitHub
- Nov 2, 2026mromidev 'claude-animated-shorts' — three.js와 Remotion으로 55~70초 애니메이션 숏츠를 만드는 Claude 스킬, 511스타 (11/2, GitHub) — roomedia/ax-trend0 reactions
Other versions4 projects use a version of this.
Word for word · 1
- opradopedro/claude-skills★ 0100% same
Edited · 3
- owlinthebarnai/video-studio-kit★ 41100% same
- EssouliAnas/claude-animated-shorts★ 490% same
- VUXXE/cartoon-3d-short★ 458% 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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 9 are common, 0 are distinctive, and 4 are very specific to this project.
9
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 15
Never copy their scripts, characters or shots.
- Common: line 16
Never say the channel's name in a voice-over or description.
- Common: line 19
No captions or labels in the video.
- Very specific: line 31
Write the facts with their source at the top of SCRIPT.md.
- Common: line 41
Never describe on screen what the viewer already sees.
- Very specific: line 43
Put them in the project folder, e.g.
- Common: line 53
Every visual reaction lands 0-3 frames before its word.
- Common: line 66
Every pixel parameter scales with output height / 1920.
- Very specific: line 71
Look checks: Run node scripts/bridge-stills.mjs out/<name>/x_ 100,400 0.5.
- Very specific: line 83
Start every new short from templates/bridge/ (copy to src/videos/<name>/): the look lives in these values, the story lives in story.ts / …
- Common: line 119
Every hold pushes in 0.15-0.35 %/f, with 0.6 %/f on punch words.
- Common: line 121
No hand-held float. Impact shakes flip sign every frame and decay over 7 f.
- Common: line 126
No blush or eye highlights.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cartoon 3D story short (three.js + Remotion)
Proven example: The Bridge That Fell for a Song. It is an original 67 s short about the 1831 Broughton bridge and 74 soldiers marching in step.
- Code:
src/videos/bridge/of your Remotion project (compositionBridgeShort, 1080x1920, 30 fps). - Script, voice and sound:
~/bridge-short/. - Style research:
references/.
The style reference is a channel studied privately (references/: STYLE_BIBLE.md, reports/*.md, frames/).
- Those videos are private study material. Never upload, publish or send them.
- Never copy their scripts, characters or shots. Story, characters and voice are always OUR OWN.
- Never say the channel's name in a voice-over or description.
User rules that apply:
- No captions or labels in the video.
- English only.
- Voice: one steady tone.
- Jokes are researched real facts.
- Standard mix: music +3 dB, SFX -6 dB, voice unchanged.
- Final export 2K vertical: 1440x2560,
--scale 1.3333. - Opus max verifies every check.
- Save after every step.
- "Just do it" once the script is approved.
Pipeline
- Topic and facts. Pick one surprising true story with a physical cause and effect (it should be visual), plus a simple everyday analogy that explains it.
- Write the facts with their source at the top of
SCRIPT.md.
- Write the facts with their source at the top of
- Script (~3.7 words/s, 55-70 s). Beat formula from the bridge short:
- Hook: the absurd fact in one line ("Seventy-four soldiers knocked down an iron bridge just by walking across it.").
- Setting: year, place, pride.
- Action: escalation over three or four beats, each a little bigger.
- Snap: the moment it breaks.
- Deadpan double line: "Luckily ... / Unluckily ...".
- Explanation: one physics idea through an everyday analogy (the kid on a swing).
- Consequence: the rule it created.
- Callback twist: the ending.
- Never describe on screen what the viewer already sees.
- Voice. Record or generate
voice.wav, then make its word timingswords.json(any speech-to-text with word times).- Put them in the project folder, e.g.
~/bridge-short/voice/. - Hand-fix the word timings. Everything is timed to words.json.
- Put them in the project folder, e.g.
- Shot plan in
story.ts: copytemplates/bridge/(the final bridge source, same assrc/videos/bridge/of your Remotion project) tosrc/videos/<name>/, register a new composition next toBridgeShortinsrc/Root.tsx, and rename it.SHOTS: id, a/b frames, light day/golden, crowd mode,taustory time.XFADE: crossfades at place/time changes.FLASH_AT: a white flash after the hook.CAMS: per-shot keys{f, dur?, cut?, s: f => {pos, look, fov, roll}}.KICKS: impact flip-shakes.DOF/dofAt: lens blur per beat.FOREGROUND: near framing props.- Every visual reaction lands 0-3 frames before its word.
- World.
lights.ts: LIGHTS plus the LOOK sky/river/cloud palette per light.shade.ts: two-tone shading anduntone().build.ts: town, houses and Kenney CC0 kit props, recoloured, with sight-line culling of anything blocking a camera.paint.ts: HD Canvas2D painted textures with seams painted in as dark tints.world.ts: sky shader, fog = horizon colour, river, per-frame posing, sun frozen per shot and camera-relative.
- Characters.
toon.ts: the Canvas2DPendrawing API, 600x1000 design canvas, soles at y = 975, bean heads, stick limbs, plum variable-width outline, face library.cast.ts: camera-facing billboards, crowds, effect cards, blinks, walk cycles. All billboards go on theNOINKlayer.cardshade.ts: cards lit by the scene light, no emissive.
- Post (
Bridge.tsx+ink.ts+lensblur.ts+grade.ts).- Composer order: ink → lens pre → lens main → bloom → NEUTRAL tone map → grade (MSAA 4).
- Every pixel parameter scales with output height / 1920.
- Sound (
~/bridge-short/audio/: timeline.py, sfx_gen.py, sfx.py, music.py, instruments.py, dsp.py, mix.py).- Event table → synthesized SFX plus an original score ducked under the voice.
- Output: mix.wav (48 kHz, exact length), stems and cues.md.
- Lock the picture's time constants before the sound is made. Any later timing change means re-running the sound.
- Look checks. Run
node scripts/bridge-stills.mjs out/<name>/x_ 100,400 0.5.- Set
BRIDGE_ENTRY=src/sandboxes/<n>/index.tsxto render a sandbox copy. - Make side-by-sides against reference frames with
python scripts/sbs_sheet.py out.jpg --ours ... --ref .... - Send them to an Opus max verifier: 1-3 images, a ≤200-word verdict.
- Set
- Final render.
npx remotion render src/index.ts <Comp> out/<name>/video.mp4 --codec h264 --crf 16 --scale 1.3333- Mux with
-map 0:v:0 -map 1:a:0(Remotion writes a silent audio track). - QA:
python scripts/short_qa.py final.mp4 out/<name>/qa shots.jsonchecks every frame for black, white, frozen and pop frames, plus loudness and sheets. - Fix anything it finds, then run a deep Opus audit.
- Deliver. SendUserFile the final mp4, update memory, write notes.
Final look values (bridge after 4 verifier rounds; all in templates/bridge/)
Start every new short from templates/bridge/ (copy to src/videos/<name>/): the look lives in these values, the
story lives in story.ts / build.ts layout / cast.ts roles. Opus max scores at the end: colour day 7, golden 5-6,
lighting 5-6, ink 6, textures 5-6, characters 7, depth 6-7, composition 6-7 (from 5/3/4/5/4/7/4/6 at the start).
- Light presets (
lights.ts, sun camera-relative and frozen per shot):- day: az 75 / el 48, lit [1.58,1.5,1.33], shade [.30,.29,.36], lift [.05,.06,.11] (cool tint ONLY in shade), sky top #3e7fd2 → horizon #b8d0ec, fog = horizon, 25→300 m, uSat 1.08, ~15 % blue haze past 60 m.
- golden: az 6 / el 7 (backlit low sun), key toward #FFB36B ×1.5, violet-blue shade (facade ≈ #444380), sky #ffc47c → #8a6f8a, peach fog only past 50 m, sun disc #ffcf9e + bloom, contact blobs + real card shadows.
- Albedos (
paint.ts/build.ts): muted brick / cream / ochre / terracotta houses with plinth, cornice, sills, hoods, door step, chimney + pot, heights 7 / 8.4 / 9.8 m; warm grey/beige stone (saturation −35 % from "storybook"); ochre wood deck C* ~51-58 with near-black seams; iron dark and desaturated. Never lemon, never lavender lit faces. - Ink (
ink.ts): #030303, 5.1 px near (6 m) → 3.3 px far (90 m) at 1080x1920, creases ×0.8 from 35°, depth jumps from 1 %, fog tint 0.3 only far; character cards on layerNOINK(they carry their own plum ink). - Lens (
lensblur.ts+dofAtin story.ts): cInf px at 1080: hook/river CU 15-16, close-ups 12-14, MS 10-12, park 7, golden sway 5, wides/aerials 0. Focus on the eyes of the front row. - Post (
Bridge.tsx): ink → lens pre → lens main → bloom (thr 1.0, int .5, 6 levels, radius .6) → NEUTRAL tone map → grade; MSAA 4. Film grain exists but is OFF (reference measures no grain; it quadruples the file size). - Characters (
toon.ts/cast.ts/cardshade.ts): bean heads h/w .94, plum ink #241726, eyes .26 W apart, no blush, 14 expressions; adults 3.5 head-heights; walk bob 5 %, lean 1-7°, planted 0.8 m stride; blinks 0.5-2.3 s; tight contact shadow ~.5 under the feet + sun-direction tail by day; golden rim inner only (never an offset outer copy). - Camera (
story.ts): cuts on big jumps, smootherstep glides 18-40 f, every hold creeps (no static hold ≥4 f), flip kicks decaying over 7 f on impacts, 4-4.6° rolls, foreground props (FOREGROUND) in ~1/3 of shots.
Look targets (measured from the reference; see references/reports/)
- Ink:
- World lines: about 3 px at 1080 wide, near-black #0b0a0c, nearly constant with distance. Silhouettes, depth jumps and normal creases only. No line on wall/floor joins or the horizon. Character cards are never outlined by the world ink.
- Character ink: dark plum #201628-#2f1d28, thicker on the bottom/shadow side.
- Colour:
- Day median luma ~.57. Non-ink p5 ~.23 (no crushed blacks). Lit chroma C* p90 ~55. Day sky top ~#5e93d9, horizon 1.28x brighter.
- Golden: peach horizon #ffd08a, violet-blue shadows (never brown), backlit sun.
- Depth:
- DOF on about 1/3 of screen time (CU, MS, inserts), cInf 10-16 px at 1080, focus on the eyes. Establishing and wide shots stay sharp.
- Fog = horizon colour, 25→420 m day, 20→360 m golden.
- Bloom only on HDR emissives: threshold 1.0.
- Camera:
- Hard cuts on big jumps. Everything else is a smootherstep glide of 18-40 f, peak ≤ 25 px/f at 720p.
- Every hold pushes in 0.15-0.35 %/f, with 0.6 %/f on punch words.
- Rolls of 4-5°.
- No hand-held float. Impact shakes flip sign every frame and decay over 7 f.
- Characters:
- About 3.5 head-heights tall, legs 1.4 HH.
- Stick limbs about 0.055 of head width, ink-dot hands.
- Bean head (h/w ~0.93, narrower chin, pointier crown).
- No blush or eye highlights. Faces at brightness ~.93.
- Walk bob 3-7 %, lean 1-7°, planted feet.
- Blinks every 0.5-2.3 s, lasting 4 f.
Look-match loop (how the bridge look was reached; reuse for any "make it look like X" pass)
- Measure the reference first. One analysis agent per topic (motion, depth, textures, characters, lighting, outlines, grade), each writing numbers, not adjectives, to
references/reports/<topic>.md. Shared brief:compare/CONTEXT.md. Reports are the source of truth for every agent after. - Sandboxes, one owner per file. Copy the project folder to
src/videos/<name>_{cam,world,mat,char,post}with entriessrc/sandboxes/<n>/index.tsx(sameindex.tsxas main, only the import path changed). Ownership used for the bridge:- cam: story.ts (camera keys, cuts, kicks, DOF table, foreground props)
- world: world.ts, lights.ts, shade.ts, grade.ts (sun, sky, fog, river, colour, grade)
- mat: paint.ts, build.ts (painted textures, buildings, props)
- char: toon.ts, cast.ts, cardshade.ts (character drawing, posing, card lighting, fx cards)
- post: ink.ts, Bridge.tsx, lensblur.ts (outline pass, composer, lens blur, bloom)
Agents only edit their own files in their own sandbox and render stills with
BRIDGE_ENTRY=src/sandboxes/<n>/index.tsx node scripts/bridge-stills.mjs out/<name>/<n>/x_ <frames> 0.5.
- Merge with
python scripts/bridge_merge.py [cam,world,mat,char,post](backs main up tobackup/bridge_<time>/, copies owned files only). Thennpx tsc --noEmit(filter to the project folder), then re-sync every sandbox from main (cp -f src/videos/<name>/* src/videos/<name>_<n>/) before the next round. - Verify with a fresh Opus max agent: side-by-side sheets (
python scripts/sbs_sheet.py out.jpg --ours a b --ref r1 r2), score each area out of 10 (colour day / golden, lighting, ink, textures, characters, depth, composition) plus a numbered fix list with frame numbers. Map each fix to the file owner and resume that owner's agent with SendMessage (keeps its context). Bridge scores: round 1 5/3/4/5/4/7/4/6 → round 2 5/4/5/6/4/7/6/6 → round 3 see notes. - Contracts between owners live in exported constants (e.g.
NOINKlayer from ink.ts,dofAt/FOREGROUNDfrom story.ts,LIGHTS/LOOKfrom lights.ts). Changing a contract means telling every owner that reads it.
Gotchas
- Kenney nature-kit materials are teal: recolour them by material name in build.ts.
- Cameras end up inside houses: the sight-line culler in build.ts/world.ts removes anything blocking any camera ray.
- Ink in the same merged effect pass as DOF gets overwritten. Ink must be its own pass before the blur.
- Pixel-sized post parameters must scale with resolution: stills are at 0.5, the final at 1.333. R3F clamps dpr to ≥ 1, so
--scale 0.5stills still render a 1080x1920 buffer. - Disk: every Remotion bundle copies
public/(~1.3 GB) intothe temp folder\remotion-webpack-bundle-*and never deletes it. 60+ GB filled the system drive during the bridge passes and a render died with ENOSPC. Always render withexport TEMP='<big drive>/remotion-tmp' TMP='<big drive>/remotion-tmp'(bridge-stills.mjs sets it itself) and ask the user before deleting old bundle folders in the shared the temp folder (auto mode blocks the sweep).<big drive>/remotion-tmp fills too (~500 folders / 110 GB after the 4 bridge rounds): when a project is finished and nothing is rendering, delete itsremotion-webpack-bundle-*andpuppeteer_dev_chrome_profile-*folders there. - In JS strings write
"<big drive>/remotion-tmp", never"<big drive>\remotion-tmp"(\rbecomes a carriage return). - Remotion writes a silent audio track: mux with
-map 0:v:0 -map 1:a:0. - Sub-agents can't write report files in this harness: ask them for a ≤150-word final message and save it yourself to
out/<name>/<n>/REPORT.md. - Scratch
.tsfiles insideout/breaktsc: name them.txt. - 2K renders run ~4 fps (≈10 min for 67 s). Stills at 0.5 take 3-8 s each after a ~40 s bundle.
- Film grain at 2.5 % made the 2K file 910 MB instead of ~250 MB and will turn to mush on YouTube; the reference has none. Keep it off.
Readability traps the verifier caught (check every new prop/shot for these)
- A swing drawn as one rope that disappears behind the kid reads as a HANGING. Always two ropes to a wide plank
with the kid between them (
swingKidin toon.ts), and a frame whose legs clear the arc (A-frame at each end). - Props or flotsam closer than ~2 m to a lens become huge cut-off blobs at the frame edge. When a camera moves, re-check every prop near its new position (the river cameras moved into the floating hats).
- A foreground bush cut by the frame edge reads as a "green ball"; a foreground prop must be recognisable or gone.
- Flags: red + yellow star/diamond reads as Vietnam's. Use a period-correct flag (St George's cross for England 1831).
- Painted signs lit by a side sun go grey-blue and unreadable: give the sign face an unlit material.
- Golden rim light done as an offset outer copy turns every hat into a picture frame: inner rim only, head/torso only.
- Balcony/railing rails at chest height through characters: put the lens ~2.5 m up so rails cross legs, not torsos.
- Flat holds read as freezes in QA (frozen span ≥12 f): every hold needs a creeping push-in.
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.

