vibe-replay / rules
Cursor rule39 starsChanged 3 months agoMITView on GitHub
Where vibe-replay's project instructions live
The file
Files
--- description: Where vibe-replay's project instructions live alwaysApply: true --- Project conventions, commands, gotchas, and release rules for this repo live in `AGENTS.md` at the repository root. Read it before making changes. Current Cursor versions load root and nested `AGENTS.md` natively, so this rule is only a pointer for older versions — it deliberately carries no project knowledge of its own. Do not copy rules from `AGENTS.md` into this file; keep `AGENTS.md` the single source of truth. `CLAUDE.md` is a shim that imports `AGENTS.md` for Claude Code. Never record project knowledge there.
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.