agentleFS
Sign inStart free
docxologydocxology/codomyrmex/.jules/AGENTS.md

codomyrmex

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Configuration for the Jules agent runtime: one Markdown file per scheduled Jules persona (Bolt, Palette, Sentinel). Each file pairs the persona's mandatory session rules with a dated record of learnings, merged-PR dispositions, and retired topics that later sessions must read before proposing a change. - bolt.md — Bolt performance journal: dated learnings (sync/async wrappers, hoisted type maps, O(1) cache eviction), the mandatory dedupe-before-optimizing session rules, and the retired-topic list with the PR numbers that already landed each optimization. - palette.md…

The file

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

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Read by the external Jules runtime at session start.

    line 26
  2. Very specific:

    Add journal entries under a dated ## YYYY-MM-DD - Title heading and keep earlier entries: the retired-topic and disposition lists are what …

    line 40
  3. Distinctive:

    When a persona's fix merges, record it (with its PR number) in that file's retired-topic or disposition list.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

AGENTS.md — codomyrmex/.jules

Purpose

Configuration for the Jules agent runtime: one Markdown file per scheduled Jules persona (Bolt, Palette, Sentinel). Each file pairs the persona's mandatory session rules with a dated record of learnings, merged-PR dispositions, and retired topics that later sessions must read before proposing a change.

Key Files

  • bolt.md — Bolt performance journal: dated learnings (sync/async wrappers, hoisted type maps, O(1) cache eviction), the mandatory dedupe-before-optimizing session rules, and the retired-topic list with the PR numbers that already landed each optimization.
  • palette.md — Palette UI/UX and accessibility spec: owned surfaces (src/codomyrmex/pai_pm/server/spa/, src/codomyrmex/pai_pm/server/routes/), session rules, surface notes, and the disposition of earlier a11y PR floods.
  • sentinel.md — Sentinel security journal: dated vulnerability learnings, session rules, and dispositions for intentional shell executors and already-fixed injection paths that must not be re-proposed.
  • README.md — human signpost for the three persona files.

Dependencies

  • Read by the external Jules runtime at session start; no code under src/ imports these files. The in-repo Jules client lives in src/codomyrmex/agents/jules/.
  • scripts/maintenance/close_duplicate_prs.py treats every .jules/ path as a journal note (JOURNAL_PREFIXES), so a PR that only touches these files never represents a duplicate-PR family.
  • .github/workflows/jules-dispatch.yml dispatches Jules tasks from its own prompt templates and does not read these files.
  • Parent: ../README.md · Root contract: ../AGENTS.md

Development Guidelines

  • These files are instructions for an external agent runtime; treat edits as behavior changes and review them like code.
  • Add journal entries under a dated ## YYYY-MM-DD - Title heading and keep earlier entries: the retired-topic and disposition lists are what stop sessions from re-proposing merged work.
  • When a persona's fix merges, record it (with its PR number) in that file's retired-topic or disposition list.
  • The persona rules reject journal-only .jules/ diffs; a persona PR needs a real code change with file:line evidence from main.

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