agentleFS
gpolancogpolanco/dev-workflows/CLAUDE.md

dev-workflows

CLAUDE.md1 starsChanged 9 months agoMITView on GitHub

CLI tool that compiles developer rules into editor-specific config files (CLAUDE.md, .cursor/rules, GEMINI.md). If a decision is not in the specs, do not implement it. Propose a documentation change first. If you are on main, stop and create a branch before doing anything else.

  • Installs packages
  • In this repositoryOne other file it gives its agents.

The file

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

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Distinctive:

    If a decision is not in the specs, do not implement it.

    line 40
  2. Distinctive:

    NEVER commit directly to main.

    line 44
  3. Distinctive:

    Don't create PRs without my approval.

    line 47
  4. Distinctive:

    If you are on main, stop and create a branch before doing anything else.

    line 51
  5. Very specific:

    Do not add dependencies not listed in openspec/specs/cli/spec.md without asking.

    line 55
  6. Distinctive:

    Do not create new documentation trees.

    line 56
  7. Distinctive:

    Do not move files or rename directories unless explicitly instructed.

    line 57

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

Dev Workflows

CLI tool that compiles developer rules into editor-specific config files (CLAUDE.md, .cursor/rules, GEMINI.md).

Stack

  • Monorepo with pnpm workspaces
  • CLI in packages/cli/ (TypeScript, commander)
  • Rules in content/rules/ (Markdown with YAML frontmatter, hosted on GitHub)
  • Tests with node:test

Architecture

  • content/rules/ → official rule files (Markdown), fetched from GitHub via devw add
  • content/blocks/ → local prebuilt blocks installed via devw add <block-id>
  • packages/cli/src/bridges/ → per-tool adapters that translate rules → native format
  • Bridges only translate. They do not add new intent or logic.

Key commands

pnpm install                    # install deps
pnpm build                      # build CLI
pnpm test                       # run tests
pnpm dev                        # dev mode
devw add                        # interactive: browse and install rules from registry
devw add typescript/strict      # direct: install specific rule
devw add --list                 # list available rules

Specs (read before implementing)

  • openspec/specs/cli/spec.md → CLI spec (commands, bridges, UI, registry) — current state
  • openspec/specs/decisions/spec.md → accepted decisions (source of truth if conflict)
  • openspec/specs/docs/spec.md → Mintlify documentation site spec
  • openspec/specs/theme/spec.md → design system for the landing page
  • openspec/changes/pull-command/tasks.md → feat/pull-command branch state (pending merge)
  • openspec/ is gitignored — internal specs not published

If a decision is not in the specs, do not implement it. Propose a documentation change first.

Git workflow (BLOCKING — do this BEFORE writing any code)

  1. NEVER commit directly to main. Always create a feature branch first.
  2. Branch naming: feat/<slug>, fix/<slug>, chore/<slug>, docs/<slug>
  3. Commits: feat(scope): ..., fix(scope): ..., docs(scope): ..., chore(scope): ...
  4. Don't create PRs without my approval.
  5. One PR per feature. Include: what/why, list of changes, how to test.
  6. Clean up branch after merge.

If you are on main, stop and create a branch before doing anything else.

What NOT to do

  • Do not add dependencies not listed in openspec/specs/cli/spec.md without asking.
  • Do not create new documentation trees. Update existing docs instead.
  • Do not move files or rename directories unless explicitly instructed.

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.