agentleFS
nuncaeslupusnuncaeslupus/literary-critic/CLAUDE.md

literary-critic

CLAUDE.md0 starsChanged 27 days agoMITView on GitHub

Were you spawned by another session, with a task already assigned? Then skip straight to that task. Steps 2-5 below need the GitHub API, and a spawned session has no mcp__* tools — implement, run the gate, and let claude-arsenal/bin/open_task_pr.sh push. It prints branch:<name> when it cannot open the PR here; return that line and stop. Never claim or release. Otherwise, every session, without waiting to be asked: 1. Read arsenal/session/handover.md for the previous session's context. 2. List the repository's…

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 arsenal/session/handover.md for the previous session's context.

    line 12
  2. Very specific:

    Run python3 claude-arsenal/scripts/query_status.py --issues <that file> for the board, and report anything it flags.

    line 18
  3. Very specific:

    Every change goes through a PR, ad hoc requests included — never push to the default branch.

    line 25
  4. Very specific:

    After any session with tasks: update arsenal/session/handover.md.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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-arsenal: auto-managed -->

Automatic session protocol

Were you spawned by another session, with a task already assigned? Then skip straight to that task. Steps 2-5 below need the GitHub API, and a spawned session has no mcp__* tools — implement, run the gate, and let claude-arsenal/bin/open_task_pr.sh push. It prints branch:<name> when it cannot open the PR here; return that line and stop. Never claim or release.

Otherwise, every session, without waiting to be asked:

  1. Read arsenal/session/handover.md for the previous session's context.
  2. List the repository's issues labelled arsenal:task — open and closed — and save the JSON. Use whatever GitHub access this surface has; run claude-arsenal/bin/github_channel.sh --detect to find out which. Request number, title, state, labels, assignees and not body — the bodies are the bulk of that fetch and nothing downstream reads them.
  3. Run python3 claude-arsenal/scripts/query_status.py --issues <that file> for the board, and report anything it flags.
  4. Pick up work: python3 claude-arsenal/scripts/task_select.py --issues <that file> returns the next unblocked task, then bash claude-arsenal/bin/claim_task.sh <id> takes it (see @claude-arsenal/AGENTS.md).
    • Nothing returned + workspace plans exist → seed tasks from each plan.
    • Nothing at all → ask what to work on.
  5. Every change goes through a PR, ad hoc requests included — never push to the default branch. A task's PR carries Closes #<issue> so merging it closes the task by itself. Dispatching the work to another session instead? Pass the repository explicitly and pass ARSENAL_TASK_ISSUE — a spawned worker can resolve neither. → claude-arsenal/references/orchestrator-tick.md
  6. After any session with tasks: update arsenal/session/handover.md.

Specs and plans live at status/specification.md and status/plan.md (a workspace's at arsenal/project/<ws>/spec.md / plan.md). A brainstorming or planning skill from another plugin writes its output there too, not to its own default location.

@claude-arsenal/AGENTS.md

<!-- /claude-arsenal: auto-managed -->

Project rules

@AGENTS.md

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.