refresh-claude-mdlisted

## Constraints - Apply `@rules/php/core-standards.mdc` - Apply `@rules/git/general.mdc` - Trigger only to update or create `CLAUDE.md` — never run this as a general onboarding or audit task - Reconnaissance uses Glob and Grep; use Read only to resolve an ambiguous signal, never to read every file - Enhance, never blindly replace: preserve all human-authored sections, custom rules, and project-specific instructions already in `CLAUDE.md` - Keep `CLAUDE.md` scannable and under ~100 lines; link to `@rules/**` instead of pasting rule content - Flag unknowns explicitly ("Could not determine X") rather than speculate - Do not modify other skills, rules, or production code ## Use when - `CLAUDE.md` does not exist and the project needs one generated from the codebase - `CLAUDE.md` is stale — the tech stack, build/test commands, directory layout, or conventions have drifted from what the file documents - The user asks to "refresh", "regenerate", "update", or "rebuild" `CLAUDE.md` - A dependency, framework, or tooling change has invalidated the documented commands or structure Do **not** use this skill for ad-hoc codebase questions, code review, or onboarding write-ups — it has one job: keep `CLAUDE.md` correct. ## Execution ### 1. Decide whether a refresh is warranted - Read the existing `CLAUDE.md` (if any) and record which sections are human-authored vs auto-generated. - Confirm at least one trigger applies. If `CLAUDE.md` already matches the codebase, stop and report "no refres