My personal Claude Code configuration — the
version-controlled parts of ~/.claude: global instructions, always-on rule/lesson guards,
user-authored skills, and a statusline script.
| Path | What it is |
|---|---|
CLAUDE.md |
Global instructions auto-loaded into every session — preferences, environment notes, coding style. |
rules/ |
Always-loaded lessons and action-guards — narrow guards against specific, recurring failure modes. |
skills/genseq/ |
Generative sequencer. Turns a task into the optimal generative sequence — the smallest living version of the whole, grown step by step by felt necessity. Ships with three worked examples and the verbatim Christopher Alexander source. See its own README. |
skills/chrome-mcp/ |
Gotchas and known-bad patterns for the Chrome MCP browser-automation tools. |
skills/find-past-claude-session/ |
Locate a past Claude Code conversation by topic, title, or phrase. |
statusline-command.ps1 |
PowerShell statusline script. |
The .gitignore is an allowlist: it ignores everything in ~/.claude by default and
re-includes only the files above. Credentials, session history, auto-memory, plugin-installed
skills, and machine-specific settings (settings.json) are never committed. If you fork this as
your own ~/.claude repo, that safety carries over — any new state file a future Claude Code
version writes stays ignored unless you explicitly allow it.
Everything lives under ~/.claude/ (%USERPROFILE%\.claude on Windows). Skills load at session
start, so restart Claude Code / start a new session after copying. Pick one:
git clone https://github.com/cjunekim/claude-config.git /tmp/claude-config
cp -r /tmp/claude-config/skills/genseq ~/.claude/skills/Then invoke it by name: /genseq <task>.
git clone https://github.com/cjunekim/claude-config.git /tmp/claude-config
cp -r /tmp/claude-config/{CLAUDE.md,rules,skills,statusline-command.ps1} ~/.claude/CLAUDE.md and rules/ encode my preferences and environment (Windows, Korean locale, specific
tooling) — read them and adapt before adopting wholesale.
git clone https://github.com/cjunekim/claude-config.git ~/.claudestatusline-command.ps1 is the script only; the settings.json that points at it is
machine-specific and not tracked. Wire it up with /statusline, or in ~/.claude/settings.json:
{ "statusLine": { "type": "command", "command": "pwsh -File C:/Users/<you>/.claude/statusline-command.ps1" } }Use forward slashes in that command path even on Windows — settings.json command fields are
run through bash, which strips backslashes.