same-set-reusable-flow-for-project-file-inventor

# Project File Inventory Classification Use this skill when a Meta_Kim workspace has too many files and the user needs to know which are useful, generated, risky, or safe to ignore. ## Goal Produce a source-backed inventory, not a cleanup guess. The output should help the user decide what to keep, commit, ignore, or inspect again. ## Required Evidence Start with read-only evidence: 1. `git status --short --branch` 2. `git ls-files` 3. `git ls-files --others --exclude-standard` 4. `git check-ignore -v <path>` for suspicious ignored paths 5. `rg -n "<filename-or-command>" package.json docs scripts tests canonical config` for tracked candidates 6. `npm run` script inventory from `package.json` Do not classify a tracked file as removable only because it has few references. Check package scripts, tests, docs, sync scripts, setup scripts, and contracts first. ## Classification Buckets - **Core source**: `canonical/`, `config/contracts/`, `config/capability-index/`, durable scripts, package scripts, and tests that define behavior. - **Runtime projection**: `.claude/`, `.agents/`, `.cursor/`, `openclaw/`, `.codex/` mirrors generated from canonical sources or sync scripts. - **Generated evidence**: `.meta-kim/state/default/`, graph outputs, reports, SQLite run state, smoke artifacts, and temporary proof files. - **Planning continuity**: `task_plan.md`, `findings.md`, `progress.md`; keep during active work even if ignored. - **Reference docs**: tracked docs and plans that expl...