pstack

Skills 45

• Make Bot UI, Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must…
• Poteto Mode, poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified…
• architect, Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use fo…
• arena, Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /ar…
• automate-me, Use for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into…
• blast-radius, Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe becaus…
• bro, Restate the last message in plain human language, with no jargon.
• create-verification-skill, Generate a project-local verification skill that drives your app the way a user does — any language, framework, or plat…
• figure-it-out, Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a hu…
• how, Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering question…
• interrogate, Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\",…
• maintain-verification-skill, Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, on…
• no-comments, Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
• principle-boundary-discipline, Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, conf…
• principle-build-the-lever, Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or…
• principle-encode-lessons-in-structure, Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
• principle-exhaust-the-design-space, Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competi…
• principle-experience-first, Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship f…
• principle-fix-root-causes, Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach i…
• principle-foundational-thinking, Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what c…
• principle-guard-the-context-window, Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents;…
• principle-laziness-protocol, Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
• principle-make-operations-idempotent, Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Conve…
• principle-migrate-callers-then-delete-legacy-apis, Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
• principle-minimize-reader-load, Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state i…
• principle-model-the-domain, Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the d…
• principle-never-block-on-the-human, Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correc…
• principle-outcome-oriented-execution, Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
• principle-prove-it-works, Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actua…
• principle-redesign-from-first-principles, Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundationa…
• principle-separate-before-serializing-shared-state, Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; s…
• principle-sequence-verifiable-units, Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work i…
• principle-subtract-before-you-add, Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references…
• principle-type-system-discipline, Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make ille…
• recall, Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, pr…
• reflect, Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit…
• setup-pstack, Configure which models pstack uses per role. Detects your available models and writes an always-applied rule that overr…
• show-me-your-work, Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, e…
• swarm, Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, race…
• tdd, Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious ch…
• teach, Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what the…
• technical-writing, Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global…
• typescript-best-practices, TypeScript best practices. Use when reading or editing any .ts or .tsx file.
• unslop, Cut AI tells from any writing. Must always apply.
• why, Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thres…