v0.4.5 - Memory-import orchestrator, setup guide, contributor surface

dazzle-claude-code-config v0.4.5

A curated, working set of Claude Code skills, commands, and agents -- a live ccs payload repo you can fork as your own config home -- and, as of this release, adoptable end-to-end: an orchestrating CLAUDE.md you never have to edit, a five-step install, and the full setup walk.

The 0.4.x series is the "make it adoptable" wave on top of v0.4.0 (the maximal collection: 14 skills / 28 commands / 11 agents). Content is stable; docs and adoption mechanics moved fast this series.

What's New in 0.4.x

The orchestrator imports your personal sections (v0.4.1)

Born from a real drift problem: the global CLAUDE.md originally asked adopters to edit [FILL IN] sections in place -- which forks the shared file and turns every upstream pull into a merge conflict. Now the personal sections are Claude Code memory imports:

@~/claude/claude-config/environment.md
@~/claude/claude-config/projects.md
@~/claude/claude-config/task-rules.md

ccs apply seeds all three with starter templates (never overwriting existing files -- seed-if-absent), your details live in user territory where no sync or upgrade touches them, and the shared CLAUDE.md stays byte-identical to upstream forever. Verified on a pristine fixture: one ccs apply lands the orchestrator plus all three seeds, and a second apply reports nothing to do.

Also in v0.4.1: python scripts/install-hooks.py -- the guard-hook installer now runs identically from cmd, PowerShell, or any POSIX shell.

Install quickstart + the exhaustive setup guide (v0.4.3)

The README now opens with the whole install in five steps:

pip install dazzle-claude-config
git clone <your-fork-or-this-repo> ~/claude/dazzle-claude-code-config-public
ccs apply --checkout-dir ~/claude/dazzle-claude-code-config-public
# then: edit the seeded ~/claude/claude-config/*.md and set CLAUDE_CODE_ROOTS

and docs/setup.md is the exhaustive walk: Claude Code install, fork-vs-consume, what ccs apply actually does, personalization, the companion DazzleML plugins (session-logger, claude-session-backup with csb setup), hooks, verification, multi-machine rollout, and troubleshooting seeded with real failure modes. docs/customization.md is the companion checklist of every directory, env var, and placeholder that expects your values.

Contributor surface + docs truth-ups (v0.4.2 / v0.4.4 / v0.4.5)

CONTRIBUTING.md (ground rules for a config collection: no personal content, cross-platform conventions, the guard hooks, VERSION/CHANGELOG lockstep), docs/platforms.md + Platform badge, the standard footer, docs-index corrections, and the PAL MCP (aka Zen MCP) rename.

Installation

See the quickstart above, or fork first (recommended) so the repo becomes your payload: the manifest, guards, and hook installer travel with the fork. Pairs with ccs v0.2.0, which also accepts any bare ~/.claude mirror as a payload -- not just this layout.

Version History (0.4.x)

Version	Key Change
v0.4.5	Current -- README wording pass, PAL MCP rename
v0.4.4	CONTRIBUTING, platforms doc + badge, house footer
v0.4.3	Install quickstart + exhaustive docs/setup.md
v0.4.2	docs index truth-up
v0.4.1	Memory-import orchestrator, cross-platform hook installer
v0.4.0	The maximal collection -- first release

Earlier: v0.1.0-v0.3.0 (seed through settings/docs waves) -- see the CHANGELOG.

Platform Support

Platform	Status
Windows 10/11	Tested (primary dev; Git Bash for shell scripts, Python installer for hooks)
Linux / macOS / BSD	Expected to work (markdown-first content; POSIX-native scripts)

Details: docs/platforms.md

Requirements

• Claude Code
• git; Python 3.10+ (for ccs and the hook installer)
• Optional: node (Bash-guard hook + statusline), gh CLI (GitHub workflow commands), dazzlecmd

Validation: every published file passed personal-marker sweeps plus independent adversarial content review; the install path is verified by pristine-fixture ccs apply runs (idempotency included); pushes go through a credential-scanning guard that travels with forks.