chiewoscar/pstack-codex

Use only when explicitly invoked or routed by another pstack skill. 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.

Use only when explicitly invoked or routed by another pstack skill. 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.

Use only when explicitly invoked or routed by another pstack skill. Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via skill-creator + unslop, optionally pulling fresh evidence from recent transcripts.

Use only when explicitly invoked or routed by another pstack skill. 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.

Use only when explicitly invoked or routed by another pstack skill. Restate the last message in plain human language, with no jargon.

Use only when explicitly invoked or routed by another pstack skill. 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.

Remove AI-generated code slop from a branch or diff. Use when the user says "deslop", "remove AI slop", "clean up the AI code", or asks to strip over-commenting, unnecessary defensive try/catch, as any casts, deep nesting, or styling that doesn't match the surrounding file. Run before opening a PR or committing agent-written code.

Use only when explicitly invoked or routed by another pstack skill. 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 narrower playbook applies.

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.

Use only when explicitly invoked or routed by another pstack skill. 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.

Use only when explicitly invoked or routed by another pstack skill. 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".

Use only when explicitly invoked or routed by another pstack skill. Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

Use only when explicitly invoked or routed by another pstack skill. poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.

Explicit pstack principle: boundary discipline. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: build the lever. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: encode lessons in structure. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: exhaust the design space. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: experience first. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: fix root causes. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: foundational thinking. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: guard the context window. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: laziness protocol. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: make operations idempotent. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: migrate callers then delete legacy apis. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: minimize reader load. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: model the domain. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: never block on the human. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: outcome oriented execution. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: prove it works. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: redesign from first principles. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: separate before serializing shared state. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: sequence verifiable units. Use when the user names it or poteto-mode routes to it.

Explicit pstack principle: subtract before you add. Use when the user names it or poteto-mode routes to it.

Apply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test.

Explicit pstack principle: type system discipline. Use when the user names it or poteto-mode routes to it.

Use only when explicitly invoked or routed by another pstack skill. 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 work.

Use only when explicitly invoked or routed by another pstack skill. Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

Check the local pstack for Codex installation, optional Bun scripts, and supported model and reasoning effort overrides. Use when the user asks to set up pstack, choose a budget, or a bundled script fails.

Use only when explicitly invoked or routed by another pstack skill. 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 away.

Use only when explicitly invoked or routed by another pstack skill. Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.

Use only when explicitly invoked or routed by another pstack skill. 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.

Use only when explicitly invoked or routed by another pstack skill. 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'.

Use only when explicitly invoked or routed by another pstack skill. 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.

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

Cut AI tells from any writing. Must always apply.

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 warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.