Use when creating a worktree, setting up a worktree, starting feature work that needs isolation, or before executing implementation plans. Covers git worktree creation under .worktrees/, gitignore setup, beads integration, and merge guardrails.
Creates isolated git worktrees for parallel development with automatic beads integration and safety checks.
npx claudepluginhub rbergman/dark-matter-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.
Primary tool: bd worktree — handles git worktree + beads integration automatically.
/merge when ready to integrate — it enforces the pre-flight checklist.Before creating any worktrees, ensure .worktrees/ is in .gitignore. This is a one-time setup that covers all future worktrees:
# Check if .worktrees/ is already ignored
git check-ignore -q .worktrees/ || echo '.worktrees/' >> .gitignore
If you added the line, commit it:
git add .gitignore && git commit -m "Ignore .worktrees/ directory"
Why this matters: Without this, beads adds each worktree individually to .gitignore, creating noise. With .worktrees/ ignored, all worktrees underneath are automatically covered.
All worktrees go under .worktrees/ in the repo root. This is the standard location.
bd worktree create .worktrees/feature-auth
What it does automatically:
.beads/redirect pointing to main repo's databaseWith custom branch name:
bd worktree create .worktrees/bugfix --branch fix-123
CLAUDE.local.md only exists in one worktree. To share personal preferences across all worktrees, use a home-directory import in each worktree's CLAUDE.local.md:
# CLAUDE.local.md
@~/.claude/my-project-instructions.md
This way all worktrees load the same personal preferences from a single source. The @~/... import syntax resolves to your home directory regardless of which worktree you're in.
cd .worktrees/feature-auth
# Node.js
[ -f package.json ] && npm install
# Rust
[ -f Cargo.toml ] && cargo build
# Go
[ -f go.mod ] && go mod download
npm test # or cargo test, go test ./...
If tests fail: Report failures, ask whether to proceed.
bd ready # Should show same beads as main workspace
bd worktree list
Or standard git:
git worktree list
Use bd worktree remove — includes safety checks:
bd worktree remove feature-auth
Safety checks (automatic):
Skip checks (not recommended):
bd worktree remove feature-auth --force
Check current worktree status:
bd worktree info
| Task | Command |
|---|---|
| Ensure .worktrees/ ignored | git check-ignore -q .worktrees/ || echo '.worktrees/' >> .gitignore |
| Create worktree | bd worktree create .worktrees/<name> |
| Create with branch | bd worktree create .worktrees/<name> --branch <branch> |
| List worktrees | bd worktree list |
| Remove worktree | bd worktree remove .worktrees/<name> |
| Check status | bd worktree info |
| Verify beads sync | bd ready (in worktree) |
| Manual git worktree | bd worktree |
|---|---|
| Separate commands for git + beads | Single command |
| No beads redirect setup | Automatic redirect to main DB |
| No safety checks on remove | Checks for uncommitted/unpushed |
# One-time: ensure .worktrees/ is ignored
git check-ignore -q .worktrees/ || echo '.worktrees/' >> .gitignore
# Create isolated workspace
bd worktree create .worktrees/feature-auth
# Enter and setup
cd .worktrees/feature-auth
npm install
npm test # ✓ 47 passing
# Verify beads shared
bd ready # Shows same issues as main
# Work on feature...
bd claim auth-001
# When done
cd ../..
bd worktree remove .worktrees/feature-auth
Daemon mode does not work correctly with user-created git worktrees. Worktrees share the same .git directory and beads database, but the daemon doesn't track which branch each worktree has checked out.
Solution: Use direct mode in worktrees:
bd --no-daemon <command>
# Or set environment variable
export BEADS_NO_DAEMON=1
Don't confuse these:
| Type | Location | Purpose |
|---|---|---|
| User worktrees | .worktrees/<name> | Parallel feature work (you create these) |
| Beads internal | .git/beads-worktrees/beads-sync | Sync-branch commits (beads creates this) |
The internal worktree is hidden and managed by beads for the sync-branch feature. Don't manually modify it.
If git status doesn't show changes to .beads/*.jsonl files, check for SKIP_WORKTREE flags:
git ls-files -v .beads/
# 'h' prefix = SKIP_WORKTREE set (changes hidden)
# 'H' prefix = normal tracking
Fix: Remove and re-add the files:
git rm --cached .beads/issues.jsonl
git add .beads/issues.jsonl
Or run bd sync which sets the correct index flags.
If beads isn't installed, use manual git worktree:
# Verify ignored
git check-ignore -q .worktrees/ || echo '.worktrees/' >> .gitignore
# Create
git worktree add .worktrees/feature-auth -b feature-auth
# Remove
git worktree remove .worktrees/feature-auth
But you lose: automatic gitignore, beads sync, and safety checks.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.