← ClaudeAtlas

init-user-instructionslisted

Audits and rewrites ~/.claude/CLAUDE.md, Claude Code's user-scope instructions, from its source claude/CLAUDE.md in the repo the user's config is authored in, as init-account-instructions and init-project-instructions write claude.ai's Account block and a Project's instructions. A bundled script checks the line count against the lint cap, ~/ pointers that resolve nowhere, skills named but not deployed at user scope, tools claimed on PATH or not installed, dated rules by age, counts that want a derivation command and drift from each deployed copy, then reads this machine's transcripts: corrections repeated across sessions, each rule's error text after its date, and whether the Account block loads, masked and reported as counts. Routes every line to the home that loads it, interviews, and proposes a table and a diff, adding a line only for a standing behavior the user states and only by displacing another. A repo's CLAUDE.md is scope-instructions'; one session's learning is capture-learning's.
wardawgmalvicious/claude-plugins · ★ 0 · AI & Automation · score 78
Install: claude install-skill wardawgmalvicious/claude-plugins
# Init user instructions: the user-scope CLAUDE.md `~/.claude/CLAUDE.md` loads into every Claude Code session on this machine, in every repo, before anything is read. Its source is `claude/CLAUDE.md` in the config source, the repo the user's config is authored in, copied by its `link-claude.ps1`, and its `lint-claude-md.py` caps it at `MAX_LINES`, the one place the number lives. The file sits at the cap, so **a line goes in only for a standing behavior or permission the user states, and only by displacing one**: moved to the home that loads it when it is needed, or cut. No cap rises. This is the Claude Code third of three. `init-account-instructions` writes claude.ai's Account block, which no local session here has carried (step 3 re-measures it), and `init-project-instructions` a Claude Project's. A repo's own `CLAUDE.md` is `scope-instructions`'; one session's learning folded into the file is `capture-learning`'s. This skill **proposes**; nothing changes before the user approves a row. ## 0. Where, which mode, which bound ```bash git rev-parse --show-toplevel ``` - **The config source**, the root holding `claude/CLAUDE.md` and the `link-claude.ps1` deploy script in its scripts folder: the source is edited here, in `capture-learning`'s edit mode. - **Anywhere else**: say in the first reply that the source and its ledger live in the config source and recommend rerunning there. Go on only if the user wants to, or keeps no config source, against the deployed copy