41 skills (repositories by painhardcore) · sorted by popularity
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.
The English summary is being prepared. Showing the original 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.
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
The English summary is being prepared. Showing the original description.
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
The English summary is being prepared. Showing the original description.
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
The English summary is being prepared. Showing the original description.
Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
The English summary is being prepared. Showing the original description.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
The English summary is being prepared. Showing the original description.
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
The English summary is being prepared. Showing the original description.
Cut AI tells from any writing. Must always apply.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.
The English summary is being prepared. Showing the original description.
Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.
The English summary is being prepared. Showing the original description.
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
The English summary is being prepared. Showing the original description.
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
The English summary is being prepared. Showing the original description.
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
The English summary is being prepared. Showing the original description.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
The English summary is being prepared. Showing the original description.
Use when the user asks to restate or explain the last message in plain, jargon-free language.
The English summary is being prepared. Showing the original description.
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. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
The English summary is being prepared. Showing the original description.
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
The English summary is being prepared. Showing the original 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.
The English summary is being prepared. Showing the original description.
Use before review when the user asks to strip, remove, or clean up comments in code.
The English summary is being prepared. Showing the original description.