agentleFS
Sign inStart free
saffron-healthsaffron-health/libretto/CLAUDE.md

libretto

CLAUDE.md883 starsChanged 3 months agoMITView on GitHub

Never manually edit packages/libretto/package.json version. Use the release script: This bumps the version, updates all SKILL.md files, syncs mirrors, validates parity, commits, pushes a release-v* branch, and opens a PR. The release CI workflow triggers automatically when the PR merges to main. Temporarily set a pre-release version in packages/libretto/package.json and replace its workspace: and catalog: dependency ranges with published ranges. Then run: Approve npm's browser passkey prompt and verify the exact version installs in a clean project. Do not commit…

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After any change to source skill files or READMEs:

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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

Libretto Monorepo

Releasing a New Version

Never manually edit packages/libretto/package.json version. Use the release script:

pnpm prepare-release [patch|minor|major]

This bumps the version, updates all SKILL.md files, syncs mirrors, validates parity, commits, pushes a release-v* branch, and opens a PR. The release CI workflow triggers automatically when the PR merges to main.

Publishing an Experimental Version

Temporarily set a pre-release version in packages/libretto/package.json and replace its workspace: and catalog: dependency ranges with published ranges. Then run:

pnpm publish:experimental

Approve npm's browser passkey prompt and verify the exact version installs in a clean project. Do not commit the temporary manifest edits.

Mirror System

Skill files and READMEs are mirrored across multiple locations. Do not hand-edit the mirrored copies. Edit source files only, then sync.

Source directories:

  • packages/libretto/skills/libretto/ — interactive Libretto skill (source of truth)
  • packages/libretto/skills/libretto-readonly/ — read-only diagnosis skill (source of truth)

Mirror targets (generated — never edit directly):

  • .agents/skills/libretto/ and .agents/skills/libretto-readonly/
  • .claude/skills/libretto/ and .claude/skills/libretto-readonly/

After any change to source skill files or READMEs:

pnpm sync:mirrors    # sync all mirrored files
pnpm check:mirrors   # validate everything is in sync

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.

Reviews can't be read right now.

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