agentleFS
kinlacekinlace/parent-recap/CLAUDE.md

parent-recap

CLAUDE.md8 starsChanged 44 days agoMITView on GitHub

Issues live in GitHub Issues for kinlace/parent-recap, managed via the gh CLI. See docs/agents/issue-tracker.md. Default five-role vocabulary (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md. Single-context: one CONTEXT.md and docs/adr/ at the repo root. See docs/agents/domain.md. Before publishing a spec or tickets, record in docs/adr/ (via /domain-modeling) every decision in them that clears that skill's ADR bar and has no ADR yet. main is protected: every change lands through a PR from its own branch, rebase-merged once the test and gitleaks…

The file

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

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

  • 2

    Very specific

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

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

    Default five-role vocabulary (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix).

    line 9
  2. Very specific:

    Before publishing a spec or tickets, record in docs/adr/ (via /domain-modeling) every decision in them that clears that skill's ADR bar and …

    line 15

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

Issue tracker

Issues live in GitHub Issues for kinlace/parent-recap, managed via the gh CLI. See docs/agents/issue-tracker.md.

Triage labels

Default five-role vocabulary (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md.

Domain docs

Single-context: one CONTEXT.md and docs/adr/ at the repo root. See docs/agents/domain.md.

Before publishing a spec or tickets, record in docs/adr/ (via /domain-modeling) every decision in them that clears that skill's ADR bar and has no ADR yet.

Landing changes

main is protected: every change lands through a PR from its own branch, rebase-merged once the test and gitleaks checks pass. Merging before CI (--admin) is for an urgent hotfix only, and only when Xi asks for it ("Urgent hotfix" in CONTRIBUTING.md). The PR body starts with What changes for families: and closes its issue (Closes #N). See CONTRIBUTING.md.

Gateway admin requests

A request to act on the hosted server (a Gateway Key, an invite, a family's status, a deploy) is answered with the exact sudo admin … command from the "What you want" table at the top of "Runbook" in ops/gateway/README.md. Xi runs it after ssh oci-a1-admin, which works only from Xi's own devices (hyprland, thinkpad), and pastes the output back when it needs reading. With each command, say whether its output can be pasted back as it is, per "What can be pasted" under that table: if not, say to read it on the server, or to take the addresses and key out first. The Mac mini is a tagged Tailscale node whose mini login on oci-a1 reads logs and systemctl status only.

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.