---
title: "pstack"
description: "Skills and thin named agents: poteto-mode, principles, playbooks, tools."
canonical: https://agentpluginsdirectory.com/plugins/pstack--uraxii
last-updated: 2026-09-25
---

# pstack
Skills and thin named agents: poteto-mode, principles, playbooks, tools.
- Slug: pstack--uraxii
- Publisher: Uraxii
- Repository: https://github.com/Uraxii/dotai
- Manifest: plugins/pstack/plugin.json
- Version: 1.2.0
- Category (editorial): other
- Skills: 44 (architect, arena, blast-radius, deslop, figure-it-out, how, interrogate, no-comments, poteto-mode, principle-attack-the-premise, principle-boundary-discipline, principle-build-the-lever, principle-code-quality, principle-decomposition, principle-encode-lessons-in-structure, principle-exhaust-the-design-space, principle-experience-first, principle-fix-root-causes, principle-foundational-thinking, principle-guard-the-context-window, principle-laziness-protocol, principle-make-operations-idempotent, principle-migrate-callers-then-delete-legacy-apis, principle-minimize-reader-load, principle-model-the-domain, principle-naming, principle-never-block-on-the-human, principle-outcome-oriented-execution, principle-output-to-user, principle-prove-it-works, principle-redesign-from-first-principles, principle-separate-before-serializing-shared-state, principle-sequence-verifiable-units, principle-subtract-before-you-add, principle-test-behavior-not-implementation, principle-type-system-discipline, reflect, setup-pstack, show-me-your-work, swarm, tdd, technical-writing, unslop, why)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-26
- Repository last pushed: 2026-09-23
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/pstack--uraxii
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## Skills

- 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.
- 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.
- 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', reviewing a small diff you don't trust, or a brief that asserts something…
- deslop: Remove AI-generated code slop and clean up code style
- 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 migrat…
- 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 motiv…
- 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.
- no-comments: Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.
- poteto-mode: 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.
- principle-attack-the-premise: Apply when repeated fixes sharing an assumption fail. State the assumption and choose an observation that can challenge it before trying another fix that depends on it.
- 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.
- 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.
- principle-code-quality
- principle-decomposition
- principle-encode-lessons-in-structure
- principle-exhaust-the-design-space
- principle-experience-first
- principle-fix-root-causes
- principle-foundational-thinking
- principle-guard-the-context-window
- principle-laziness-protocol
- principle-make-operations-idempotent
- principle-migrate-callers-then-delete-legacy-apis
- principle-minimize-reader-load
- principle-model-the-domain
- principle-naming
- principle-never-block-on-the-human
- principle-outcome-oriented-execution
- principle-output-to-user
- principle-prove-it-works
- principle-redesign-from-first-principles
- principle-separate-before-serializing-shared-state
- principle-sequence-verifiable-units
- principle-subtract-before-you-add
- principle-test-behavior-not-implementation
- principle-type-system-discipline
- reflect
- setup-pstack
- show-me-your-work
- swarm
- tdd
- technical-writing
- unslop
- why

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.