ConfigDeckReuse your Claude Code .claude/ configs across every project
Three patterns: user-level settings, a skeleton repo, and ConfigDeck packs.
Are you rewriting .claude/ from scratch every time?
Split `.claude/` into project-specific parts and cross-project parts, and reuse the latter.
Pattern 1: user-level settings (~/.claude/)
Personal preferences (coding style, always-on hooks, always-on MCP connections) belong in `~/.claude/`, applied across every project.
Pattern 2: a skeleton template repo
Keep your go-to subagents, a CLAUDE.md template and hooks in one template repo; clone it for new projects and adjust.
Pattern 3: use a ConfigDeck pack
Pick a use-case starter pack from /packs and install with one click, or via the CLI:
$ npx configdeck add <pack-name>Sharing with a team
Commit project-level `.claude/` to your repo, but keep secrets out of it — use env vars or a key manager instead.
When to refresh
Revisit your template every 3–6 months so stale rules don't linger across projects.
FAQ
Where should shared config live?
Personal defaults in ~/.claude/, project-specific rules in the project's .claude/.
How do I avoid repeating setup?
A template repo, or a ConfigDeck starter pack via `npx configdeck add`.
Can .claude/ be shared with a team?
Yes, commit the project-level .claude/ — but never hardcode secrets in it.
When should I refresh reused configs?
Every 3–6 months is a reasonable cadence.
Is it safe to install the same ConfigDeck pack repeatedly?
Yes — install only writes inside the chosen project's .claude/.