painhardcore

painhardcore/pstack

Plugin Claude Code

poteto's engineering skills for rigorous AI-assisted development.

painhardcore/pstack

Plugin Claude Code

poteto's engineering skills adapted for Codex, Claude Code, and OpenCode.

painhardcore/pstack

Agent

A deranged comment-hater that savors deletion and condemns workaround code.

painhardcore/pstack

Agent

Routing target for poteto-mode and any request for poteto's style. Reads the poteto-mode skill's SKILL.md in full before any work, including its inline Principles index.

painhardcore/pstack

Skill Claude CodeCodex

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

painhardcore/pstack

Skill Claude CodeCodex

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

painhardcore/pstack

Skill Claude CodeCodex

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

painhardcore/pstack

Skill Claude CodeCodex

Use when the user asks to restate or explain the last message in plain, jargon-free language.

painhardcore/pstack

Skill Claude CodeCodex

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.

painhardcore/pstack

Skill Claude CodeCodex

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no…

painhardcore/pstack

Skill Claude CodeCodex

Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.

painhardcore/pstack

Skill Claude CodeCodex

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

painhardcore/pstack

Skill Claude CodeCodex

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

painhardcore/pstack

Skill Claude CodeCodex

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

painhardcore/pstack

Skill Claude CodeCodex

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

painhardcore/pstack

Skill Claude CodeCodex

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

painhardcore/pstack

Skill Claude CodeCodex

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

painhardcore/pstack

Skill Claude CodeCodex

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

painhardcore/pstack

Skill Claude CodeCodex

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

painhardcore/pstack

Skill Claude CodeCodex

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

painhardcore/pstack

Skill Claude CodeCodex

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

painhardcore/pstack

Skill Claude CodeCodex

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

painhardcore/pstack

Skill Claude CodeCodex

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

painhardcore/pstack

Skill Claude CodeCodex

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.