fake-data-guardlisted

# Fake Data Guard ## Install Save this file as `~/.claude/skills/fake-data-guard/SKILL.md`, or `.claude/skills/fake-data-guard/SKILL.md` to scope it to one repo. Claude Code auto-discovers it. Invoke with `/fake-data-guard` or by asking "could any fake data reach production?". ## Why this exists Every project grows demo data. Seed scripts with plausible users, fixtures with realistic-looking metrics, a placeholder testimonial nobody removed. All of it is correct locally and radioactive in production. The damage is asymmetric. A crash is embarrassing and recoverable. Published invented traction is a trust failure, and for anything that sells, reviews, or reports numbers it is the one mistake that cannot be walked back. It is also usually invisible: the fake row looks exactly like a real row. The path is almost always short and boring. A seed script one keystroke from a migration command in a runbook. A fixture imported by a component that ships. A constants file someone reached for because the real query was not ready yet. ## Step 1 — Find the fabricated data Search for the shapes, not the word "fake". Fabricated data rarely labels itself. **Invented people.** Realistic full names next to handles or emails in source: ``` rg -n "name:\s*['\"][A-Z][a-z]+ [A-Z][a-z]+['\"]" --type-add 'src:*.{ts,tsx,js,jsx,py,rb,go}' -tsrc rg -n "@(example|test|demo|acme)\.(com|org|local)" -tsrc ``` **Invented numbers.** Hardcoded counts, ratings, revenue, follower counts: ``` rg -n "(