Browse / General-purpose / claude-setup

claude-setup

siddharth-Spark18

My Claude Code workflow: agents, skills, evals, orchestration rules

Open siddharth-Spark18/claude-setup → Checked against the four rules.

Built for one agent

ships CLAUDE.md and nothing for other agents.

In its own words

README.mdsiddharth-Spark18/claude-setup

My Claude Code workflow, kept in git so it's the same on every machine and can keep improving: orchestration rules (CLAUDE.md), specialist agents, skills, eval cases, and portable settings. No project data, transcripts, memory or credentials live here.

Layout

Local-only on each machine (never committed): hooks and any other settings.json keys, and the ## AgentWatch Correlation section of CLAUDE.md. Both are preserved across installs and stripped by sync.sh.

New machine

Anything install.sh would overwrite is moved to ~/.claude/backups/claude-setup- /. Safe to re-run.

Evolving it

Agents, evals, notes and skills are symlinked, so edits (including /agent-retro) land straight in this repo's working tree. CLAUDE.md and settings.json are copies, so after changing them run:

Adding a new portable settings key or a new local-only section: edit PORTABLE_SETTINGS_KEYS / LOCAL_ONLY_HEADING in lib.sh.

The whole README. Open the repo ↗

Read from the repository's git tree on 2026-08-17.