agentleFS
ArangoGutierrezArangoGutierrez/claude-toolkit/.cursor/rules/workbench.mdc

claude-toolkit / rules

Cursor rule4 starsChanged 3 months agoMITView on GitHub

agents-workbench workflow — worktree-based development with branch detection

We split this workbench.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

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

    Before editing any source code, check: git branch --show-current

    line 8
  2. Very specific:

    If output is agents-workbench → source code is READ-ONLY.

    line 9
  3. Very specific:

    If inside a .worktrees/ path → you are in a worktree.

    line 10
  4. Distinctive:

    If on any other branch → normal development.

    line 11
  5. Very specific:

    Create from remote ref: git worktree add .worktrees/<name> -b <branch> "$BASE"

    line 20
  6. Distinctive:

    NEVER modify source code directly

    line 28
  7. Distinctive:

    All commits in worktrees use: git commit -s -S

    line 33
  8. Very specific:

    Run ~/.claude/scripts/setup-workbench.sh in any project

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
workbench.mdc
---
description: agents-workbench workflow — worktree-based development with branch detection
alwaysApply: true
---
# agents-workbench Workflow

## Branch Detection
Before editing any source code, check: `git branch --show-current`
- If output is `agents-workbench` → source code is READ-ONLY. Suggest a worktree.
- If inside a `.worktrees/` path → you are in a worktree. Proceed normally.
- If on any other branch → normal development. Follow project conventions.

## Branch: agents-workbench (local-only, NEVER push)
- Coordination hub: AGENTS.md, .agents/*, docs/plans/*
- Source code is READ-ONLY on this branch
- Local commits only (preserve agent state)

## Implementation: ALWAYS in worktrees
- Fetch first: `git fetch upstream 2>/dev/null && BASE="upstream/$(git symbolic-ref refs/remotes/upstream/HEAD 2>/dev/null | sed "s@^refs/remotes/upstream/@@" || echo main)" || { git fetch origin && BASE="origin/$(git symbolic-ref refs/remotes/origin/HEAD | sed "s@^refs/remotes/origin/@@")"; }`
- Create from remote ref: `git worktree add .worktrees/<name> -b <branch> "$BASE"`
- Each feature/fix gets its own worktree from the default branch
- Push feature branches from worktrees, create PRs to default branch
- Clean up after merge: `git worktree remove .worktrees/<name>`

## What is editable on agents-workbench
- OK to edit: AGENTS.md, .agents/*, docs/plans/*, CLAUDE.md, .cursor/rules/*
- OK to read: any file (for context and planning)
- NEVER modify source code directly

## Agent Teams (Cursor + Claude Code)
- Lead agent: stays on agents-workbench, coordinates via AGENTS.md
- Worker agents: each in own worktree, parallel implementation
- All commits in worktrees use: `git commit -s -S`

## Setup
Run `~/.claude/scripts/setup-workbench.sh` in any project

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.