agentleFS
LMikeHLMikeH/whileai-sdk/CLAUDE.md

whileai-sdk

CLAUDE.md21 starsChanged 51 days agoApache-2.0View on GitHub

Read CONSTITUTION.md first: what the library is, what we believe, and where each belief is enforced. Then docs/reference/style.md for the ergonomics standard. One command, run from any checkout, by anyone with write access: It cuts the next number (0.N then 0.N+1, never 1.0) from whatever sits under ## Unreleased in CHANGELOG.md, lands the bump on main, and starts publish.yml. Runs queue on a concurrency group, so two agents shipping in the same minute get two releases in order, or one…

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read CONSTITUTION.md first: what the library is, what we believe, and where each belief is enforced.

    line 3
  2. Very specific:

    Never bump version by hand.

    line 23
  3. Very specific:

    Every change ships with an entry under ## Unreleased.

    line 25
  4. Distinctive:

    Add files by path. Never git add -A.

    line 49

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

Working in whileai-sdk

Read CONSTITUTION.md first: what the library is, what we believe, and where each belief is enforced. Then docs/reference/style.md for the ergonomics standard.

Shipping a release

One command, run from any checkout, by anyone with write access:

gh workflow run release.yml

It cuts the next number (0.N then 0.N+1, never 1.0) from whatever sits under ## Unreleased in CHANGELOG.md, lands the bump on main, and starts publish.yml. Runs queue on a concurrency group, so two agents shipping in the same minute get two releases in order, or one release and one "nothing to ship". Watch it with gh run watch and confirm with pip index versions whileai.

Rules the tooling enforces (CI fails otherwise):

  • Never bump version by hand. A PR that bumps it may touch only CHANGELOG.md, both pyprojects and uv.lock.
  • Every change ships with an entry under ## Unreleased. Keep that header; the cut renames it and puts a fresh one above.
  • To see what a cut would ship without doing it: uv run python .github/scripts/release.py --dry-run

Coding standard

.claude/agents/ holds the three agents that apply the constitution on demand (style-guide, docs-designer, user-sim). docs/reference/style.md is the standard: PyTorch/DSPy ergonomics. One import (import whileai as wai), one command (wai login, never the package name followed by a verb; scripts/check_cli_name.py fails CI on the long spelling), objects carry configuration and calls carry data, at most eight parameters on a public call, reports print themselves (no format_* twins), verbs a scientist says. New public names go one dot down or become methods on the rows object. tests/api/test_style_ratchet.py pins today's counts of the retired shapes; lower a pin when you retire a name, never raise one.

Pull requests

  • gh pr create fails on this repo ("must be a collaborator"); open PRs through the API: gh api -X POST repos/whilehq/whileai-sdk/pulls -f title=.. -f head=<branch> -f base=main -F body=@body.md
  • A PR that touches whileai/ must touch docs/ too, or carry the no-docs label.
  • Add files by path. Never git add -A; other sessions share this checkout.

Checks

uv run pytest -q
uv run ruff check . && uv run ruff format --check .
uv run mypy            # the gate
uv run ty check        # same, under a second; mypy stays the gate until ty is 1.0
uv run python scripts/check_no_hardcoding.py

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.