Generators
Produce configuration and instruction files from structured input.
When you would reach for these
Coding agents read a project instruction file before they touch anything — AGENTS.md, CLAUDE.md, or whatever the tool of the week expects. The file is doing real work: it is the difference between an agent that follows your conventions and one that invents its own and leaves you to review the results.
The Instruction File Generator turns answers about your project into that file. It is faster than writing one from scratch, and more importantly it prompts you for the things people forget: which package manager the project actually uses, which commands verify a change, which directories are off limits, and what the definition of done is.
What belongs in an instruction file
The useful content is whatever an agent cannot infer by reading the code. Build and test commands, the branching convention, the one way the project does something it could do three ways, and the rules that are not visible in any single file. A good instruction file is mostly constraints.
What does not belong is a description of the codebase structure, which an agent can read for itself and which goes stale the first time a directory moves. Nor does anything secret: an instruction file is committed, and it is read by every tool and contributor who opens the repository. Keep credentials, internal URLs and customer names out of it.
Treat the generated file as a first draft. It captures what you told it, and every project has a rule its author only remembers on being asked.