Tools
Context File Generator
Tell an AI tool how your project works, so it stops guessing.
1. Answer, one at a time
Nine short questions. Stuck? Tap “Show me an example first”.
2. Reveal your files
Your files appear, one tab per file, with its save path.
3. Drop them in your repo
AGENTS.md goes in the repo root. The rest point at it.
Free, in your browser, no signup. The full why is in the context files guide.
Which tools do you use?
Tick the tools you use. AGENTS.md is the safe default.
Questions, answered
AGENTS.md vs CLAUDE.md: which file should I use?
Use AGENTS.md as the canonical file. It is the cross-tool standard that Cursor, Codex, opencode, and about sixty other tools read natively. CLAUDE.md should then be a one-line import of AGENTS.md plus Claude-only extras, not a second copy of the same rules. Two copies drift apart, and drifted instructions are worse than missing ones, because each agent then follows a different version of your conventions.
What file does Cursor read?
Cursor reads AGENTS.md at the repo root, and it also reads .cursor/rules/*.mdc files. Each .mdc file carries frontmatter with a description, a globs pattern, and an alwaysApply flag. This generator splits Cursor rules by concern, commands, conventions, and gotchas, so each file stays short and its scope is explicit.
What is the GitHub Copilot instructions file?
Copilot reads .github/muse-instructions.md for repo-wide instructions, and .github/instructions/*.instructions.md files for path-scoped instructions, declared with an applyTo pattern. This generator writes the repo-wide file from your answers and a test-scoped file for test paths.
Built by NotVibesCoded. Use AI. Just don't ship slop.