Use this skill for Proto production incidents and reliability work. Read before changing code:
- Reproduce the failure against the relevant preview or production route when safe.
- Inspect Vercel runtime errors and deployment metadata.
- Trace the route into its integration boundary: Supabase, catalogue, stock, Instore, Brevo, or authentication.
- Separate user-input errors, transient upstream failures, configuration failures, and code defects.
- Write a failing regression test before implementing a fix.
- Add bounded timeouts, useful error categories, and safe user-facing fallbacks where appropriate.
- Verify the complete flow in a browser and inspect the post-fix runtime signal.
Known Proto signals to check first include shared url.parse() deprecation warnings, incomplete extended-range catalogue lookups, stock timeouts, missing Instore configuration, invalid catalogue credentials, unsupported .jfif uploads, weak-password registration errors, and idempotent archive/unarchive actions.
Never expose secrets, service keys, auth tokens, or private customer data in logs, issues, screenshots, or commits. Do not suppress a warning until its source is identified.
1---2name: proto-production-debugging3description: Diagnose Proto production failures across Vercel, Supabase, catalogue integrations, stock, registration, uploads, and order flows.4---56Use this skill for Proto production incidents and reliability work. Read before changing code:781. Reproduce the failure against the relevant preview or production route when safe.92. Inspect Vercel runtime errors and deployment metadata.103. Trace the route into its integration boundary: Supabase, catalogue, stock, Instore, Brevo, or authentication.114. Separate user-input errors, transient upstream failures, configuration failures, and code defects.125. Write a failing regression test before implementing a fix.136. Add bounded timeouts, useful error categories, and safe user-facing fallbacks where appropriate.147. Verify the complete flow in a browser and inspect the post-fix runtime signal.1516Known Proto signals to check first include shared `url.parse()` deprecation warnings, incomplete extended-range catalogue lookups, stock timeouts, missing Instore configuration, invalid catalogue credentials, unsupported `.jfif` uploads, weak-password registration errors, and idempotent archive/unarchive actions.1718Never expose secrets, service keys, auth tokens, or private customer data in logs, issues, screenshots, or commits. Do not suppress a warning until its source is identified.
Gee9999