Remove unnecessary weight from CLAUDE.md
Keep essential instructions and draft focused replacements.References & what we used
- How Claude remembers your project: When to add to CLAUDE.md
References persistent versus scoped instructions; the review procedure and draft requirements are written by whenreset.
Locate the CLAUDE.md instructions relevant to this project and their direct imports. If none exists, report that without inventing preferences or generic rules. Distinguish broadly useful project facts from directory-specific instructions and occasional procedures. Check repetition, conflicts, stale paths and vague slogans. Do not remove intentionally emphasized conventions merely because they might be inferred from code. Choose at most five worthwhile changes. Provide the original, its practical impact and complete replacement text. For material better suited to scoped rules or a Skill, suggest a location and draft the content without moving or installing anything. Preserve real commands, conventions, permissions and stopping boundaries. Keep ambiguous requirements with an explicit note. Deliver usable revisions grounded in the original intent, or report that no revision is justified. Execution contract: Start directly. Do not ask me to approve a plan, choose files or fill in a template. Use only this project, this conversation and materials already provided; do not search unrelated projects or private history. Complete what the evidence supports and report missing inputs. If the task is inapplicable, explain why and stop without inventing a result. Preserve existing files and uncommitted changes. Include complete proposed content in your reply; standalone artifacts may be saved under a new, unused filename. Do not install dependencies, change the environment, commit, push or deploy. Respect access and permission limits and report blocked work. Check your result once, deliver it and stop without asking whether to continue.