agentleFS
codervisorcodervisor/lean-spec/CLAUDE.md

lean-spec

CLAUDE.md296 starsChanged 6 months agoMITView on GitHub

This file defines shared conventions enforced across all codervisor repositories. It is synced from the codervisor meta-repo into each child project. codervisor is a suite of AI-agent infrastructure projects: Types: feat, fix, refactor, test, docs, chore, ci, perf. Examples: feat/session-pool, fix/auth-timeout, chore/update-deps.

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. codervisor/leanspec★ 294100% 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 repository8 other files it gives its agents.

The file

Show its rules and text

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

13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Write clear, self-documenting code.

    line 23
  2. Distinctive:

    Prefer small, focused commits with descriptive messages (imperative mood, <72 chars).

    line 24
  3. Distinctive:

    Every PR must pass CI before merge.

    line 25
  4. Distinctive:

    Keep dependencies minimal.

    line 26
  5. Very specific:

    Use thiserror for library errors, anyhow for binary/application errors.

    line 33
  6. Very specific:

    Prefer #[must_use] on functions returning values that should not be silently dropped.

    line 34
  7. Very specific:

    Use named exports. Avoid default exports except for framework conventions.

    line 42
  8. Very specific:

    Prefer async/await over raw Promises.

    line 43
  9. Distinctive:

    Follow Mathlib conventions for naming and style.

    line 48
  10. Distinctive:

    Keep proofs tactic-mode where possible for readability.

    line 49
  11. Distinctive:

    Keep PRs small and focused.

    line 73
  12. Distinctive:

    Never commit secrets, tokens, or credentials.

    line 78
  13. Distinctive:

    Follow OWASP top-10 awareness for any web-facing code.

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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 — codervisor project standards

This file defines shared conventions enforced across all codervisor repositories. It is synced from the codervisor meta-repo into each child project.

Repository overview

codervisor is a suite of AI-agent infrastructure projects:

RepoStackPurpose
stiglabRust + TypeScriptDistributed AI agent session orchestration
synodicTypeScriptAI harness governance framework
telegramableTypeScriptTelegram-first AI agent proxy
isingRustCode graph analysis engine
skillsTOML / MarkdownShared Claude Code skills
lean-specLean 4Formal specification framework

Coding conventions

General

  • Write clear, self-documenting code. Add comments only where intent is non-obvious.
  • Prefer small, focused commits with descriptive messages (imperative mood, <72 chars).
  • Every PR must pass CI before merge. No force-pushing to main.
  • Keep dependencies minimal. Justify new crates / packages in the PR description.

Rust repos (stiglab, ising)

  • Edition: 2021 or later.
  • Format with rustfmt (default config unless rustfmt.toml is present).
  • Lint with clippy — treat warnings as errors in CI (-D warnings).
  • Use thiserror for library errors, anyhow for binary/application errors.
  • Prefer #[must_use] on functions returning values that should not be silently dropped.
  • Tests live next to the code in #[cfg(test)] modules; integration tests in tests/.

TypeScript repos (synodic, telegramable)

  • Target: ES2022+ / Node 20+.
  • Strict mode: "strict": true in tsconfig.json.
  • Lint with Biome (preferred) or ESLint. Format with Biome or Prettier.
  • Use named exports. Avoid default exports except for framework conventions.
  • Prefer async/await over raw Promises. Avoid .then() chains.
  • Tests use Vitest (preferred) or Jest. Co-locate test files as *.test.ts.

Lean repos (lean-spec)

  • Follow Mathlib conventions for naming and style.
  • Keep proofs tactic-mode where possible for readability.

Commit messages

<type>: <short summary in imperative mood>

Optional body explaining *why*, not *what*.

Types: feat, fix, refactor, test, docs, chore, ci, perf.

Branch naming

<type>/<short-description>

Examples: feat/session-pool, fix/auth-timeout, chore/update-deps.

PR standards

  • Title follows commit message format.
  • Description includes a Summary (what and why) and Test plan (how it was verified).
  • Keep PRs small and focused. Split large changes into stacked PRs.
  • Request review from at least one team member.

Security

  • Never commit secrets, tokens, or credentials. Use environment variables.
  • Validate all external input at system boundaries.
  • Follow OWASP top-10 awareness for any web-facing code.
  • Pin CI action versions to full SHA, not tags.

Dependencies

  • Rust: pin exact versions in Cargo.toml for binaries; use semver ranges for libraries.
  • TypeScript: use a lockfile (package-lock.json or pnpm-lock.yaml). Commit it.
  • Review dependency updates via Dependabot or Renovate PRs — don't auto-merge.

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.