agentleFS
Sign inStart free
Catalyst-Forge-LLCCatalyst-Forge-LLC/temper-pass/CLAUDE.md

temper-pass

CLAUDE.md0 starsChanged 47 days agoMITView on GitHub

This repo uses ForgeTrail lifecycle tracking. Source of truth: .forgetrail/workflow_tracking.json (currentPhase, phases, decisions). Do not advance currentPhase or mark a phase complete without explicit user confirmation. If exit criteria look satisfied, say so and wait.

The file

We split this CLAUDE.md into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .forgetrail/workflow_tracking.json and CONTEXT_PROMPT.md (once it exists) before making changes.

    line 7
  2. Very specific:

    Check currentPhase and work within that phase's scope.

    line 8
  3. Very specific:

    Commit after substantive work per .cursor/rules/git-user-commits.mdc.

    line 13
  4. Very specific:

    Do not advance currentPhase or mark a phase complete without explicit user confirmation.

    line 17

≈ “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

Agent guardrails — TemperPass

This repo uses ForgeTrail lifecycle tracking. Source of truth: .forgetrail/workflow_tracking.json (currentPhase, phases, decisions).

Session start

  1. Read .forgetrail/workflow_tracking.json and CONTEXT_PROMPT.md (once it exists) before making changes.
  2. Check currentPhase and work within that phase's scope; don't jump ahead without user confirmation.

Git commits

  • Plain git commit -m "..." or git commit -F <file>.
  • Commit after substantive work per .cursor/rules/git-user-commits.mdc. Do not push unless the user explicitly asks.

Phase transitions

Do not advance currentPhase or mark a phase complete without explicit user confirmation. If exit criteria look satisfied, say so and wait.

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