scope-instructionslisted
Install: claude install-skill wardawgmalvicious/claude-plugins
# Scope instructions: where each piece of guidance lives
The question about a repo's agent guidance is rarely what to write and
usually where. Each home loads on its own trigger and misses in silence:
the guidance is on disk, correct, and never read. The built-ins answer
the other questions. In a trial on 2026-10-15, `CLAUDE_CODE_NEW_INIT=1`
`/init` and the `claude-md-improver` skill each cut derivable lines,
surfaced a README's rule and caught a stale command, and in three runs
neither moved a section out of a root `CLAUDE.md` into a nested file or
a `paths:` rule. This skill asks what they skip, of every section:
**what event loads its home, and does that event come before the mistake
it guards against?**
The homes and how each fails live in one place, the user-scope rule
`agent-instructions-scoping.md`, which this skill applies and does not
restate. It **proposes**; files change only on approval, and committing
is `commit-changes`'s.
Past that rule, the live page: code.claude.com by the
`claude-code-docs` MCP server or
`curl -s https://code.claude.com/docs/en/<page>.md`, and another
tool's file by that tool's own markdown source, else `WebFetch`, saying
it read a summary. A live page that contradicts a line here wins: say
so, act on the page, and route the fix by `capture-learning`, bar a
dated measured line that names the page it overrules and the call that
measured it, which a page changed since its date sends back to re-measure.
An observed claim is cited or marked p