@giljae/opencode-pstack 0.0.0-stage → 0.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/NOTICE +10 -0
- package/README.md +176 -2
- package/package.json +42 -4
- package/src/agents.ts +110 -0
- package/src/commands.ts +37 -0
- package/src/content.ts +119 -0
- package/src/host.ts +59 -0
- package/src/index.ts +21 -0
- package/src/install.ts +22 -0
- package/src/models.ts +112 -0
- package/src/pstack-setup.ts +111 -0
- package/src/setup.ts +42 -0
- package/src/skills.ts +24 -0
- package/vendor/pstack/LICENSE.upstream +21 -0
- package/vendor/pstack/README.upstream.md +290 -0
- package/vendor/pstack/UPSTREAM.json +545 -0
- package/vendor/pstack/agents/comment-sicko.md +32 -0
- package/vendor/pstack/agents/poteto-agent.md +10 -0
- package/vendor/pstack/docs/guide/01-setup.md +66 -0
- package/vendor/pstack/docs/guide/02-poteto-mode.md +139 -0
- package/vendor/pstack/docs/guide/03-understand.md +79 -0
- package/vendor/pstack/docs/guide/04-design.md +127 -0
- package/vendor/pstack/docs/guide/05-build-and-clean.md +83 -0
- package/vendor/pstack/docs/guide/06-verify-and-ship.md +162 -0
- package/vendor/pstack/docs/guide/07-overnight.md +122 -0
- package/vendor/pstack/docs/guide/08-principles.md +72 -0
- package/vendor/pstack/docs/guide/09-make-it-yours.md +100 -0
- package/vendor/pstack/docs/guide/10-recipes-and-pitfalls.md +182 -0
- package/vendor/pstack/docs/guide/README.md +38 -0
- package/vendor/pstack/docs/guide/images/design.jpg +0 -0
- package/vendor/pstack/docs/guide/images/overnight.jpg +0 -0
- package/vendor/pstack/docs/guide/images/recipes.jpg +0 -0
- package/vendor/pstack/docs/guide/images/router.jpg +0 -0
- package/vendor/pstack/docs/guide/images/understanding.jpg +0 -0
- package/vendor/pstack/docs/guide/images/verification.jpg +0 -0
- package/vendor/pstack/docs/harness/claude-code.md +68 -0
- package/vendor/pstack/skills/architect/SKILL.md +11 -0
- package/vendor/pstack/skills/arena/SKILL.md +48 -0
- package/vendor/pstack/skills/automate-me/SKILL.md +104 -0
- package/vendor/pstack/skills/benchmark-checklist/SKILL.md +39 -0
- package/vendor/pstack/skills/blast-radius/SKILL.md +50 -0
- package/vendor/pstack/skills/bro/SKILL.md +7 -0
- package/vendor/pstack/skills/correct/SKILL.md +32 -0
- package/vendor/pstack/skills/create-formal-verification-skill/SKILL.md +43 -0
- package/vendor/pstack/skills/create-verification-skill/SKILL.md +44 -0
- package/vendor/pstack/skills/create-verification-skill/references/feature-map-example/README.md +47 -0
- package/vendor/pstack/skills/create-verification-skill/references/feature-map-example/create-note.md +39 -0
- package/vendor/pstack/skills/create-verification-skill/references/feature-map-example/search.md +45 -0
- package/vendor/pstack/skills/figure-it-out/SKILL.md +52 -0
- package/vendor/pstack/skills/how/SKILL.md +21 -0
- package/vendor/pstack/skills/in-your-own-words/SKILL.md +7 -0
- package/vendor/pstack/skills/interrogate/SKILL.md +31 -0
- package/vendor/pstack/skills/ketchup/SKILL.md +43 -0
- package/vendor/pstack/skills/ketchup-video/SKILL.md +29 -0
- package/vendor/pstack/skills/maintain-formal-verification-skill/SKILL.md +58 -0
- package/vendor/pstack/skills/maintain-verification-skill/SKILL.md +39 -0
- package/vendor/pstack/skills/make-bot-ui/SKILL.md +115 -0
- package/vendor/pstack/skills/no-comments/SKILL.md +24 -0
- package/vendor/pstack/skills/poteto-help/SKILL.md +162 -0
- package/vendor/pstack/skills/poteto-help/references/prompting.md +51 -0
- package/vendor/pstack/skills/poteto-help/references/recipes.md +51 -0
- package/vendor/pstack/skills/poteto-mode/SKILL.md +110 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/authoring-a-skill.md +12 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/autonomous-run.md +13 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/autopilot-full.md +25 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/autopilot-stack.md +8 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/babysit.md +10 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/bug-fix.md +15 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/eval.md +25 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/feature.md +21 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/hillclimb.md +21 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/investigation.md +14 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/multi-phase-plan.md +11 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/opening-a-pr.md +9 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/pause-safely.md +10 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/perf-issue.md +25 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/prototype.md +14 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/refactoring.md +16 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/runtime-forensics.md +11 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/session-pickup.md +11 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/shipping.md +12 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/trace-forensics.md +14 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/visual-parity.md +11 -0
- package/vendor/pstack/skills/poteto-mode/playbooks/worktree-cleanup.md +12 -0
- package/vendor/pstack/skills/poteto-mode/references/bugbot-triage.md +142 -0
- package/vendor/pstack/skills/poteto-mode/scripts/bootstrap.ts +62 -0
- package/vendor/pstack/skills/poteto-mode/scripts/bun.lock +67 -0
- package/vendor/pstack/skills/poteto-mode/scripts/package.json +16 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/cli.test.ts +224 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/cli.ts +223 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/fakes.test-helper.ts +129 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/github.test.ts +498 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/github.ts +726 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/policy.test.ts +482 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/policy.ts +842 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/render.ts +169 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/tsconfig.json +13 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/types.compile.ts +93 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/types.ts +414 -0
- package/vendor/pstack/skills/poteto-mode/scripts/watch-pr/watch-pr +6 -0
- package/vendor/pstack/skills/poteto-mode/scripts/worktree-audit.sh +134 -0
- package/vendor/pstack/skills/poteto-mode/worker.md +11 -0
- package/vendor/pstack/skills/principle-attack-the-premise/SKILL.md +15 -0
- package/vendor/pstack/skills/principle-boundary-discipline/SKILL.md +11 -0
- package/vendor/pstack/skills/principle-build-the-lever/SKILL.md +14 -0
- package/vendor/pstack/skills/principle-encode-lessons-in-structure/SKILL.md +11 -0
- package/vendor/pstack/skills/principle-exhaust-the-design-space/SKILL.md +9 -0
- package/vendor/pstack/skills/principle-experience-first/SKILL.md +19 -0
- package/vendor/pstack/skills/principle-explain-the-number/SKILL.md +14 -0
- package/vendor/pstack/skills/principle-fix-root-causes/SKILL.md +14 -0
- package/vendor/pstack/skills/principle-foundational-thinking/SKILL.md +13 -0
- package/vendor/pstack/skills/principle-guard-the-context-window/SKILL.md +12 -0
- package/vendor/pstack/skills/principle-laziness-protocol/SKILL.md +10 -0
- package/vendor/pstack/skills/principle-make-operations-idempotent/SKILL.md +15 -0
- package/vendor/pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md +14 -0
- package/vendor/pstack/skills/principle-minimize-reader-load/SKILL.md +15 -0
- package/vendor/pstack/skills/principle-model-the-domain/SKILL.md +15 -0
- package/vendor/pstack/skills/principle-never-block-on-the-human/SKILL.md +15 -0
- package/vendor/pstack/skills/principle-outcome-oriented-execution/SKILL.md +21 -0
- package/vendor/pstack/skills/principle-prove-it-works/SKILL.md +11 -0
- package/vendor/pstack/skills/principle-redesign-from-first-principles/SKILL.md +16 -0
- package/vendor/pstack/skills/principle-separate-before-serializing-shared-state/SKILL.md +11 -0
- package/vendor/pstack/skills/principle-sequence-verifiable-units/SKILL.md +13 -0
- package/vendor/pstack/skills/principle-subtract-before-you-add/SKILL.md +18 -0
- package/vendor/pstack/skills/principle-test-behavior-not-implementation/SKILL.md +16 -0
- package/vendor/pstack/skills/principle-type-system-discipline/SKILL.md +15 -0
- package/vendor/pstack/skills/recall/SKILL.md +35 -0
- package/vendor/pstack/skills/reflect/SKILL.md +17 -0
- package/vendor/pstack/skills/setup-pstack/SKILL.md +78 -0
- package/vendor/pstack/skills/sharpen/SKILL.md +16 -0
- package/vendor/pstack/skills/show-me-your-work/SKILL.md +82 -0
- package/vendor/pstack/skills/show-me-your-work/references/decision-log-template.tsv +1 -0
- package/vendor/pstack/skills/show-me-your-work/scripts/log.sh +42 -0
- package/vendor/pstack/skills/statechart/SKILL.md +82 -0
- package/vendor/pstack/skills/statechart/references/render.md +93 -0
- package/vendor/pstack/skills/statechart/scripts/backends/cfg.ts +33 -0
- package/vendor/pstack/skills/statechart/scripts/backends/mermaid.ts +249 -0
- package/vendor/pstack/skills/statechart/scripts/backends/plain-text.ts +72 -0
- package/vendor/pstack/skills/statechart/scripts/backends/report.ts +177 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/config.ts +276 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/dot.ts +74 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/marks.ts +93 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/messages.ts +52 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/spec.ts +114 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/trace.ts +24 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/value.ts +166 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/verdict.ts +40 -0
- package/vendor/pstack/skills/statechart/scripts/frontends/view.ts +119 -0
- package/vendor/pstack/skills/statechart/scripts/ir.ts +547 -0
- package/vendor/pstack/skills/statechart/scripts/package.json +11 -0
- package/vendor/pstack/skills/statechart/scripts/passes/annotate.ts +128 -0
- package/vendor/pstack/skills/statechart/scripts/passes/label.ts +269 -0
- package/vendor/pstack/skills/statechart/scripts/passes/lift.ts +85 -0
- package/vendor/pstack/skills/statechart/scripts/passes/loop-check.ts +68 -0
- package/vendor/pstack/skills/statechart/scripts/passes/paths.ts +60 -0
- package/vendor/pstack/skills/statechart/scripts/passes/reach.ts +135 -0
- package/vendor/pstack/skills/statechart/scripts/passes/region-check.ts +97 -0
- package/vendor/pstack/skills/statechart/scripts/passes/regions.ts +295 -0
- package/vendor/pstack/skills/statechart/scripts/pipeline.ts +76 -0
- package/vendor/pstack/skills/statechart/scripts/run.ts +506 -0
- package/vendor/pstack/skills/statechart/scripts/statechart +29 -0
- package/vendor/pstack/skills/statechart/scripts/statechart.ts +164 -0
- package/vendor/pstack/skills/statechart/scripts/test/ConfigOracle.java +63 -0
- package/vendor/pstack/skills/statechart/scripts/test/chart.test.ts +1253 -0
- package/vendor/pstack/skills/statechart/scripts/test/charts/Braces.mmd +7 -0
- package/vendor/pstack/skills/statechart/scripts/test/charts/Escapes.mmd +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/charts/Phases.mmd +29 -0
- package/vendor/pstack/skills/statechart/scripts/test/cli.test.ts +1315 -0
- package/vendor/pstack/skills/statechart/scripts/test/config-fuzz.test.ts +263 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/Counter.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/Counter.tla +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/chart.mmd +9 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/graph.dot +16 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/report.md +7 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Counter/verdict-1.out +49 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/ChartRun.out +60 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/CounterAction.cfg +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/CounterAction.tla +22 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/chart.mmd +26 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/graph.dot +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/report.md +20 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/verdict-2.out +82 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterAction/verdict-3.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/CounterDeadlock.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/CounterDeadlock.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/chart.mmd +22 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/graph.dot +16 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/report.md +17 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterDeadlock/verdict-2.out +77 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/ChartRun.out +69 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/CounterFan.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/CounterFan.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/chart.mmd +85 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/graph.dot +70 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/report.md +12 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/verdict-1.out +67 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterFan/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/ChartRun.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/ChartRun.out +85 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/CounterGuard.cfg +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/CounterGuard.tla +13 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/chart.mmd +5 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/graph.dot +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/report.md +31 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/verdict-1.out +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterGuard/verdict-2.out +77 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/ChartRun.out +55 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/CounterInitPast.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/CounterInitPast.tla +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/chart.mmd +12 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/graph.dot +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/report.md +12 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/verdict-1.out +33 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPast/verdict-2.out +54 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/ChartRun.out +54 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/CounterInitPastHolds.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/CounterInitPastHolds.tla +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/chart.mmd +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/graph.dot +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/report.md +7 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInitPastHolds/verdict-1.out +46 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/CounterInstance.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/CounterInstance.tla +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/CounterSteps.tla +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/chart.mmd +17 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/graph.dot +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/report.md +14 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/sany.out +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterInstance/verdict-1.out +78 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/CounterJump.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/CounterJump.tla +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/chart.mmd +26 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/graph.dot +22 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/report.md +12 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/verdict-1.out +58 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterJump/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/CounterLoop.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/CounterLoop.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/chart.mmd +17 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/graph.dot +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/report.md +14 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterLoop/verdict-1.out +76 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/CounterOrder.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/CounterOrder.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/chart.mmd +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/graph.dot +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/report.md +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterOrder/verdict-2.out +67 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/ChartRun.out +62 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/CounterRules.cfg +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/CounterRules.tla +24 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/Moves.tla +5 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/chart.mmd +22 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/graph.dot +10 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/report.md +23 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/sany.out +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-1.out +58 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-2.out +66 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-3.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-3.out +74 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterRules/verdict-4.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/ChartRun.out +58 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/CounterStart.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/CounterStart.tla +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/chart.mmd +18 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/graph.dot +13 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/report.md +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/verdict-1.out +33 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStart/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/CounterStop.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/CounterStop.tla +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/chart.mmd +7 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/graph.dot +13 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/report.md +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterStop/verdict-1.out +49 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/ChartRun.out +61 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/CounterTie.cfg +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/CounterTie.tla +14 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/chart.mmd +30 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/graph.dot +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/report.md +27 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-2.out +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-3.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-3.out +87 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTie/verdict-4.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/ChartRun.out +60 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/CounterTieInGraph.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/CounterTieInGraph.tla +12 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/chart.mmd +23 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/graph.dot +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/report.md +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterTieInGraph/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/ChartRun.out +61 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/CounterView.cfg +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/CounterView.tla +14 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/chart.mmd +23 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/graph.dot +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/report.md +27 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-2.out +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-3.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-3.out +87 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/verdict-4.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/CounterView/view.mjs +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/DieHard.cfg +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/DieHard.tla +38 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/chart.mmd +92 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/graph.dot +126 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/report.md +17 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/verdict-1.out +91 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/DieHard/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/ChartRun.out +61 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/FirstRule.cfg +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/FirstRule.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/chart.mmd +22 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/graph.dot +16 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/report.md +25 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-2.out +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-3.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-3.out +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-4.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/FirstRule/verdict-4.out +77 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/HiddenClock.cfg +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/HiddenClock.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/chart.mmd +13 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/graph.dot +12 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/report.md +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/HiddenClock/verdict-1.out +72 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/Login.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/Login.tla +62 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/chart.mmd +28 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/graph.dot +40 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/report.md +7 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/verdict-1.out +47 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Login/view.mjs +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/LoginGuarded.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/LoginGuarded.tla +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/chart.mmd +28 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/graph.dot +37 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/report.md +8 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/verdict-1.out +47 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginGuarded/view.mjs +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/ChartRun.out +60 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/LoginParallel.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/LoginParallel.tla +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/chart.mmd +44 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/graph.dot +58 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/report.md +17 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/verdict-1.out +83 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/LoginParallel/view.mjs +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/ChartRun.out +60 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/MediaPlayer.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/MediaPlayer.tla +103 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/chart.mmd +43 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/graph.dot +93 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/report.md +14 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/verdict-1.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/verdict-2.out +72 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayer/view.mjs +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/MediaPlayerFixed.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/MediaPlayerFixed.tla +100 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/chart.mmd +31 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/graph.dot +85 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/report.md +9 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/verdict-1.out +47 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerFixed/view.mjs +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/MediaPlayer.tla +103 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/MediaPlayerProps.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/MediaPlayerProps.tla +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/chart.mmd +42 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/graph.dot +93 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/report.md +19 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-1.out +61 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-2.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-3.out +61 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-4.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-4.out +66 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-5.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-5.out +58 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/verdict-6.out +49 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/MediaPlayerProps/view.mjs +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/PickWorker.cfg +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/PickWorker.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/chart.mmd +5 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/graph.dot +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/report.md +7 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/sany.out +5 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/PickWorker/verdict-1.out +70 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/ChartRun.out +61 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/Shadow.cfg +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/Shadow.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/ShadowLib.tla +6 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/ShadowSub.tla +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/chart.mmd +9 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/graph.dot +16 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/report.md +8 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/sany.out +4 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/Shadow/verdict-1.out +65 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/ChartRun.out +59 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/SpacedNames.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/SpacedNames.tla +9 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/chart.mmd +23 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/graph.dot +17 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/report.md +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/verdict-1.out +65 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/SpacedNames/verdict-2.out +75 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/ChartRun.out +69 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/TwoPhase.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/TwoPhase.tla +75 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/chart.mmd +60 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/graph.dot +297 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/report.md +20 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/verdict-1.out +95 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/verdict-2.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhase/view.mjs +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/ChartRun.out +57 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/TwoPhaseFixed.cfg +3 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/TwoPhaseFixed.tla +75 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/chart.mmd +37 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/graph.dot +223 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/report.md +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/sany.out +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/verdict-1.out +47 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TwoPhaseFixed/view.mjs +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/ChartRun.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/ChartRun.out +75 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/TypeGuard.cfg +5 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/TypeGuard.tla +11 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/chart.mmd +18 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/graph.dot +14 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/report.md +29 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/verdict-1.out +64 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/TypeGuard/verdict-2.out +75 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/ChartRun.out +58 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/UserNoDeadlock.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/UserNoDeadlock.tla +8 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/chart.mmd +22 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/graph.dot +16 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/report.md +15 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/verdict-1.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/verdict-1.out +56 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/verdict-2.exit +1 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus/UserNoDeadlock/verdict-2.out +77 -0
- package/vendor/pstack/skills/statechart/scripts/test/corpus.test.ts +441 -0
- package/vendor/pstack/skills/statechart/scripts/test/differential.test.ts +565 -0
- package/vendor/pstack/skills/statechart/scripts/test/drawn.ts +20 -0
- package/vendor/pstack/skills/statechart/scripts/test/grid/Grid.cfg +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/grid/Grid.tla +9 -0
- package/vendor/pstack/skills/statechart/scripts/test/grid/sany.out +2 -0
- package/vendor/pstack/skills/statechart/scripts/test/java.ts +63 -0
- package/vendor/pstack/skills/statechart/scripts/test/labels.ts +648 -0
- package/vendor/pstack/skills/statechart/scripts/test/messages.test.ts +212 -0
- package/vendor/pstack/skills/statechart/scripts/test/pipeline.test.ts +270 -0
- package/vendor/pstack/skills/statechart/scripts/test/plain-tlc.test.ts +255 -0
- package/vendor/pstack/skills/statechart/scripts/test/render.test.ts +145 -0
- package/vendor/pstack/skills/statechart/scripts/test/tlc-out.test.ts +90 -0
- package/vendor/pstack/skills/statechart/scripts/test/tlc.ts +158 -0
- package/vendor/pstack/skills/statechart/scripts/tsconfig.json +11 -0
- package/vendor/pstack/skills/statechart/scripts/worker.ts +35 -0
- package/vendor/pstack/skills/swarm/SKILL.md +41 -0
- package/vendor/pstack/skills/tdd/SKILL.md +42 -0
- package/vendor/pstack/skills/teach/SKILL.md +21 -0
- package/vendor/pstack/skills/technical-writing/SKILL.md +70 -0
- package/vendor/pstack/skills/typescript-best-practices/SKILL.md +31 -0
- package/vendor/pstack/skills/typescript-best-practices/references/patterns.md +328 -0
- package/vendor/pstack/skills/unslop/SKILL.md +40 -0
- package/vendor/pstack/skills/why/SKILL.md +9 -0
- package/vendor/pstack/upstream-plugin.json +21 -0
|
@@ -0,0 +1,182 @@
|
|
|
1
|
+
# Recipes and pitfalls
|
|
2
|
+
|
|
3
|
+
Prompts worth copying, then the mistakes everyone makes once. Swap in your own paths and finish conditions. The recipes are deliberately informal. That's how they get typed in practice, and the skills read intent fine.
|
|
4
|
+
|
|
5
|
+

