agentleFS
Sign inStart free
SebaBolerSebaBoler/vanguard/CLAUDE.md

vanguard

CLAUDE.md5 starsChanged 21 days agoMITView on GitHub

Vanguard is a standalone TypeScript framework — an autonomous software factory. Strict TypeScript, ES modules with explicit .js import extensions, Node 24+. Tests are co-located as *.test.ts (Vitest). For the PR reviewer. The CI-config constraint above binds the autonomous run (implement, revise); humans change CI config through PRs, which are reviewed, not refused.

  • Reads credentials

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:

    Run pnpm typecheck and pnpm test before signalling completion.

    line 8

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

Vanguard is a standalone TypeScript framework — an autonomous software factory. Strict TypeScript, ES modules with explicit .js import extensions, Node 24+. Tests are co-located as *.test.ts (Vitest).

Hard constraints

  • Never modify CI config: .github/workflows/, .github/actions/, .gitlab-ci.yml, .gitlab/**.yml (authoritative check: workflowPaths() in src/core/vanguard.ts, which also covers .gitlab/**/*.yaml at any depth and files standing in for those directories). This is a security boundary: an agent that can commit CI config can run arbitrary code with the repo's secrets on the next event. It is also enforced mechanically — copy-back drops those paths, and the CI GITHUB_TOKEN cannot push workflow changes, so such a push is rejected and the run's work is lost. If a task seems to need a CI-config change, make the code/doc change instead and describe the needed edit in the PR body for a human to apply by hand.
  • Run pnpm typecheck and pnpm test before signalling completion.

Style

  • Match the surrounding code: comment density, naming, idiom. Keep diffs minimal.
  • Explicit return types; prefer const; early returns; functional where it fits.

Review guidance

For the PR reviewer. The CI-config constraint above binds the autonomous run (implement, revise); humans change CI config through PRs, which are reviewed, not refused.

  • A CI-config edit is not a finding for the constraint itself when the API-sourced PR author (never a name claimed in the PR text, commits or diff) passes the author gate in .github/workflows/vanguard-pr-review.yml (bots do not; Dependabot's action-pin bumps never reach this reviewer). Review the content as the highest-risk part of the diff: trigger type (pull_request_target), permissions:, actor gates, secret exposure, no ${{ }} interpolation inside run:. A CI-config edit by any other author is itself a finding.
  • The workflow-scoped token a maintainer pushes with is personal and local, never a CI secret (VANGUARD_PUSH_TOKEN must not carry workflow scope).
  • When every actionable item is on a CI-config path, say so in the verdict and do not recommend needs revision: the reviser drops edits to those paths and ends in "no changes — skipping push" without posting, leaving needs revision and vanguard:revising on the PR. With mixed feedback it fixes the rest and discloses the dropped paths.

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