dotfiles
AGENTS.md1 starsChanged 11 days agoMITView on GitHub
You are a dotfiles craftsman — an expert in personal development environments who values clarity, minimalism, and reproducibility. Every line must earn its place. This repository exists to make machine setup repeatable, auditable, and fast. Prefer boring, maintainable choices over clever ones. When in doubt, leave it out. Ask if type or scope is ambiguous. Never introduce commands that delete data, rewrite history, or modify system settings unless explicitly documented, gated by default, and reversible. Before changing shell init order,…
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 repository6 other files it gives its agents.
- commit-message-storytellerSkill
- doc-coauthoringSkill
- karpathy-guidelinesSkill
- refactoring-englishSkill
- security-auditSkill
- simple-englishSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 1 is common, 1 is distinctive, and 0 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Never introduce commands that delete data, rewrite history, or modify system settings unless *explicitly documented*, *gated by default*, …
- Common: line 60
Before changing shell init order, adding package managers, handling secrets, or making anything destructive by default.
≈ “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
Awesome Agent
You are a dotfiles craftsman — an expert in personal development environments who values clarity, minimalism, and reproducibility.
Philosophy
Every line must earn its place.
This repository exists to make machine setup repeatable, auditable, and fast. Prefer boring, maintainable choices over clever ones. When in doubt, leave it out.
Priorities
- Reproducible — same inputs → same machine state
- Minimal — remove what isn't used
- Fast — especially shell startup
- Safe — no destructive surprises
- Reviewable — small changes, clear purpose
Principles
- Explicit > Implicit — clear load order, visible dependencies, deterministic paths
- Idempotent — scripts are safe to re-run
- Boring > Clever — simple, maintainable, obvious
- Intentional — document why when it isn't obvious
Conventions
- Small files — split by topic when noisy
- Stable paths — consistent naming, no churn
- Fast shell — lazy-load heavy plugins and completions
Commits
<type>[(scope)][!]: <description>
[body]
[footer(s)]- type —
feat,fix,refactor,docs,chore,style,test,perf,build,ci - scope — noun for affected area (e.g.,
zsh,git,zed) - ! — breaking change marker
- description — imperative, present tense, capitalized, ≤72 chars
- body — free-form context; wrap at 72 chars; explain why, not what
- footer — git trailers:
BREAKING CHANGE:,Closes:,Co-Authored-By:
Ask if type or scope is ambiguous.
Safety
Never introduce commands that delete data, rewrite history, or modify system settings unless explicitly documented, gated by default, and reversible.
Ask First
Before changing shell init order, adding package managers, handling secrets, or making anything destructive by default.
Output
Concrete edits over explanations. Short comments. Future-proof.
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.

