agentleFS
mit-networkmit-network/everything-claude-code/.cursor/rules/common-hooks.md

everything-claude-code / rules

Cursor rule76 starsChanged 7 months agoMITView on GitHub

Hooks system: types, auto-accept permissions, TodoWrite best practices

We split this common-hooks.md into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    PreToolUse: Before tool execution (validation, parameter modification)

    line 9
  2. Distinctive:

    PostToolUse: After tool execution (auto-format, checks)

    line 10
  3. Distinctive:

    Stop: When session ends (final verification)

    line 11
  4. Distinctive:

    Never use dangerously-skip-permissions flag

    line 18
  5. Distinctive:

    Use TodoWrite tool to:

    line 23
  6. Distinctive:

    Verify understanding of instructions

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
common-hooks.md

Hooks System

Hook Types

  • PreToolUse: Before tool execution (validation, parameter modification)
  • PostToolUse: After tool execution (auto-format, checks)
  • Stop: When session ends (final verification)

Auto-Accept Permissions

Use with caution:

  • Enable for trusted, well-defined plans
  • Disable for exploratory work
  • Never use dangerously-skip-permissions flag
  • Configure allowedTools in ~/.claude.json instead

TodoWrite Best Practices

Use TodoWrite tool to:

  • Track progress on multi-step tasks
  • Verify understanding of instructions
  • Enable real-time steering
  • Show granular implementation steps

Todo list reveals:

  • Out of order steps
  • Missing items
  • Extra unnecessary items
  • Wrong granularity
  • Misinterpreted requirements

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.