tuo-leituo-lei/vibe-replay/CLAUDE.md

vibe-replay

CLAUDE.md39 starsChanged 3 months agoMITView on GitHub

Add something here only if it is genuinely Claude-Code-specific — a plan-mode rule, a subagent hint, a reference to .claude/ tooling. Anything a different agent would also need goes in AGENTS.md. packages/cli/test/agent-instructions.test.ts fails if the import above is removed or if this file grows past a small size budget. --> - Editing a file triggers the PostToolUse hook in .claude/settings.json, which runs oxlint --fix and oxfmt on that file. Do not also run pnpm lint on a file you just…

In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/project-instructions.mdcCursor rule
- replaySkill

The file

We split this CLAUDE.md 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:
Add something here only if it is genuinely Claude-Code-specific — a plan-mode rule, a subagent hint, a reference to .claude/ tooling.
line 8
Very specific:
Add new skills under skills/<name>, then create discovery symlinks under .agents/skills/ and .claude/skills/ as described in Agent setup in …
line 21

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

CLAUDE.md

@AGENTS.md

<!--
  Shim, not a source of truth. Claude Code reads CLAUDE.md and does not read
  AGENTS.md, so this file imports it. Project knowledge belongs in AGENTS.md so
  that Codex, Cursor, Pi, and opencode see it too.

  Add something here only if it is genuinely Claude-Code-specific — a plan-mode
  rule, a subagent hint, a reference to .claude/ tooling. Anything a different
  agent would also need goes in AGENTS.md.

  packages/cli/test/agent-instructions.test.ts fails if the import above is
  removed or if this file grows past a small size budget.
-->

Claude Code

Editing a file triggers the PostToolUse hook in .claude/settings.json, which runs oxlint --fix and oxfmt on that file. Do not also run pnpm lint on a file you just edited — it is already formatted.
Add new skills under skills/<name>, then create discovery symlinks under .agents/skills/ and .claude/skills/ as described in Agent setup in AGENTS.md. Do not create the canonical skill in either discovery directory.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free