pstack

# pstack Rigor over throughput. The point is to write **less** code, and to be able to prove the code you wrote works. Original by Lauren Tan (poteto), MIT, from the Cursor plugin marketplace. This is a port: the principles and general skills are upstream's, the orchestration around them is rewritten for Claude Code and this repo. What changed and why: [ATTRIBUTION.md](./ATTRIBUTION.md). ## How to use it Read the principles below. **Name the ones that shaped a decision, and say which choice each one changed.** A citation with no decision behind it means you did not actually apply it — that is worse than not citing, because it reads as rigor without being rigor. For any principle you actually apply, read its leaf skill in full (`skills/principle-<name>/SKILL.md`). The one-liners here are an index, not the content. ## Principles **Core** - **Laziness Protocol** (`principle-laziness-protocol`). Refactoring, sizing a diff, or tempted to add abstractions, layers, or signal threading. Bias to deletion and the smallest change that solves the problem. - **Foundational Thinking** (`principle-foundational-thinking`). Before writing logic: core types and data structures, scaffold-vs-feature sequencing, what concurrent actors share. - **Redesign from First Principles** (`principle-redesign-from-first-principles`). Integrating a new requirement into an existing design. Redesign as if it had been foundational from day one. - **Subtract Before You Add** (`principle-subtract-before-y...