Updated 1w ago
by uzairansaruzi
p3-stack
pstack reworked for T3 Code: delegated subagents, worktree threads, PR watching, scheduled runs.
156 GitHub stars (156)
+156 in 11 days
| Period | New stars |
|---|---|
| Oct 7 | +43 |
| Oct 8 | +12 |
| Oct 9 | +3 |
| Oct 10 | +1 |
| Oct 11 | +1 |
| Oct 12 | +1 |
| Oct 13 | +1 |
| Oct 14 | +6 |
| Oct 15 | +1 |
| Oct 16 | +3 |
- 30 skills (30 skills found in its SKILL.md files)
- 15 forks (15 forks)
- 1w ago last update (Last updated 1w ago)
Install
Skills CLI
npx skills add uzairansaruzi/p3-stack
Asks which skills and agents to install. Just one: npx skills add uzairansaruzi/p3-stack --skill architect — add -g for every project.
Claude Code
git clone https://github.com/uzairansaruzi/p3-stackcp -r "p3-stack/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 uzairansaruzi/p3-stack
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 51 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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
automate-me
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 the authoring-a-skill playbook + unslop, optionally pulling fresh evidence from recent threads.
skills/automate-me/SKILL.md on GitHub (opens in a new tab) -
benchmark-checklist
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
skills/benchmark-checklist/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
bro
Restate the last message in plain human language, with no jargon.
skills/bro/SKILL.md on GitHub (opens in a new tab) -
correct
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
skills/correct/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
how
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. Use why for motivation.
skills/how/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
make-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake the agent over a webhook, when the user must provide a webhook secret, or when exposing that UI on Tailscale.
skills/make-bot-ui/SKILL.md on GitHub (opens in a new tab) -
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
skills/no-comments/SKILL.md on GitHub (opens in a new tab) -
p3-help
Guides users through p3-stack setup, /p3-mode, and picking the skill, playbook, or principle for a task. Use for /p3-help, or when the user asks how to install, set up, or use p3-stack, or which p3-stack skill fits. Not for requests to do work, even ones that name p3-stack.
skills/p3-help/SKILL.md on GitHub (opens in a new tab) -
p3-mode
p3 agent style for concise, detailed responses, deliberate delegation, unslopped prose, simple code, and verified work. Use for p3, /p3-mode, or requests to work in this style.
skills/p3-mode/SKILL.md on GitHub (opens in a new tab) -
principle-attack-the-premise
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.
skills/principle-attack-the-premise/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
principle-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
skills/principle-explain-the-number/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
principle-guard-the-context-window
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to delegated tasks; keep summaries in the main thread, not raw payloads.
skills/principle-guard-the-context-window/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab) -
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/SKILL.md on GitHub (opens in a new tab)
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.