painhardcore

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind…

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading.

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session…

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries.

Apply when introducing a new internal API while old callers still exist.

Apply when reviewing or shaping code that's hard to trace.

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.

Apply when tempted to ask 'should I do X?' on reversible work.

Use before review when the user asks to strip, remove, or clean up comments in code.

Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.

Apply after completing a task, before declaring done.

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes…