cm-identity-guardlisted

# Identity Guard — Multi-Account Safety Protocol ## TL;DR - **Use before** any git push, Cloudflare deploy, or Supabase op - **Verifies**: GitHub account, CF account, Supabase project match expected - **Prevents**: wrong-account deploys, cross-project secret leaks ## Overview Working across multiple projects, clients, and platforms means one wrong `git push` or `wrangler deploy` can publish work to the wrong account. This skill establishes a mandatory identity check before any operation that touches external services. > [!CAUTION] > **Real incidents this skill prevents:** > - Pushed client code to personal GitHub repo > - Deployed to wrong Cloudflare account (different org's Pages project, billing confusion) > - Used personal Supabase `ANON_KEY` in a client project (wrong DB entirely) > - `git config user.email` was personal email → commits show wrong author in client repo ## The Iron Law ``` NEVER push, deploy, or use secrets WITHOUT verifying identity first. ASK: Which account? Which project? Which database? ONE command verifies all three. Run it. Always. ``` ## When to Use **ALWAYS** before: - `git push` or `git commit` in a project with multiple account contexts - `wrangler pages deploy` or any Cloudflare operation - Creating or accessing a Supabase/Neon client - Setting up a new project from scratch - Resuming work after switching between personal and work projects --- ## Account Registry (Your Known Accounts) Maintain this table in your head (or in `.project-