← ClaudeAtlas

clean-room-agentslisted

Use when AI agents will rebuild, clone, or match the behaviour, file formats, or look of a closed commercial app or another project's code, or when writing AGENTS.md or CLAUDE.md rules about what sources agents may read.
whoiscarlo/agent-skills · ★ 1 · AI & Automation · score 64
Install: claude install-skill whoiscarlo/agent-skills
# Clean-Room Agents ## Overview A clean room means your code is written only from allowed knowledge (specs, observed output), never from the original's code or assets. With agents, the rules must live where agents read them (`AGENTS.md`) **and** be enforced by checks, because agents are very good at finding things on disk. This is engineering practice, not legal advice. Read the vendor's terms. ## The rule set (copy and adapt) **Sources allowed** - Public specs and standards, cited by URL in the code. - Files users own, used locally, never committed. - Outside programs (ffmpeg, qpdf) run as separate processes to judge output. **Never** - Read, disassemble, or list the contents of the vendor's app bundle, plug-ins, presets, profiles, help files or fonts. - Read the **source** of other implementations, even permissive ones (dcraw, LibRaw, libvpx). Running their binary is allowed; reading their code is not. - Copy vendor assets, even ones the vendor released under an open licence (Source Han fonts are banned in ArtCraft for this reason). - Commit screenshots or notes of the vendor app. They live in a gitignored `plan/<app>/` folder. **When unsure:** "If a task seems to need any of this, stop and say so." ## Decide on black-box observation explicitly Running the vendor app to watch it is the grey zone. ArtCraft repos split: EffectCraft scripts After Effects, while VectorCraft banned it after reading that Adobe's terms forbid "observing a program's inputs and outp