|
|
6
|
+
|
|
7
|
+
## Understand an unfamiliar subsystem
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
use /how first to understand how this initialization works. then use /why to figure out why it broke recently.
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
Mechanics first, history second. Each skill's report tells you which sources it searched, so you know what the answer is grounded in.
|
|
14
|
+
|
|
15
|
+
## Restate a noisy report before touching code
|
|
16
|
+
|
|
17
|
+
```text
|
|
18
|
+
/poteto-mode read this thread. restate the underlying issue in your own words, in plain english. don't change any code yet.
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
A misreading shows up in the restatement, where it costs one message to correct. Keep your own theory to yourself until the agent has stated its own. `/in-your-own-words` asks for the restatement alone, with no playbook.
|
|
22
|
+
|
|
23
|
+
## Sharpen a prompt before you send it
|
|
24
|
+
|
|
25
|
+
```text
|
|
26
|
+
/sharpen write the onboarding doc for the new billing service.
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
The agent names what an expert would do that you didn't ask for, the raw material they'd start from, their methods and tools, and an outside check that the result is right. It hands back your prompt rewritten to ask for that and doesn't do the task. Send the rewrite when it reads right.
|
|
30
|
+
|
|
31
|
+
## Prototype before you pick
|
|
32
|
+
|
|
33
|
+
```text
|
|
34
|
+
/poteto-mode prototype a few options for the settings layout. put them behind a switcher and send me screenshots of each.
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
You pick from things that run, not from descriptions. The agent answers its own layout and timing questions along the way.
|
|
38
|
+
|
|
39
|
+
## Turn a settled design into a plan
|
|
40
|
+
|
|
41
|
+
```text
|
|
42
|
+
/poteto-mode turn this design into a plan. small verifiable PRs, each with its own proof.
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
Ask only after the design settles. The plan is the deliverable, and it names the playbook that will execute it.
|
|
46
|
+
|
|
47
|
+
## Get a second opinion on a design
|
|
48
|
+
|
|
49
|
+
```text
|
|
50
|
+
ask /arena for a second opinion on this thread and our approach
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
Your current design becomes one candidate among several, and the synthesis tells you whether the panel found something better or confirmed what you had. It costs little next to a design that is expensive to reverse.
|
|
54
|
+
|
|
55
|
+
## Check independent slices in parallel
|
|
56
|
+
|
|
57
|
+
```text
|
|
58
|
+
/swarm check every package under packages/ against its check.sh. one worker per package. one report.
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
Each worker owns one package. The parent waits for every slice and returns one `PASS`, `ISSUES`, or `BLOCKED` report instead of raw worker dumps.
|
|
62
|
+
|
|
63
|
+
## Review a branch skeptically
|
|
64
|
+
|
|
65
|
+
```text
|
|
66
|
+
/interrogate the whole branch, but skeptically. don't change anything yet. no nitpicks unless it's an actual bug or regression in behavior.
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
The qualifiers do real work. "don't change anything yet" keeps it read-only, and the nitpick rule pre-filters the noise so the verified findings are worth your time.
|
|
70
|
+
|
|
71
|
+
## Fix a bug through a failing test
|
|
72
|
+
|
|
73
|
+
```text
|
|
74
|
+
/poteto-mode repro the duplicate write first. if there's a cheap test path, /tdd it. then fix and rerun.
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
"if there's a cheap test path" matters. Forcing a test through brittle mocks proves less than running the real command, and the playbook is allowed to say so.
|
|
78
|
+
|
|
79
|
+
## Repro and fix a report with proof
|
|
80
|
+
|
|
81
|
+
```text
|
|
82
|
+
/poteto-mode repro this with /verify-<app>. if it repros on main, fix it and show me a video as proof.
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
"if it repros on main" lets the run stop early when the bug is already gone. The video lets you check the fix before you read the diff.
|
|
86
|
+
|
|
87
|
+
## Prove a property tests rarely reach
|
|
88
|
+
|
|
89
|
+
```text
|
|
90
|
+
/create-formal-verification-skill the retry queue. a message must never be delivered twice.
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
You get one property checked in every case within a stated scope, a counterexample in your code's terms if the code already breaks it, and a project skill the next agent runs on any change to that code.
|
|
94
|
+
|
|
95
|
+
## Vet a number before you post it
|
|
96
|
+
|
|
97
|
+
```text
|
|
98
|
+
/benchmark-checklist vet this 40% speedup before it goes in the pr description
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
You get faster, slower, no measurable difference, or inconclusive, with the run count, the range, and what limits the number.
|
|
102
|
+
|
|
103
|
+
## Stop correcting the same mistake
|
|
104
|
+
|
|
105
|
+
```text
|
|
106
|
+
/correct agents keep adding new config flags without registering them in the schema
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
The fix lands in the repo as architecture, a type, a lint, or a test, so the next agent can't make the mistake.
|
|
110
|
+
|
|
111
|
+
## Ask how without starting the work
|
|
112
|
+
|
|
113
|
+
```text
|
|
114
|
+
/poteto-help how do i get poteto-mode to stay on every turn?
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
You get an answer, a prompt to send, and a link to the source. Nothing runs until you send that prompt.
|
|
118
|
+
|
|
119
|
+
## Keep a run honest while you're away
|
|
120
|
+
|
|
121
|
+
```text
|
|
122
|
+
im going to bed, keep going autonomously until every fixture passes. do not stop. keep a decision log i can audit in the morning.
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
The full contract is on the [overnight page](./07-overnight.md). The short form works once the task and finish condition are already in the conversation.
|
|
126
|
+
|
|
127
|
+
## Redirect a drifting run
|
|
128
|
+
|
|
129
|
+
Steering prompts are one line:
|
|
130
|
+
|
|
131
|
+
```text
|
|
132
|
+
i said the goal is to repro. i did not ask for a fix yet.
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
```text
|
|
136
|
+
apply prove it works. show me the real output, not the build log.
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
```text
|
|
140
|
+
/unslop that, no emdashes
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
You rarely need more words. You need the right name, and [the principles page](./08-principles.md) is the vocabulary.
|
|
144
|
+
|
|
145
|
+
## Get the reply in plain words
|
|
146
|
+
|
|
147
|
+
```text
|
|
148
|
+
/bro
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
That's the whole prompt. [`/bro`](../../skills/bro/SKILL.md) restates the last message like one human talking to another, no jargon, shorter. Use it when a reply is technically thorough and you still don't know what it said.
|
|
152
|
+
|
|
153
|
+
## Catch up on a chat you left running
|
|
154
|
+
|
|
155
|
+
```text
|
|
156
|
+
/ketchup
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
[`/ketchup`](../../skills/ketchup/SKILL.md) tells you in plain words what changed since your last message, then lists each call waiting on you with its pick, evidence, and risk. It changes nothing while it reports.
|
|
160
|
+
|
|
161
|
+
To watch the catch-up instead, run [`/ketchup-video`](../../skills/ketchup-video/SKILL.md). It shows what happened in a short subtitled video of slides, and lists the calls waiting on you as text under it.
|
|
162
|
+
|
|
163
|
+
## The pitfalls
|
|
164
|
+
|
|
165
|
+
- **Enumerating skills in the prompt.** "use /architect then /arena then /interrogate" reorders steps the playbook already sequences. State the goal and constraints. Name a skill only to override a default.
|
|
166
|
+
- **A vague finish condition.** "make it better" gives `/loop` nothing to check. Give a command or artifact that can pass or fail.
|
|
167
|
+
- **Leading with your theory of the cause.** The agent searches wherever you pointed. Ask it to restate the problem first, then share your hunch.
|
|
168
|
+
- **Taking the first design.** One attempt locks in the first shape the model thought of. Ask for prototypes or `/architect` and pick from evidence.
|
|
169
|
+
- **Polishing an abstract plan.** Adversarial review of a plan with no code behind it invents risks that will never happen. Settle the open questions with prototypes, then review what got built.
|
|
170
|
+
- **Parallel agents in one worktree.** They overwrite each other, and nobody can tell which agent changed what. Run them as cloud agents, or say "own worktree per attempt".
|
|
171
|
+
- **Looping before you trust the loop.** A loop that can't verify its own work only makes unchecked work faster. Get the verification skill working first.
|
|
172
|
+
- **Trusting an unvetted number.** A warm cache or a skipped code path can fake a speedup. Run `/benchmark-checklist` before the number goes anywhere.
|
|
173
|
+
- **Correcting the same mistake by hand.** A correction in chat helps one run. `/correct` fixes the repo so no later run repeats it.
|
|
174
|
+
- **Using `/arena` for coverage.** `/arena` repeats one design or code brief, then picks a base and grafts the best parts. `/swarm` partitions slices or declared race arms and aggregates one report.
|
|
175
|
+
- **Accepting every review comment.** Bots and humans both file real catches and noise in one list. `/interrogate` keeps only the findings a rerun proves and lists what it dropped and why, and you can override either way.
|
|
176
|
+
- **Treating `auto` as a model slug.** `auto` and `inherit-parent` mean "omit the model field so the subagent inherits the parent chat model." [Setup](./01-setup.md) covers the roles.
|
|
177
|
+
- **Reporting success off a green build.** A build proves it compiles. Ask for the real command, flow, stored value, or profile, and expect the evidence in the reply.
|
|
178
|
+
- **Writing a `SKILL.md` freehand.** Route it through the [Authoring or modifying a skill playbook](../../skills/poteto-mode/playbooks/authoring-a-skill.md) so validation and review happen.
|
|
179
|
+
|
|
180
|
+
That's the guide. If you skipped ahead, go back to [setup](./01-setup.md) and run one real task. The habits stick from use, not from reading.
|
|
181
|
+
|
|
182
|
+
Back to the [guide index](./README.md).
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# The pstack guide
|
|
2
|
+
|
|
3
|
+
pstack works best when you stop micromanaging the agent. You describe what you want and how you'll know it's done. `/poteto-mode` picks the playbook, runs the other skills as the steps need them, and shows you the evidence. This guide teaches that habit with realistic prompts.
|
|
4
|
+
|
|
5
|
+
Here's what you'll learn:
|
|
6
|
+
|
|
7
|
+
1. [Set up pstack](./01-setup.md). Install the plugin and pick your models.
|
|
8
|
+
2. [Route work through `/poteto-mode`](./02-poteto-mode.md). Give it a goal and watch it pick a playbook.
|
|
9
|
+
3. [Understand the code](./03-understand.md). A read-only investigation, then `/how`, `/why`, `/teach`, and `/recall` before you edit anything.
|
|
10
|
+
4. [Design the change](./04-design.md). `/architect`, `/arena`, `/swarm`, `/interrogate`, prototypes, and plans before code locks in a shape.
|
|
11
|
+
5. [Build and clean the change](./05-build-and-clean.md). The build playbooks, `/tdd`, `/unslop`, and `/no-comments`.
|
|
12
|
+
6. [Verify and ship](./06-verify-and-ship.md). Prove behavior on the real app, formally verify what tests rarely reach, vet numbers with `/benchmark-checklist`, then open a focused PR and drive it to merged.
|
|
13
|
+
7. [Run work while you sleep](./07-overnight.md). Trust before loops, an overnight contract, a decision log you can audit, and Projects and automations that scale past one agent.
|
|
14
|
+
8. [Steer with principle names](./08-principles.md). The 24 names that redirect an agent mid-task.
|
|
15
|
+
9. [Make it yours](./09-make-it-yours.md). Your own mode, `/correct` for repeated mistakes, and how to test a skill change.
|
|
16
|
+
10. [Recipes and pitfalls](./10-recipes-and-pitfalls.md). Prompts to copy and mistakes to skip.
|
|
17
|
+
|
|
18
|
+
Read the pages in order the first time. After that, each page stands alone.
|
|
19
|
+
|
|
20
|
+
When you're stuck, or can't tell which skill fits, type [`/poteto-help`](../../skills/poteto-help/SKILL.md) with your question:
|
|
21
|
+
|
|
22
|
+
```text
|
|
23
|
+
/poteto-help which skill should i use to review this branch?
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
It answers, hands you a prompt to send, and links the skill or guide page the answer came from. It doesn't start the work, because a pstack run spends real tokens, so you send the prompt when you're ready. It runs only when you type it.
|
|
27
|
+
|
|
28
|
+
## If you only remember one thing
|
|
29
|
+
|
|
30
|
+
Give the agent a goal and a way to check it, in your own words:
|
|
31
|
+
|
|
32
|
+
```text
|
|
33
|
+
/poteto-mode the export writes duplicate rows when a retry lands mid-run. repro first, then fix and verify.
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
You don't need to name a playbook or list skills. "repro first" and a checkable outcome are all the routing signal `/poteto-mode` needs. It matches the Bug fix playbook, copies the steps into a todo list, and calls the right skills as each step fires.
|
|
37
|
+
|
|
38
|
+
Next: [Set up pstack](./01-setup.md).
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1,68 @@
|
|
|
1
|
+
# pstack in Claude Code
|
|
2
|
+
|
|
3
|
+
pstack skills use Cursor names. In Claude Code, read this file once per session, then map each Cursor name in a skill with the tables below. `<pstack>` means the folder that holds `skills/` and `docs/`. If a Cursor field has no row, drop it and say so. Never pass a field or value the tool schema rejects.
|
|
4
|
+
|
|
5
|
+
## Tools
|
|
6
|
+
|
|
7
|
+
| Cursor | Claude Code |
|
|
8
|
+
| --- | --- |
|
|
9
|
+
| `Task` | `Agent` |
|
|
10
|
+
| `AskQuestion` | `AskUserQuestion`. In `-p` mode it is absent, so ask in plain text. |
|
|
11
|
+
| Open a todolist, or copy steps into the todolist tool | Use `TodoWrite` if the session offers it. Otherwise keep the list in your reply and update it at each phase. |
|
|
12
|
+
| Run another pstack skill (`/name` or "the **name** skill") | `Read` `<pstack>/skills/<name>/SKILL.md` and follow it. The `Skill` tool refuses most pstack skills. When you tell the user to type it, write `/pstack:<name>`. |
|
|
13
|
+
| `Grep`, `Glob` | `Bash` with `rg` when the session has no `Grep` or `Glob`. |
|
|
14
|
+
|
|
15
|
+
## Subagent fields
|
|
16
|
+
|
|
17
|
+
| Cursor | Claude Code |
|
|
18
|
+
| --- | --- |
|
|
19
|
+
| `subagent_type: generalPurpose` | `subagent_type: "general-purpose"` |
|
|
20
|
+
| `poteto-agent`, `comment-sicko` | `pstack:poteto-agent`, `pstack:comment-sicko` |
|
|
21
|
+
| The `model:` line in `poteto-agent`'s file | It holds a Cursor slug. Pass `model` and `effort` on every `Agent` call that spawns `pstack:poteto-agent`, mapped with the Models table, so that slug never reaches the API. |
|
|
22
|
+
| `readonly: true` | `subagent_type: "Explore"`. It keeps `Bash`, so the brief also says "do not edit files", and you check `git status` afterward. |
|
|
23
|
+
| `readonly: false` | `general-purpose`. It keeps the session's MCP servers. |
|
|
24
|
+
| `environment: "cloud"` | `isolation: "worktree"`. Name the branch or commit the worker checks out. |
|
|
25
|
+
| `environment: "local"` | Omit. |
|
|
26
|
+
| `cloud_base_branch: <b>` | Tell the worker to check out `<b>` first. |
|
|
27
|
+
| `run_in_background: true` | Omit. Subagents run in the background by default and notify you when they finish. |
|
|
28
|
+
| `resume` | Spawn a new agent and paste the earlier result into its brief. |
|
|
29
|
+
| `file_attachments` | List the paths in the brief. |
|
|
30
|
+
|
|
31
|
+
## Models
|
|
32
|
+
|
|
33
|
+
| Cursor | Claude Code |
|
|
34
|
+
| --- | --- |
|
|
35
|
+
| `claude-<family>-<version>-<effort>[-fast]`, such as `claude-opus-5-5-xhigh` | `model: "opus"` and `effort: "xhigh"`. `model` takes only `opus`, `sonnet`, `haiku`, `fable`. Drop `-fast`. |
|
|
36
|
+
| A `gemini-*` or other non-Claude slug | Omit `model` so the agent runs on the session model, and say so. |
|
|
37
|
+
| `auto` or `inherit-parent` | Omit `model`. |
|
|
38
|
+
| The `pstack-models.mdc` rule, `~/.cursor/rules/pstack-models.mdc` | `~/.claude/rules/pstack-models.md`. Claude Code loads it into every new session, so its role lines are already in context. If they are not, read the file. If the file or the role's line is missing, use the skill's default slug. |
|
|
39
|
+
| A role value `<model> <effort>`, such as `opus high` | `model: "opus"` and `effort: "high"`. |
|
|
40
|
+
|
|
41
|
+
## setup-pstack
|
|
42
|
+
|
|
43
|
+
Claude Code loads every `.md` file in `~/.claude/rules/` into each new session, so `setup-pstack` writes its rule there. Follow its steps with these changes:
|
|
44
|
+
|
|
45
|
+
- Detect. The detected models are the `model` values that the `Agent` tool schema lists, each with an effort from its `effort` values. Write a real model as `<model> <effort>`, such as `opus xhigh`. The effort is the last token, so the budget step works as written.
|
|
46
|
+
- Defaults. Map each default slug with the rows above: `claude-opus-5-5-xhigh-fast` is `opus xhigh`, `claude-opus-5-5-high-fast` is `opus high`, `claude-fable-5-2-high` is `fable high`, and `gemini-4-carbon-high` is `inherit-parent`.
|
|
47
|
+
- Write. Write `~/.claude/rules/pstack-models.md` with no frontmatter, then the comment lines, the `# budget` line, and one line per role from step 5. Overwrite the whole file. Never put the role lines in `CLAUDE.md` or `AGENTS.md`.
|
|
48
|
+
|
|
49
|
+
## Paths
|
|
50
|
+
|
|
51
|
+
| Cursor | Claude Code |
|
|
52
|
+
| --- | --- |
|
|
53
|
+
| `.cursor/skills/`, `~/.cursor/skills/` | `.claude/skills/`, `~/.claude/skills/` |
|
|
54
|
+
| `~/.cursor/plugins/`, `.cursor-plugin/plugin.json` | `~/.claude/plugins/`, `.claude-plugin/plugin.json` |
|
|
55
|
+
| `.cursor/rules/*.mdc`, always-applied rules | `CLAUDE.md`, or `AGENTS.md` when no `CLAUDE.md` exists. Claude Code never reads `.mdc` files. The model rule is the exception. See Models. |
|
|
56
|
+
| `https://github.com/cursor/plugins/blob/main/pstack/<path>` | `<pstack>/<path>` when that file exists. The plugin ships the skills, `docs/guide/`, and `README.md`. Read the local copy and never fetch it. Give the user the URL when they need a link. |
|
|
57
|
+
| Transcripts in `~/.cursor/projects/<slug>/agent-transcripts/` | `~/.claude/projects/<slug>/<session>.jsonl`. The slug is the workspace path with each `/` and `.` changed to `-`, so `/Users/you/proj` is `-Users-you-proj`. The newest `.jsonl` directly in that folder is the current session. Its `<session>/subagents/` folder holds subagent transcripts. Read only this workspace's folder. |
|
|
58
|
+
|
|
59
|
+
## Cursor-only features
|
|
60
|
+
|
|
61
|
+
Claude Code has no Cursor Automations, Bugbot, Cursor cloud agents, or built-in PR tool. When a step needs one, put one line in your reply, `Skipped in Claude Code: <step>. <reason>.`, then go on to the next step. Do not stop, ask, or retry. When a later step needs what the skipped step made, such as a URL or a key, leave a placeholder and name it in the line.
|
|
62
|
+
|
|
63
|
+
| Cursor | Claude Code |
|
|
64
|
+
| --- | --- |
|
|
65
|
+
| Cursor Automations: routines, `update_state` routine calls, `api2.cursor.sh/automations` webhooks, routine wakes, and `SendToUser` secret requests | Skip with the line. |
|
|
66
|
+
| Bugbot | Bugbot comments on a GitHub PR are ordinary review threads, so triage them with the forge command that the step gives. Skip a step that starts, waits for, or configures Bugbot when the PR has no Bugbot check or comment. |
|
|
67
|
+
| Cursor cloud agents | `environment: "cloud"` maps to a worktree, as in Subagent fields. Skip a step that needs the cloud agent itself, such as its dashboard status or its own machine. |
|
|
68
|
+
| A built-in PR tool | Use the forge command that the step gives, such as `gh pr create`. That is not a skip, so write no line. |
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: architect
|
|
3
|
+
description: "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."
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Architect
|
|
8
|
+
|
|
9
|
+
Before writing code, trace every system the change touches, then sketch two different shapes for it (types, signatures, module boundaries) and pick the one where each piece of state has one owner, each task has one way to do it, and callers need to know least. Redesign instead of patching if workarounds repeat.
|
|
10
|
+
|
|
11
|
+
For a large or contested design, run the **arena** skill instead of sketching alone.
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: arena
|
|
3
|
+
description: "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."
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Arena
|
|
8
|
+
|
|
9
|
+
Open a todolist with one entry per phase (Frame, Fan out, Cross-judge, Pick, Graft, Verify) before launching anything.
|
|
10
|
+
|
|
11
|
+
## Phase A: Frame
|
|
12
|
+
|
|
13
|
+
Every candidate gets the same prompt, so the prompt is the contract.
|
|
14
|
+
|
|
15
|
+
1. State the artifact each candidate is producing.
|
|
16
|
+
2. Derive the rubric, 3-6 concrete gradeable criteria for what success looks like on *this* task. It is the picker's tool in Phase D. Candidates only see the task.
|
|
17
|
+
3. Pick the runners from the `arena runners` line in `~/.cursor/rules/pstack-models.mdc`, by default `claude-fable-5-2-high`, `claude-opus-5-5-high-fast`, and `gemini-4-carbon-high`. An `auto` or `inherit-parent` entry is the parent model, so omit `model` and spawn `generalPurpose`. If the Task tool rejects a slug, use the nearest valid slug of the same family or drop the seat, keep at least two runners, and say so. Families go by prefix, and the longest match wins: `claude-fable-*`, `claude-*`, and `gemini-*`, after dropping a leading `cursor-`. Any other slug's family is its text before the first hyphen. Spawn more for multiple design directions, and repeat one model when the work is generation-bound, not judgment-sensitive. Pick each subagent's reasoning level per the Subagents section of the **poteto-mode** skill.
|
|
18
|
+
4. Give each candidate its own output location (a git worktree where possible, otherwise `/tmp/arena-<slug>/candidate-<n>/`), per the **separate-before-serializing-shared-state** principle skill.
|
|
19
|
+
|
|
20
|
+
## Phase B: Fan out
|
|
21
|
+
|
|
22
|
+
Spawn all N subagents in one message with `run_in_background: true`, each with the task, the path to the shared grounding, its own output path, and instructions to produce the artifact and a short rationale naming the alternatives it considered and what it rejected.
|
|
23
|
+
|
|
24
|
+
If a candidate produces no output, proceed with N-1 and note the dropout.
|
|
25
|
+
|
|
26
|
+
## Phase C: Cross-judge
|
|
27
|
+
|
|
28
|
+
After all Phase B candidates complete, spawn one readonly judge from the `arena cross-judge pool` line in `~/.cursor/rules/pstack-models.mdc`, by default `claude-opus-5-5-high-fast`, `gemini-4-carbon-high`. The judge is never from the parent's vendor, and Fable counts as Claude for that check, so use the first entry from another vendor. An `auto` or `inherit-parent` entry is the parent model. If you do not know the parent's model, use the first real slug and say that the vendor check did not run. If the Task tool rejects a slug, use the nearest valid slug of the same family, then the next such entry, or skip the judge, and say so. While you read in Phase D, the judge scores each candidate, by path label, on each rubric criterion and recommends a base.
|
|
29
|
+
|
|
30
|
+
## Phase D: Pick a base
|
|
31
|
+
|
|
32
|
+
Read every candidate end to end before picking. Score each against the rubric criterion by criterion, not on holistic feel, and compare with the cross-judge when Phase C ran one. Agreement on the base confirms the pick. Disagreement means one of you is biased or the rubric was ambiguous. Read both rationales before deciding.
|
|
33
|
+
|
|
34
|
+
Pick the base a future maintainer can extend most easily without breaking invariants. When two feel tied, prefer the cleaner boundary or smaller API, per the Laziness Protocol.
|
|
35
|
+
|
|
36
|
+
## Phase E: Graft
|
|
37
|
+
|
|
38
|
+
Walk each losing candidate once more for what is worth porting into the base, usually one or two things per candidate, not most of it. Fold each graft in by hand, per the **redesign-from-first-principles** principle skill, so the result stays coherent under one mental model. Don't paste mechanically.
|
|
39
|
+
|
|
40
|
+
If the candidates converge on one shape, that is strong agreement. Note it and ship the consensus shape. No graft is needed. If they wildly diverge, Phase A was under-specified. Reframe and re-run rather than averaging the divergence.
|
|
41
|
+
|
|
42
|
+
## Phase F: Verify
|
|
43
|
+
|
|
44
|
+
Verify the synthesized artifact like any other output, per the **prove-it-works** principle skill. If verification finds a problem the arena missed, either Phase A was wrong (re-frame and re-run) or a candidate caught it and you missed the graft (go back to Phase E). Don't paper over it.
|
|
45
|
+
|
|
46
|
+
## Outputs
|
|
47
|
+
|
|
48
|
+
One synthesized artifact, with a short synthesis note alongside naming the base and why, the cross-judge's verdict or that Phase C skipped the judge, each graft with its source candidate, what was rejected and why, any convergence or dropouts, and the verification result.
|
|
@@ -0,0 +1,104 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: automate-me
|
|
3
|
+
description: "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 create-skill + unslop, optionally pulling fresh evidence from recent transcripts."
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Automate me
|
|
8
|
+
|
|
9
|
+
A guided flow for turning the user's working conventions into a skill agents will follow. The output is one `-mode` skill tailored to them (e.g. `jay-mode`, `priya-mode`).
|
|
10
|
+
|
|
11
|
+
This skill orchestrates three others: an inline mining pass (see step 1), Cursor's built-in `create-skill` (authoring), and the **unslop** skill (prose discipline). It sequences them. It doesn't replace them.
|
|
12
|
+
|
|
13
|
+
## Flow
|
|
14
|
+
|
|
15
|
+
### 0. Check for an existing skill
|
|
16
|
+
|
|
17
|
+
Look recursively for `.cursor/skills/**/*-mode/SKILL.md` and `~/.cursor/skills/*-mode/SKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.cursor/skills/<handle>/`), not only at the top level. If one exists, confirm intent with `AskQuestion` (unless they already said "update my skill" or similar):
|
|
18
|
+
|
|
19
|
+
- Update the existing skill (default for repeat runs)
|
|
20
|
+
- Start fresh (rare, ask why before doing it)
|
|
21
|
+
|
|
22
|
+
Update mode changes the rest of the flow:
|
|
23
|
+
- Step 1 mines only history since the skill was last edited (`git log -1 --format=%cI <path>`).
|
|
24
|
+
- Step 2 asks what's changed or missing, not what to capture from zero.
|
|
25
|
+
- Step 4 edits the existing file in place. Preserve sections the user hasn't contradicted. Revise ones with new evidence. Add new sections only for genuinely new rules.
|
|
26
|
+
|
|
27
|
+
### 1. Mine their history
|
|
28
|
+
|
|
29
|
+
Locate the active workspace's transcripts before fanning out. The system prompt names the workspace's `agent-transcripts/` directory. Use only that path. Don't glob across `~/.cursor/projects/*/`. That crosses workspace boundaries and reads private chats from unrelated projects.
|
|
30
|
+
|
|
31
|
+
Survey recent agent conversations within that scope for recurring patterns. Run multiple parallel subagents across slices of history (e.g. last 2-4 weeks, split into 3 slices so each has enough material). Pick each subagent's reasoning level for the job, per the Subagents section of the **poteto-mode** skill. Each slice mining subagent reads transcripts from the workspace-scoped path the parent provides, looks for the signals below, and returns a short structured list of patterns it saw with evidence pointers. Default signals worth hunting:
|
|
32
|
+
|
|
33
|
+
- Response preferences (length, tone, format, "dumb it down" corrections)
|
|
34
|
+
- Delegation habits (subagents, models, specialized workflows, parallelism)
|
|
35
|
+
- Verification posture (what "done" means, unit tests vs live repro, reviewers)
|
|
36
|
+
- Code and prose discipline (style, principles cited, lint/format tools)
|
|
37
|
+
- Process conventions (worktrees, commits, PRs, review/merge tooling)
|
|
38
|
+
- Meta preferences (fixing skills mid-task, proposing new ones)
|
|
39
|
+
|
|
40
|
+
Cross-check across slices before elevating a signal. Patterns seen in 2+ slices are high-confidence. Lone signals are weak and usually get dropped.
|
|
41
|
+
|
|
42
|
+
### 2. Ask the user directly
|
|
43
|
+
|
|
44
|
+
Mining misses intent that hasn't come up yet. Use the `AskQuestion` tool (structured multi-choice) rather than asking the user to type from scratch.
|
|
45
|
+
|
|
46
|
+
Shape: one or two questions with 4-6 options each, `allow_multiple: true` for category questions. Start broad ("Which areas matter most?"), then follow up on selected areas with specific options. After the structured rounds, one free-form chat question catches anything the options missed.
|
|
47
|
+
|
|
48
|
+
Don't dump 20 questions.
|
|
49
|
+
|
|
50
|
+
### 3. Cluster findings
|
|
51
|
+
|
|
52
|
+
Group the combined signals into sections. Common ones (use only what applies):
|
|
53
|
+
|
|
54
|
+
- **Response style**: length, tone, format.
|
|
55
|
+
- **Autonomy**: how much to do without asking, MCP tool use.
|
|
56
|
+
- **Understand first**: which skills to reach for when scoping or investigating a change.
|
|
57
|
+
- **Subagents**: default, parallelism, model-to-task, specialized workflows.
|
|
58
|
+
- **Prose / code discipline**: principles, lint tools, style guides.
|
|
59
|
+
- **Review and verify**: repro posture, verification skills, live-testing tools.
|
|
60
|
+
- **Process**: git worktrees, commits, PRs, review/merge tooling.
|
|
61
|
+
- **Skills**: skill-authoring habits, fix-the-skill-first, proposing new skills.
|
|
62
|
+
|
|
63
|
+
The **poteto-mode** skill shows the shape. Read it for granularity. Don't copy its content. The user's rules are not the same as poteto-mode's.
|
|
64
|
+
|
|
65
|
+
### 4. Draft the skill
|
|
66
|
+
|
|
67
|
+
Use Cursor's built-in `create-skill` skill to author the skill. Placement:
|
|
68
|
+
|
|
69
|
+
- Path: preserve an existing mode skill's category. For a new mode, use `.cursor/skills/<handle>/<handle>-mode/SKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.cursor/skills/<handle>-mode/SKILL.md` in the project (or `~/.cursor/skills/<handle>-mode/` if the user prefers a personal skill).
|
|
70
|
+
- Handle: the user's first name or chosen identifier.
|
|
71
|
+
- Frontmatter `description`: trigger on their name + `/<handle>-mode` + "work in their style", not on generic keywords like "write code" or "review PR".
|
|
72
|
+
- Frontmatter formatting: follow `create-skill`'s YAML rules. Keep `description` as one YAML scalar. Quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it.
|
|
73
|
+
- Frontmatter `disable-model-invocation: true` by default. Opt out only if the user explicitly wants their mode to apply on every turn.
|
|
74
|
+
|
|
75
|
+
### 5. Iterate on prose
|
|
76
|
+
|
|
77
|
+
Apply the **unslop** skill and `create-skill`'s writing guidelines to every line.
|
|
78
|
+
|
|
79
|
+
Show the draft to the user and take feedback. Expect multiple iterations. Cut ruthlessly. A mode skill is not a manual.
|
|
80
|
+
|
|
81
|
+
### 6. Land it
|
|
82
|
+
|
|
83
|
+
Work in a worktree off main. Commit and open a PR. Don't push to main directly.
|
|
84
|
+
|
|
85
|
+
## Guardrails
|
|
86
|
+
|
|
87
|
+
- **Don't overfit to one conversation.** A preference stated once and contradicted another time is noise. Require multiple instances before codifying it.
|
|
88
|
+
- **Don't be clever.** Restating other skills' contents, inventing metaphors, or writing "poetic" prose for an agent reader is cost without benefit. Keep it operational.
|
|
89
|
+
- **Reference, don't inline.** Other skills the user relies on should appear as path references, not pasted excerpts. Same for any principle docs they maintain elsewhere.
|
|
90
|
+
- **Keep sections minimal.** Only add a section if the user has a specific, non-default rule there. "Communicate clearly" is not a section. "Short paragraphs. Tables when comparing options. Bullets only when items are genuinely parallel." is.
|
|
91
|
+
- **Name conventions generic.** Use "the user" or "the human" in imperatives, not the author's first name.
|
|
92
|
+
- **Don't force symmetry.** If a user has no process rules worth writing down, skip the Process section entirely.
|
|
93
|
+
|
|
94
|
+
## Evaluation
|
|
95
|
+
|
|
96
|
+
A `-mode` skill is subjective output. A `create-skill`-style test/iterate benchmark loop isn't useful here. Vibe-check with the user: does it read like them? Did it miss anything? Then ship.
|
|
97
|
+
|
|
98
|
+
Run a description-optimization loop only if the skill's trigger accuracy turns out to be a problem in practice.
|
|
99
|
+
|
|
100
|
+
## When not to use
|
|
101
|
+
|
|
102
|
+
- User wants a task-specific skill (not working conventions): `create-skill` alone, no mining required.
|
|
103
|
+
- User wants to capture one narrow workflow (e.g. "how I write commit messages"). That's a regular skill, not a mode skill.
|
|
104
|
+
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: benchmark-checklist
|
|
3
|
+
description: "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."
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Benchmark checklist
|
|
8
|
+
|
|
9
|
+
Use this when you produce a performance number: a PR's before and after, a regression claim, a hillclimb harness, or a library or config choice. Answer each question with evidence from a run, not a guess about the code.
|
|
10
|
+
|
|
11
|
+
For a quick ballpark the user asked for, one run is enough. Still check questions 4 and 7, and say that it is one run. Skip the rest unless that run looks wrong. A choice between options is never a ballpark.
|
|
12
|
+
|
|
13
|
+
## Before you run anything
|
|
14
|
+
|
|
15
|
+
- Write down the claim you expect to make, in the words you would ship ("export is 30% faster at p50 on the 60k-row dataset"). The questions test that sentence.
|
|
16
|
+
- Read the measurement script. Note what it times, counts, and ignores.
|
|
17
|
+
- Check the load average with `uptime` and the core count with `nproc`. If the machine is busy, find out what is running. If you cannot stop it, interleave the sides so both see the same noise, and say so in the report.
|
|
18
|
+
|
|
19
|
+
## The questions
|
|
20
|
+
|
|
21
|
+
1. **Why not double?** Name the limiter. Profile in a run you do not report, because profilers and tracers slow the work down. Use CPU per process (`top`, `pidstat`), a runtime profiler (`node --cpu-prof`, `py-spy`, `perf`), I/O wait, and syscall counts (`strace -c` on Linux), then map the hot spot to source. Watch the load generator too: if it saturates first, you measured the load generator. If a change did not move the number, the limiter explains why, so find it before you call the change useless.
|
|
22
|
+
2. **Was it tuned?** Run every side the way production runs it: release builds, production flags and env, batching and transaction settings, connection pools, caches as warm or cold as production sees them, and the same versions and data. If one side runs on defaults, you compared configurations, not implementations. A limiter that is a setting (a commit per row, a debug build, a missing index) means that side is untuned. Tune it and measure again before you pick a winner. If you cannot tune it, do not pick a winner from that run. When the user is choosing what to adopt, narrowing the claim to the code as it ships today does not fix this, because they adopt the option, not today's settings.
|
|
23
|
+
3. **Did it break limits?** Do the arithmetic. Compare bytes per second with disk and network bandwidth, operations per second times cost per operation with your cores, and the time saved with the time the changed piece took. Removing a piece that takes 10% of the run can make the run at most about 11% faster. A result past a limit measured something other than the work, such as a cache, a no-op, or a bug.
|
|
24
|
+
4. **Did it error?** Count failures and non-success responses, and check that outputs are correct, not just present. Rejections are often fast, and timeouts and retries are slow. If the script does not count errors, add the count.
|
|
25
|
+
5. **Does it reproduce?** Run each side at least 5 times, alternating (A, B, A, B, and so on) so warmup, lazy initialization, caches, and drift favor neither. Report the median and range. A gap smaller than the run-to-run variation is no measurable difference. When the call is close, use a rank-sum test or the harness's own statistics.
|
|
26
|
+
6. **Does it matter?** Next to any micro result, measure the end-to-end path a user waits on, with realistic data sizes and concurrency, and report the micro result as a share of the whole. A helper that takes 1% of a request can make the request at most 1% faster, however fast the helper gets.
|
|
27
|
+
7. **Did it even happen?** Confirm the work ran inside the timed region: the request reached the server, the rows were written, the bytes were read, and the code used the result. Lazy code (generators nobody iterates, promises nobody awaits, results the JIT can discard) and timeouts produce numbers for work that never happened.
|
|
28
|
+
|
|
29
|
+
## Report
|
|
30
|
+
|
|
31
|
+
- Lead with the verdict: faster, slower, no measurable difference, or inconclusive.
|
|
32
|
+
- Give the number with its unit, the run count, the range, and the limiter. For example, "p50 41 ms → 33 ms, median of 7 runs per side, range 32 to 35 ms after, bound by JSON parsing on one core."
|
|
33
|
+
- Call the verdict inconclusive when you claim a difference but cannot name the limiter, when a side ran untuned, or when you could not check questions 4 and 7. Name the gap.
|
|
34
|
+
- Keep a PR body to one primary number. Put the runs, range, and limiter evidence in a linked artifact or notes file.
|
|
35
|
+
|
|
36
|
+
## Other perf material
|
|
37
|
+
|
|
38
|
+
- Vet the **Perf issue** playbook's baseline before the playbook plans from it, and every number after that.
|
|
39
|
+
- Vet the **Hillclimb** playbook's harness before it is frozen. The frozen harness then prints error and work counts, so each keep-or-revert checks questions 4 and 7 for free.
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: blast-radius
|
|
3
|
+
description: "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."
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Blast radius
|
|
8
|
+
|
|
9
|
+
Find what a change breaks somewhere else, before it ships. Use for "blast radius of X", "what could this break", or reviewing a small diff you don't trust yet.
|
|
10
|
+
|
|
11
|
+
Companion to `how` and `why`. `how` tells you what the code does. `why` tells you why it's shaped that way. Blast radius tells you what it breaks somewhere else.
|
|
12
|
+
|
|
13
|
+
Listing the callers is not the job. The agent can grep those in a second. The job is the breakage grep won't show you.
|
|
14
|
+
|
|
15
|
+
## Don't trust your own writeup
|
|
16
|
+
|
|
17
|
+
A blast-radius writeup that sounds right is worthless. It reads as convincing whether or not it's true. So don't hand back the writeup. Find the one or two facts the whole thing depends on and prove them by running code.
|
|
18
|
+
|
|
19
|
+
### How sure are you
|
|
20
|
+
|
|
21
|
+
For each fact the change's safety depends on, get it as far down this list as is cheap, and say where it stopped.
|
|
22
|
+
|
|
23
|
+
1. You said so. Worthless on its own.
|
|
24
|
+
2. You pointed at the line. A real `file:line`, or the library's own source.
|
|
25
|
+
3. You showed the bad case can't happen. You walked the failure step by step and it doesn't reach.
|
|
26
|
+
4. You ran it. A script or test that calls the real code and fails loud if you're wrong.
|
|
27
|
+
5. You reproduced it in the running app.
|
|
28
|
+
|
|
29
|
+
Step 4 is usually one small script that imports the same library the app ships and calls the exact function you're worried about.
|
|
30
|
+
|
|
31
|
+
## Steps
|
|
32
|
+
|
|
33
|
+
1. Read the change. The diff, the symbols it adds, changes, and deletes, and what it now does differently, including the part the diff doesn't spell out. Pull the PR and its commits.
|
|
34
|
+
2. Find the one fact it's safe because of. Most changes that look risky are safe because of a single fact, like "this call only drops already-dead cache entries and does nothing else". Find that fact. If it holds, most risky cases are cleared at once. Spend your time here, not on a long list of maybes.
|
|
35
|
+
3. Look where grep stops. Read the source of the library you call, and check its pinned version and any local patch. Work out when things run: microtasks, unmount and teardown, Solid versus React. Follow what a symbol search misses: the JSON an API returns, a DB column, a wire format, another language reading the same bytes, a feature flag, code three hops downstream.
|
|
36
|
+
4. Be honest about each risk. Give it a real chance of happening and a real cost if it does. Keep the risks you confirmed. List the ones you checked and cleared separately. Cite a real `file:line`, a search that finds nothing is still an answer, and never make up a caller or an API.
|
|
37
|
+
5. Prove the one fact. Write a script or test that runs the real code, run it, and paste what happened.
|
|
38
|
+
6. For a big or wide change, run it as an `arena`. Ask more than one model the same question and merge the answers. Different models catch different real bugs.
|
|
39
|
+
|
|
40
|
+
## What to hand back
|
|
41
|
+
|
|
42
|
+
- **What it does.** What changed, including the part that isn't obvious.
|
|
43
|
+
- **The one fact it's safe because of.** State it, say which step you got it to, and show the proof. If you couldn't prove it, write unproven.
|
|
44
|
+
- **Risks.** Each names how it breaks, the `file:line`, how likely and how bad, and how to check. Paste the proof for the ones that matter.
|
|
45
|
+
- **Cleared.** What you checked and why it's fine.
|
|
46
|
+
- **Before you merge.** The cheapest test or repro that catches the real bug, including the script you wrote.
|
|
47
|
+
|
|
48
|
+
Write it through `unslop`, cite real code, and strip anything private before it goes anywhere public.
|
|
49
|
+
|
|
50
|
+
**Reply:** the writeup above, with the one safety fact either proven or marked unproven.
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: bro
|
|
3
|
+
description: Restate the last message in plain human language, with no jargon.
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
Restate your last message. Stop using jargon and speak coherently. State it more simply and concisely, like one human talking to another.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: correct
|
|
3
|
+
description: "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."
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Correct
|
|
8
|
+
|
|
9
|
+
The operator keeps correcting agents in this repo for the same mistakes. Change the repo so the next agent can't make them.
|
|
10
|
+
|
|
11
|
+
Assume every contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Design the repo so a change that looks right from one file is right for the whole repo.
|
|
12
|
+
|
|
13
|
+
## Find the mistake classes
|
|
14
|
+
|
|
15
|
+
First, read recent commits, reverts, review comments, agent instruction files, and comments that explain workarounds. Group the mistakes into classes. A class counts once it has happened twice.
|
|
16
|
+
|
|
17
|
+
## Fix each class at the highest level that works
|
|
18
|
+
|
|
19
|
+
1. **Eliminate it with architecture.** Give each piece of state one owner and each task one supported way. Hide internals so the wrong import fails. Replace hand-synced lists with one source of truth. Delete old ways and dead code an agent would copy.
|
|
20
|
+
2. **Enforce it with types so the bad state can't be written.** If bad code still compiles, add a lint or CI check whose error names the file, type, or function to use instead. If the pattern is already common, fail only when a change adds more.
|
|
21
|
+
3. **Test the behavior.** Fix or delete any test that still passes when the behavior it checks breaks, or that fails when only the internals change.
|
|
22
|
+
4. **Write docs or agent rules last, only for judgment calls.** Nothing fails when an agent skips them.
|
|
23
|
+
|
|
24
|
+
## Fix and prove
|
|
25
|
+
|
|
26
|
+
Then fix the most frequent classes now, one commit each. Prove each new check fails on a real past mistake. Run the same command locally and in CI. Exceptions go on the offending line with a reason, an expiry date, and a human's approval.
|
|
27
|
+
|
|
28
|
+
## Keep the rule table
|
|
29
|
+
|
|
30
|
+
Last, keep a table in the agent instruction file that pairs each rule with what enforces it. When the operator corrects you, fix the mistake and add the rule. If the rule was already there and nothing enforces it, that's a repeat, so fix it at the highest level in the same change. Drop a rule once its mistake can't happen.
|
|
31
|
+
|
|
32
|
+
**Reply:** each class with its evidence, the level you picked, and why a higher level didn't work.
|