ChHsiching
- 49 skills
- 0 followers
- 2 days ago last updated
- ▌ Pstack Principle Type System Discipline · chhsichingApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.
- ▌ Pstack Principle Subtract Before You Add · chhsichingApply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
- ▌ Pstack Maintain Formal Verification Skill · chhsichingBring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /pstack-maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.
- ▌ Pstack Principle Never Block On The Human · chhsichingApply when tempted to ask 'should I do X?' on reversible work.
- ▌ Pstack Principle Sequence Verifiable Units · chhsichingApply 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.
- ▌ Pstack Principle Make Operations Idempotent · chhsichingApply 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.
- ▌ Pstack Principle Outcome Oriented Execution · chhsichingApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
- ▌ Pstack Principle Test Behavior Not Implementation · chhsichingApply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
- ▌ Pstack Principle Separate Before Serializing Shared State · chhsichingApply 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.
- ▌ Pstack Principle Fix Root Causes · chhsichingApply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
- ▌ Pstack Typescript Best Practices · chhsiching bundleTypeScript best practices. Use when reading or editing any .ts or .tsx file.
- ▌ Pstack Principle Experience First · chhsichingApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- ▌ Pstack Principle Model The Domain · chhsichingApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
- ▌ Pstack Maintain Verification Skill · chhsichingPeriodic 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 /pstack-maintain-verification-skill or "audit the verify skill".
- ▌ Pstack Principle Attack The Premise · chhsichingApply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
- ▌ Pstack Principle Explain The Number · chhsichingApply before you measure, and 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.
- ▌ Pstack Principle Boundary Discipline · chhsichingApply 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.
- ▌ Pstack Principle Minimize Reader Load · chhsichingApply 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.
- ▌ Pstack Principle Foundational Thinking · chhsichingApply 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.
- ▌ Pstack Create Formal Verification Skill · chhsichingGenerate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /pstack-create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
- ▌ Pstack Blast Radius · chhsichingFind 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.
- ▌ Pstack Setup Pstack · chhsichingConfigure which models pstack uses per role and at what reasoning budget. Detects your available models and writes a data file that overrides the defaults. Use for /pstack-setup-pstack, "configure pstack models", "pstack budget", or changing pstack's model choices.
- ▌ Pstack Figure It Out · chhsichingDesign 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. Use for /pstack-figure-it-out or 'figure it out'.
- ▌ Pstack Ketchup Video · chhsichingCatch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text under it. Use for /ketchup-video.
- ▌ Pstack Show Me Your Work · chhsiching bundleKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /pstack-show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
- ▌ Pstack Technical Writing · chhsichingLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /pstack-technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
- ▌ Pstack Benchmark Checklist · chhsichingVet 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.
- ▌ Pstack Principle Prove It Works · chhsichingApply 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.'
- ▌ Pstack Create Verification Skill · chhsiching bundleGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /pstack-create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
- ▌ Pstack Principle Build The Lever · chhsichingApply 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.
- ▌ Pstack Automate Me · chhsichingUse 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 with unslop, optionally pulling fresh evidence from recent sessions.
- ▌ Pstack Interrogate · chhsichingUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Adversaries try to break a change or design, and only findings proven by a run survive.
- ▌ Pstack Make Bot UI · chhsichingUse when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
- ▌ Pstack No Comments · chhsichingSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- ▌ Pstack Poteto Help · chhsiching bundleGuides users through pstack setup, /pstack-poteto-mode, and picking the skill, playbook, or principle for a task. Type /pstack-poteto-help with a question.
- ▌ Pstack Poteto Mode · chhsiching bundlepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /pstack-poteto-mode, or requests to work in this style.
- ▌ Pstack Recall · chhsichingReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
- ▌
- ▌ Pstack Correct · chhsichingFind 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 /pstack-correct.
- ▌ Pstack Ketchup · chhsichingCatch the user up on what changed in this chat since their last message, in plain words and small visuals. List every item waiting on them with what they need to decide it from the reply alone. Use for /pstack-ketchup.
- ▌ Pstack Reflect · chhsiching bundleSpawn three parallel review subagents over the session material, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- ▌ Pstack Sharpen · chhsichingMake a task deeper, not bigger, then rewrite the prompt. Use for /pstack-sharpen.
- ▌ Pstack Architect · chhsiching bundleSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /pstack-architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- ▌ Pstack Statechart · chhsiching bundleCheck a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use for /statechart, or to show a bug as a path through states.
- ▌ Pstack How · chhsichingUse 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.
- ▌ Pstack Arena · chhsichingSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /pstack-arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- ▌ Pstack Swarm · chhsichingFan out N parallel workers, drain them, and return one report. Use for /pstack-swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
- ▌ Pstack Teach · chhsichingExplain a body of work plainly so a person actually understands it. Runs the `pstack-how` and `pstack-why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
- ▌ Blcu Ppt · chhsiching bundleGenerate BLCU-template presentations from user material — use when the user supplies documents/images and asks for a presentation (组会汇报) on the BLCU template, or asks to revise or extend deliverables this skill produced (outline.md / deck.json / 演讲稿.md / out/ 产物).