← ClaudeAtlas

pii-detectorlisted

Proactive PII add-on — augments the main response with PII guidance. Auto-trigger on any form, schema, migration, model, API route, GraphQL resolver, auth flow, or data design discussion. Also fires on: middleware, webhooks, workers, seed/fixture/factory files, delete/export/purge/anonymize functions, cron jobs, HTTP clients, controllers, services, resolvers. Trigger phrases: "build a form", "collect X data", "what fields should I include", "how should I design the schema", "POC / lead / contact / user / customer information", "store / save / persist X", "sign up / login / auth / registration", "share thoughts on how to build". Trigger on field names: email, phone, name, dob, ssn, card, cvv, password, token, secret, api_key, health, biometric, ip_address, salary, session, device_id, notes, metadata (on user-facing models).
goSprinto/compliance-skills · ★ 122 · API & Backend · score 77
Install: claude install-skill goSprinto/compliance-skills
# PII Developer Skill — USA Focus Automatic PII checks during development. Fires on both what the user asks for AND what Claude is about to generate — not just on keyword matching. --- ## Core Principle Check before generating. Never produce code and then suggest fixes. The sequence is always: detect intent → run relevant checks → generate correct code. If there is ANY ambiguity — check it. False positives are cheap. Missed PII in production is a breach, a fine, or both. When suggesting fixes, use the language, framework, and idioms of the code being reviewed. Never suggest a fix in a different language than the one being written. If the codebase is Python, fix in Python. If Rails, fix in Ruby. If Go, fix in Go. Claude infers the language from context — no need to specify. --- ## Step 1 — Detect the Mode Read the user's request AND what Claude is about to produce. Choose the mode first — this determines everything else. **Planning / Review mode** — user is discussing, designing, reviewing, or asking Claude to read/check existing code. No new code being generated. → Load: `modes/planning.md` → Enrich Claude's natural response with PII notes. No standalone report. Signals: "review", "read", "look at", "check this", "share thoughts", "how should I build", "I want to build X", "help me design", "feedback on", "thoughts on", reading or analyzing an existing file without generating new code. **Generation mode** — Claude is about to write new code from scratch. → Load re