agentleFS
Sign inStart free
estruyfestruyf/seshboard/CLAUDE.md

seshboard

CLAUDE.md20 starsChanged 11 days agoMITView on GitHub

AGENTS.md (imported above, so there is no need to read it again) has the architecture, commands, conventions and how to keep a feature's runs short (Working on a feature). The UI rules in .claude/rules/ui.md load by themselves when you work in apps/ui. Open the detail they point to (docs/ui-patterns.md, the subsystem docs) only for the area you change. Before every release, go through docs/releasing.md: the release steps and the docs checklist (docs pages, features.json, website screenshots, npm run website:build). A…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. estruyf/switchboard★ 20100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Before every release, go through docs/releasing.md: the release steps and the docs checklist (docs pages, features.json, website …

    line 14

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

@AGENTS.md

AGENTS.md (imported above, so there is no need to read it again) has the architecture, commands, conventions and how to keep a feature's runs short (Working on a feature). The UI rules in .claude/rules/ui.md load by themselves when you work in apps/ui. Open the detail they point to (docs/ui-patterns.md, the subsystem docs) only for the area you change.

While building a feature

  • Run the related tests (npx vitest run <files>), the typecheck and npm run smoke:demo -- --only "<step label>" after each step. npm run check runs once, at the end. Don't run the full npm run smoke:demo locally, even when a feature's brief asks for it: it runs only on the pull request (check.yml) and at the release. To check whether a failure is already on dev, run that step with --only on a clean checkout.
  • Per feature, the docs need only its CHANGELOG.md line and its entry in website/src/content/features.json (the coverage test in npm run check requires it). Pages and screenshots wait for the release.

Releases

Before every release, go through docs/releasing.md: the release steps and the docs checklist (docs pages, features.json, website screenshots, npm run website:build). A release is not done until the docs are updated.

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