Red-Team Your Design Before You Build
Coding
Have a critic argue your design is wrong, log every objection, and require evidence to close each one. Inspired by Forward Future's Loop Library.
Prompt
Step 1 — State the design Write down the design you are about to commit to and the assumptions behind it. Step 2 — Attack it Ask the AI to play a skeptical critic and argue, with specifics, why this design will fail. Record every objection in a list. Step 3 — Answer with evidence For each objection, either fix the design or document why you accept the risk, backed by evidence, not hand-waving. Step 4 — Close the loop Have the critic reopen any answer that is unsupported. Stop only when no high-impact objection remains open.
Use this prompt in AIniverse
Tap to copy, run it on ChatGPT / Claude / Gemini, save to your stack, or remix.
Open in AppMore Coding prompts
Independent Verifier Pass
When implementation claims done, a separate verifier pass runs build, lint, and tests with no access to the implement...
API Contract Until Match
Loop until API responses match the OpenAPI or JSON Schema contract — catch drift between docs and implementation.
De-Sloppify Pass
After implementation, run a cleanup pass: remove debug code, tighten naming, delete dead branches, and align with pro...
Merge Conflict Resolver
Rebase or merge target branch, resolve conflicts file by file, and loop until the branch is current and tests pass.