AI Agent Workflow Collection

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…

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away.

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.

Apply when wiring validation, error handling, or framework adapters.

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction.

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase.

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share.

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading.

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries.

Apply when introducing a new internal API while old callers still exist.

Apply when reviewing or shaping code that's hard to trace.

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

Apply during planned rewrites and migrations with explicit phase boundaries.

Apply when concurrent actors might write to the same file, branch, key, or state object.

Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs.

Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language.

Configure which models pstack uses per role. Detects your available Claude models and writes a per-role override file that the user can include from their CLAUDE.md. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).