agentleFS
Sign inStart free
GRU953GRU953/MTA_Plugin/CLAUDE.md

MTA_Plugin

CLAUDE.md1 starsChanged 5 months agoMITView on GitHub

This repo is under a multi-session hardening/extension program. Cross-session state lives in program/ on the develop branch — that is the single source of truth, not model memory. Any fresh session resumes from it with zero prior context.

  • In this repositoryOne other file it gives its agents.

The file

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

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

  • 3

    Very specific

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

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

    Read program/PROGRESS.md — the ▶ RESUME HERE pointer + the WP table — and the last 1–2 entries of program/SESSION_LOG.md.

    line 9
  2. Very specific:

    Do the next unblocked WP on a wp-<id>-<slug> branch → PR into develop with green CI.

    line 13
  3. Very specific:

    Wrap up: leave the repo green + resumable.

    line 16

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

CLAUDE.md — Memorised them All

This repo is under a multi-session hardening/extension program. Cross-session state lives in program/ on the develop branch — that is the single source of truth, not model memory. Any fresh session resumes from it with zero prior context.

Resume protocol (every session)

  1. git checkout develop && git pull.
  2. Read program/PROGRESS.md — the ▶ RESUME HERE pointer + the WP table — and the last 1–2 entries of program/SESSION_LOG.md. Skim DECISIONS.md / RISKS.md / ACCEPTANCE.md as needed. Load only the code the next Work Package touches — do not re-read the whole tree.
  3. Do the next unblocked WP on a wp-<id>-<slug> branch → PR into develop with green CI. Never push main directly; release from main via a vX.Y.Z tag (the tag-triggered train publishes all channels — see program/PUBLISH_MANIFEST.md).
  4. Wrap up: leave the repo green + resumable; update PROGRESS.md (statuses + ▶ RESUME HERE) and append a SESSION_LOG.md entry ending with the single exact next step.

Status

v2.6.1 SHIPPED — PyPI + GitHub Release + .mcpb + Homebrew tap + GHCR (OIDC trusted-publish, SBOM, cosign single-file *.sigstore.json bundle). Ships v2.5.0 cross-AI mta setup (Claude/Gemini/Cursor/VS Code/Windsurf/Codex; Grok auto-discover) + v2.6.0 recall/resolve perf + supply-chain. v2.6.1 = the v2.6.0 package with two release-pipeline fixes (SBOM attach + cosign pin). S25 docs reframe SHIPPED (no version bump): README + all 7 metadata surfaces reframed Claude-only → cross-AI; live on GitHub / Claude-marketplace / Glama (PR #80→main, #81→develop). Next = v2.x+ backlog (optional): a docs-only v2.6.2 to refresh PyPI's page with the new cross-AI description; remote-MCP recipe polish; the deferred Low items in program/RISKS.md (R-16/R-17, accepted).

Invariants (must never regress)

Token-free (tiny tool results; document contents never returned to the model) · 100% local / no telemetry · dependency-free classical/offline fallback (a digest succeeds with no models and no network) · atomic, crash-safe writes. CI must stay green on the Ubuntu/macOS/Windows × 3.10/3.12 matrix.

Env notes

gh is authed as owner GRU-953. Docker isn't installed locally (the Phase-6 container matrix runs in CI / .github/workflows/e2e.yml). Tests: pytest tests/ (the conversion-e2e + e2e lanes need the full deps / a wheel install). Single version source = mta/__init__.py; scripts/check_versions.py gates drift.

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