AI Bug Patterns

Use this skill when AI-assisted code passes happy-path tests but could be silently wrong. These bugs return clean responses with the wrong access, state, timing, or data source.

Working rule

Review the negative space, not just the feature path:

1. Name who must be denied, what state must stay synchronized, and which operations must be atomic, cancel-safe, or idempotent.
2. Check whether omission fails closed. Missing auth, scope, config, or validation should block work, not allow it.
3. Ask for pre-production evidence: negative, cross-tenant, concurrent, retry, cache-invalidation, or startup checks.

Scan these clusters