declarative-infra
Skill2 starsChanged 10 days agoMITView on GitHub
Use when changing NixOS, OpenTofu, cloud resources, infrastructure secrets, deployments, or provider credentials, even when another repository owns them. Routes changes through the owning repository and trusted deployment path.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- davidvornholt/mail-mcpword for word, first seen Nov 5, 2026
Other versions1 project uses a version of this.
Word for word · 1
- davidvornholt/mail-mcp★ 2100% 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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ci-pipelinesSkill
- databaseSkill
- frontend-designSkill
- issuesSkill
- nextjsSkill
- prsSkill
- review-fixSkill
- reviewSkill
- screenshots-in-prsSkill
- secrets-and-configSkill
- standards-syncSkill
- ux-uiSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 16
Keep OpenTofu moved and import blocks in the repository after they apply, as the record of what happened.
- Very specific: line 22
Before pushing, run nix flake check, build each host's toplevel, run tofu fmt -check, and run tofu init -backend=false && tofu validate.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Declarative infrastructure
Ownership and mutation
Each host's infrastructure has exactly one home: the infra/ directory of the repository it serves, or a dedicated infrastructure repository. Everything for that host changes in that home, even when the work starts in another repository.
Live state changes only through the home's reviewed main-branch automation, so production always matches a reviewed commit. Running deploy-rs, tofu apply, or nixos-rebuild switch by hand is an emergency measure. If you do it, say so in your report.
Changing existing infrastructure
Keep OpenTofu moved and import blocks in the repository after they apply, as the record of what happened. A migration or refactor is ready to merge only when its plan is a no-op.
Data-bearing resources carry prevent_destroy, so deleting one takes two changes: the first lifts the guard, the second destroys the resource.
Validation
Before pushing, run nix flake check, build each host's toplevel, run tofu fmt -check, and run tofu init -backend=false && tofu validate. Where credentials are available, also produce a plan.
References
| Change | Reference |
| A new infrastructure home, host layout, PostgreSQL, Nix caching, private registry access, or host deployment | Bootstrapping a host repo |
| SOPS identities and recipients, CI secrets, or brokered provider credentials | Secrets bootstrap |
| Preview environments | Pull request previews |
| Releasing, rolling back, or hosting a first-party app's container images | App releases |
| Third-party container updates whose publisher the infrastructure owner doesn't control | Vendor image updates |
Web hosts get pull request previews by default. Leaving them out takes a decision recorded in the host repository.
Development environment layers and where each value is documented belong to the secrets-and-config skill.
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.