All authors
Claude Skills by lucasheriques
github.com/lucasheriques23 skills0 installs37 views
- Sync UpstreamMerge the latest cursor/plugins pstack into this Claude Code port. Use for "sync upstream", "update pstack from cursor", "pull poteto's changes", or when upstream pstack has new commits.Votes: 0GitHub stars: 2
- ArchitectSketch 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.Votes: 0GitHub stars: 2
- ArenaSpawn 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.Votes: 0GitHub stars: 2
- Automate MeUse 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 skill-creator + unslop, optionally pulling fresh evidence from recent transcripts.Votes: 0GitHub stars: 2
- Benchmark ChecklistVet 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.Votes: 0GitHub stars: 2
- Blast RadiusFind 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.Votes: 0GitHub stars: 2
- Create Verification SkillGenerate 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.Votes: 0GitHub stars: 2
- Figure It OutDesign 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.Votes: 0GitHub stars: 2
- HowUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.Votes: 0GitHub stars: 2
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", \"tear this apart\", reviewing someone else's PR, and as the pre-PR gate before opening or readying a PR. Multiple LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 2
- Maintain Verification SkillPeriodic 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\".Votes: 0GitHub stars: 2
- No CommentsSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.Votes: 0GitHub stars: 2
- Poteto HelpGuides users through /pstack:poteto-mode and picking the skill, playbook, or principle for a task. Type /pstack:poteto-help with a question.Votes: 0GitHub stars: 2
- Poteto Modepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use at the start of any engineering task that matches a playbook (bug fix, feature, refactor, perf, investigation, PR babysit or shipping, multi-phase or autonomous runs) or needs rigor, and for /poteto-mode or requests for poteto's style. Skip it for casual turns or when the user opts out.Votes: 0GitHub stars: 2
- Playbooks**You own the skill's voice.** 1. Use the `skill-creator` skill. 2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve. 3. Test cases if structural. Skip if subjective. 4. Run **Opening a PR**. When in doubt, delete. Keep only prose that changes a decision. Tell it to do the thing and skip the reason. Explain only when the rule is confusing without one. Match tone to scope. Point at structural sources (types, READMEs, config) per **...Votes: 0GitHub stars: 2
- RecallReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.Votes: 0GitHub stars: 2
- ReflectSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.Votes: 0GitHub stars: 2
- Show Me Your WorkKeep 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.Votes: 0GitHub stars: 2
- SwarmFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.Votes: 0GitHub stars: 2
- TeachExplain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.Votes: 0GitHub stars: 2
- Technical WritingLayered 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.Votes: 0GitHub stars: 2
- Typescript Best PracticesTypeScript best practices. Use when reading or editing any .ts or .tsx file.Votes: 0GitHub stars: 2
- WhyUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.Votes: 0GitHub stars: 2