painhardcore

painhardcore/pstack

Skill Claude CodeCodex

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

painhardcore/pstack

Skill Claude CodeCodex

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

painhardcore/pstack

Skill Claude CodeCodex

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

painhardcore/pstack

Skill Claude CodeCodex

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

painhardcore/pstack

Skill Claude CodeCodex

Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

painhardcore/pstack

Skill Claude CodeCodex

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

painhardcore/pstack

Skill Claude CodeCodex

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'.

painhardcore/pstack

Skill Claude CodeCodex

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

painhardcore/pstack

Skill Claude CodeCodex

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

painhardcore/pstack

Skill Claude CodeCodex

Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

painhardcore/pstack

Skill Claude CodeCodex

Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.

painhardcore/pstack

Skill Claude CodeCodex

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

painhardcore/pstack

Skill Claude CodeCodex

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming…

painhardcore/pstack

Skill Claude CodeCodex

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping…

painhardcore/pstack

Skill Claude CodeCodex

Fan out N independent workers, collect their results, and return one report for coverage, races, gauntlets, or exploration.

painhardcore/pstack

Skill Claude CodeCodex

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

painhardcore/pstack

Skill Claude CodeCodex

Explain a body of work plainly so a person actually understands it. Runs the how and why skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

painhardcore/pstack

Skill Claude CodeCodex

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

painhardcore/pstack

Skill Claude CodeCodex

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

painhardcore/pstack

Skill Claude CodeCodex

Cut AI tells from any writing. Must always apply.

painhardcore/pstack

Skill Claude CodeCodex

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics…

painhardcore/pstack

Instructions file CodexOpenCode

AGENTS.md instructions for painhardcore/pstack, covering pstack instructions for codex, direct skills, portable behavior, playbooks and repository checks.