← ClaudeAtlas

logic-auditlisted

Project-wide hunt for logical holes, meaning places where the system does not follow its own stated rules on every path. Covers a rule enforced in one place and skipped in another, two places computing the same fact differently, something left behind when a role, membership, event or record ends, features built at different times that never learnt about each other, gated features leaking past their gate, and decided features that were never built. Audit-only by default; fixes need explicit permission. Use when the user asks to find or plug logical holes or loopholes, check that the system is consistent with its rules or decisions, audit business logic, or make sure everything is logically consistent. Also use before launching a feature that touches money, roles, entitlements, flags or deletion.
swarnimodi/vibecoding-skills · ★ 0 · Code & Development · score 70
Install: claude install-skill swarnimodi/vibecoding-skills
# Logic audit Find every place where the system's behaviour does not follow, on every path, a rule the project has stated, or a rule that plainly follows from the stated ones. Report them. Fix them only when the user says so. This is not a code review, a style pass, a performance pass or a security scan, though it finds security and money bugs. Its question is always: **"the rules say X; is X true everywhere, for everyone, at every point in time?"** ## 0. Mode: audit-only unless told otherwise - **The default deliverable is a report.** While auditing, do not edit code, data, configuration, schemas or docs, and do not commit, push, deploy or run migrations. - **Fixing is a separate, permissioned step.** Start it only after the user explicitly approves which findings to fix (see section 7). "Find the holes" is not permission to fix them; "find and plug the holes" is permission to propose fixes, and anything consequential (data writes, migrations, deploys, merges) still needs its own explicit go. - **Never touch production to prove a hole,** and never copy production data or secrets into an audit environment, a report or a prompt. ## 1. Index all the context first (mandatory) Every audit starts here. Do not hunt for a single hole until this index exists. An audit that skips it finds holes against rules it guessed. Assume nothing about the setup: no particular agent, memory service or earlier conversation. Check each source below and record it as **found** (w