Updated 1w ago
by painhardcore
pstack
Portable coding-agent workflows adapted from Cursor’s pstack for Codex, Claude Code, and OpenCode.
20 GitHub stars (20)
+9 in 23 days
| Period | New stars |
|---|---|
| Oct 20 | 0 |
| Oct 21 | +1 |
| Oct 22 | 0 |
| Oct 23 | 0 |
| Oct 24 | 0 |
| Oct 25 | 0 |
| Oct 26 | 0 |
| Oct 27 | +1 |
| Oct 28 | +1 |
| Oct 29 | +1 |
| Oct 30 | 0 |
| Oct 31 | 0 |
| Nov 1 | +1 |
| Nov 2 | 0 |
| Nov 3 | 0 |
| Nov 4 | 0 |
| Nov 5 | 0 |
| Nov 6 | +1 |
| Nov 7 | +1 |
| Nov 8 | 0 |
| Nov 9 | 0 |
| Nov 10 | 0 |
| Nov 11 | +2 |
- 30 skills (30 skills found in its SKILL.md files)
- 4 forks (4 forks)
- 1w ago last update (Last updated 1w ago)
Install
Skills CLI
npx skills add painhardcore/pstack
Asks which skills and agents to install. Just one: npx skills add painhardcore/pstack --skill architect — add -g for every project.
Claude Code
git clone https://github.com/painhardcore/pstackcp -r "pstack/skills/architect" ~/.claude/skills/
Copies the architect skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add painhardcore/pstack
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 82 files.
-
architect
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.
skills/architect/ on GitHub (opens in a new tab)SKILL.md -
arena
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.
skills/arena/ on GitHub (opens in a new tab)SKILL.md -
blast-radius
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.
skills/blast-radius/ on GitHub (opens in a new tab)SKILL.md -
bro
Use when the user asks to restate or explain the last message in plain, jargon-free language.
skills/bro/ on GitHub (opens in a new tab)SKILL.md -
create-verification-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.
skills/create-verification-skill/ on GitHub (opens in a new tab)SKILL.md -
figure-it-out
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.
skills/figure-it-out/ on GitHub (opens in a new tab)SKILL.md -
how
Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.
skills/how/ on GitHub (opens in a new tab)SKILL.md -
interrogate
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.
skills/interrogate/ on GitHub (opens in a new tab)SKILL.md -
maintain-verification-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".
skills/maintain-verification-skill/ on GitHub (opens in a new tab)SKILL.md -
no-comments
Use before review when the user asks to strip, remove, or clean up comments in code.
skills/no-comments/ on GitHub (opens in a new tab)SKILL.md -
poteto-mode
Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.
skills/poteto-mode/ on GitHub (opens in a new tab)SKILL.md -
principle-boundary-discipline
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.
skills/principle-boundary-discipline/ on GitHub (opens in a new tab)SKILL.md -
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 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.
skills/principle-build-the-lever/ on GitHub (opens in a new tab)SKILL.md -
principle-encode-lessons-in-structure
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.
skills/principle-encode-lessons-in-structure/ on GitHub (opens in a new tab)SKILL.md -
principle-exhaust-the-design-space
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.
skills/principle-exhaust-the-design-space/ on GitHub (opens in a new tab)SKILL.md -
principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
skills/principle-experience-first/ on GitHub (opens in a new tab)SKILL.md -
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 it, resist nil-check guards that silence crashes.
skills/principle-fix-root-causes/ on GitHub (opens in a new tab)SKILL.md -
principle-foundational-thinking
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.
skills/principle-foundational-thinking/ on GitHub (opens in a new tab)SKILL.md -
principle-guard-the-context-window
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.
skills/principle-guard-the-context-window/ on GitHub (opens in a new tab)SKILL.md -
principle-laziness-protocol
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.
skills/principle-laziness-protocol/ on GitHub (opens in a new tab)SKILL.md -
principle-make-operations-idempotent
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.
skills/principle-make-operations-idempotent/ on GitHub (opens in a new tab)SKILL.md -
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 same wave instead of preserving compatibility layers.
skills/principle-migrate-callers-then-delete-legacy-apis/ on GitHub (opens in a new tab)SKILL.md -
principle-minimize-reader-load
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.
skills/principle-minimize-reader-load/ on GitHub (opens in a new tab)SKILL.md -
principle-model-the-domain
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.
skills/principle-model-the-domain/ on GitHub (opens in a new tab)SKILL.md -
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-correct after the fact; reserve confirmation for irreversible actions.
skills/principle-never-block-on-the-human/ on GitHub (opens in a new tab)SKILL.md -
principle-outcome-oriented-execution
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.
skills/principle-outcome-oriented-execution/ on GitHub (opens in a new tab)SKILL.md -
principle-prove-it-works
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.'
skills/principle-prove-it-works/ on GitHub (opens in a new tab)SKILL.md -
principle-redesign-from-first-principles
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.
skills/principle-redesign-from-first-principles/ on GitHub (opens in a new tab)SKILL.md -
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; serialize structurally only when one shared writer is a real invariant.
skills/principle-separate-before-serializing-shared-state/ on GitHub (opens in a new tab)SKILL.md -
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 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.
skills/principle-sequence-verifiable-units/ on GitHub (opens in a new tab)SKILL.md
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.