pstack

What you can ask

• Explain how this subsystem works. Trace the code flow and flag the parts most likely to confuse developers.Copy

  · how skill

• Review this PR for blast radius. Find what could break outside the diff and what still needs verification.
• Rewrite this to sound human. Keep the meaning and tone, but remove AI tells, filler, and generic phrasing.

Skills

26 in the ChatGPT listing

• architectDesign types, interfaces, module boundaries, data flow, and ownership before implementation.
• Blast radiusFind what a code change could break outside the diff by tracing callers, contracts, shared data, external integrations, lifecycle behavior, and downstream consumers.
• broRestate the last message in plain human language, with no jargon.
• howExplain how a codebase, subsystem, feature, API, or technical artifact works by inspecting the available source.
• Principle boundary disciplineApply when wiring validation, error handling, or framework adapters.
• Principle build the leverApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.
• Principle encode lessons in structureApply when you catch yourself writing the same instruction a second time, or notice a recurring correction.
• Principle exhaust the design spaceApply when facing a novel UI interaction or architectural decision with no precedent in the codebase.
• Principle experience firstApply when product, UX, or feature-scope tradeoffs come up.
• Principle fix root causesApply when debugging.
• Principle foundational thinkingApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share.
• Principle make operations idempotentApply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries.
• Principle migrate callers then delete legacy apisApply when introducing a new internal API while old callers still exist.
• Principle minimize reader loadApply when reviewing or shaping code that's hard to trace.
• Principle model the domainApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
• Principle prove it worksApply after completing a task, before declaring done.
• Principle redesign from first principlesApply when integrating a new requirement into an existing design.
• Principle separate before serializing shared stateApply when concurrent actors might write to the same file, branch, key, or state object.
• Principle subtract before you addApply when sequencing an addition, refactor, or rewrite.
• Principle type system disciplineApply when designing types, reviewing a function signature, or writing code in any statically-typed language.
• recallReconstruct recent working context from prior conversations, remembered context, and connected project sources, then give a concise current-state brief.
• teachExplain a codebase, subsystem, feature, change, or technical idea so the user actually understands it.
• Technical writingLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax.
• Typescript best practicesTypeScript best practices.
• unslopCut AI tells from any writing.
• whyInvestigate why a codebase, feature, design decision, threshold, workaround, or architectural choice exists by tracing evidence across the sources available to ChatGPT.