lablisted

# Lab Init — a safe place for project data The Lab is where MasterMind keeps **raw, project-specific material** — codebase notes, captured patterns, `/character` profiles, anything with real names. It is **local and gitignored**; only the **genericized, name-free output** ever graduates to a shareable field pack. This exists because raw material sitting in a publishable tree is how confidential data leaks. Make it structural, not a habit. > **Golden rule: patterns leave the Lab, identities never do.** Company/product/person/package names > stay in `lab/`. Only the general rule — stripped of every name — goes into a field pack. ## What it sets up ``` lab/ ├── .denylist ← your sensitive terms (gitignored); feeds the guards ├── raw/ ← untouched captures from a codebase ├── analysis/ ← working notes, /character profiles └── MANIFEST.md ← what's here, what's distilled, what's pending .githooks/ ├── pre-commit ← blocks staged lab/ paths, denylisted terms, and real secrets └── pre-push ← scans every commit being pushed (catches --no-verify + old history) ``` ## Steps (idempotent — safe to re-run) Run from the target repo root. The skill's files live in `assets/` next to this SKILL.md. 1. **Create the quarantine** (don't clobber existing content): - `mkdir -p lab/raw lab/analysis` - If `lab/.denylist` is missing, copy `assets/denylist.template` → `lab/.denylist`, then help the user fill it: company, product/app names, int