atet / src
AGENTS.md7 starsChanged 47 days agoMITView on GitHub
1 other project uses a version of this.
Other versions1 project uses a version of this.
Word for word · 1
- hraness/slopcamera★ 7100% same
Edited · 0
None found.
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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- .agents/skills/cinematic-pack-authoring/AGENTS.mdAGENTS.md
- .agents/skills/percolate-kb/AGENTS.mdAGENTS.md
- .agents/skills/phase-final-reviewer/AGENTS.mdAGENTS.md
- .agents/skills/phase-implementer/AGENTS.mdAGENTS.md
- .agents/skills/phase-orchestrator/AGENTS.mdAGENTS.md
- .agents/skills/phase-reviewer/AGENTS.mdAGENTS.md
- .agents/skills/plan-kb/AGENTS.mdAGENTS.md
- .agents/skills/query-kb/AGENTS.mdAGENTS.md
- .agents/skills/refresh-kb/AGENTS.mdAGENTS.md
- .agents/skills/save-pdf-kb/AGENTS.mdAGENTS.md
- .agents/skills/save-url-kb/AGENTS.mdAGENTS.md
- .agents/skills/write-phase-plan/AGENTS.mdAGENTS.md
- kb/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cinematic-pack-authoringSkill
- percolate-kbSkill
- phase-final-reviewerSkill
- phase-implementerSkill
- phase-orchestratorSkill
- phase-reviewerSkill
- plan-kbSkill
- query-kbSkill
- refresh-kbSkill
- save-pdf-kbSkill
- save-url-kbSkill
- write-phase-planSkill
- slopcameraSkill
The file
We split this AGENTS.md into the rules it gives an agent
8 rules. About 2 are common, 3 are distinctive, and 3 are very specific to this project.
≈2
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Keep canonical implementation in this source root and expose new behavior only through slopcamera commands, slopcamera.* operations, the …
- Distinctive: line 14
Keep the declarative SDK and portable core canonical.
- Distinctive: line 15
Treat explicitly imported workflow modules as trusted current-user Bun code.
- Common: line 16
Keep portable source independent of repository-only packages and state, caller-selected executable code, arbitrary network URLs, and …
- Very specific: line 17
Keep the ./workflow compatibility surface dependency-free.
- Distinctive: line 19
Treat diagram and authored composition inputs as authoritative.
- Very specific: line 20
Keep local vectorization authentication-free and network-silent.
- Common: line 21
Keep this source root free of hosted-service concerns: no HTTP routes, product account, OAuth flow, credential persistence, or legacy …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Contents
- Canonical root modules – Slopcamera CLI, imperative workflow, diagram, canvas, artifact, direct Gateway generation, operation, MCP, and desktop-integration contracts.
icon.ts– the two-class product-identity pipeline:mark(bold compact favicon/app/header symbol) andillustration(bounded isometric marketing artwork) prompts, local ink extraction, VTracer trace, deterministic geometry gates, and purpose-specific vision-model critique rounds.icon-scene.ts,soundtrack.ts,bounded-file.ts– theslopcamera.icon.*andslopcamera.soundtrack.*operations over the exact-version@hraness/iconplaceand@hraness/soundfishlibraries, with bounded reads and atomic replaceable writes.code/– canonical portable declarative graph authoring, closed public capability projection, compiler, plan, and execution contracts.vectorize/– bounded local raster decoding, VTracer supervision, SVG sanitization, measurement, provenance, and worker isolation.*.test.tsand*.property.test.ts– deterministic examples, parser laws, and standalone consumer evidence.
Guidelines
- Keep canonical implementation in this source root and expose new behavior only through
slopcameracommands,slopcamera.*operations, the additive./codegraph SDK, and the compatible./workflowSDK. - Preserve the root module and
./workflowv0.8 imperative APIs. Keep declarative authoring in./code, lower-level compiler contracts in./code/advanced, and testing or built-in workflow helpers outside the public export map. - Keep the declarative SDK and portable core canonical. The complete local host consumes that graph model and owns durable media execution. The Desktop shell supplies only native capture, permissions, and UI.
- Treat explicitly imported workflow modules as trusted current-user Bun code. Compile each graph against one closed host projection and reject unsupported capabilities before executor or resource admission. Never add an open operation-registration hook.
- Keep portable source independent of repository-only packages and state, caller-selected executable code, arbitrary network URLs, and ambient credentials.
- Keep the
./workflowcompatibility surface dependency-free. It may compose only the typed public operation registry, must parse foreign input, bound step dispatch, drain dispatched operations before returning, retain completed-step receipts on failure, and must not dynamically import authored code. - Parse every foreign value from
unknown; bound source bytes, collections, dimensions, subprocess work, responses, and outputs before expensive or privileged work begins. - Treat diagram and authored composition inputs as authoritative; make rendered SVG, PNG, tldraw, and vector derivatives reproducible and replaceable.
- Keep local vectorization authentication-free and network-silent. Send generation directly to the fixed Vercel AI Gateway origin using environment-only credentials, bounded responses, and
maxRetries: 0. - Keep this source root free of hosted-service concerns: no HTTP routes, product account, OAuth flow, credential persistence, or legacy Graphics runtime surface. The hosted adapter under
apps/api/consumes these modules through the MCP runtime and owns all transport, billing, and storage state. - Pair parsing and compatibility changes with examples and property laws, then run the package
checkgate and clean standalone export.
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.

