All authors
Claude Skills by chillerno1
github.com/chillerno149 skills0 installs36 views
- 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
- CorrectFind 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.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\", or \"tear this apart\". 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
- Make Bot UiUse when building a custom UI (page, dashboard, buttons) that should wake a Claude Code routine over its API trigger, when the user must provide the routine's bearer token, or when exposing that UI on Tailscale.Votes: 0GitHub stars: 2
- No CommentsSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.Votes: 0GitHub stars: 2
- Poteto Modepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.Votes: 0GitHub stars: 2
- Playbooks**You own the skill's voice.** 1. Use the **skill-creator** skill (Anthropic's skill for authoring SKILL.md files). 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...Votes: 0GitHub stars: 2
- Poteto WhatRecommend which pstack skill, poteto-mode playbook or principle fits a question. Use for /poteto-what <question>.Votes: 0GitHub stars: 2
- Principle Attack The PremiseApply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.Votes: 0GitHub stars: 2
- Principle Boundary DisciplineApply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.Votes: 0GitHub stars: 2
- Principle Build The LeverApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.Votes: 0GitHub stars: 2
- Principle Encode Lessons In StructureApply 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.Votes: 0GitHub stars: 2
- Principle Experience FirstApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.Votes: 0GitHub stars: 2
- Principle Explain The NumberApply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.Votes: 0GitHub stars: 2
- Principle Fix Root CausesApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.Votes: 0GitHub stars: 2
- Principle Foundational ThinkingApply 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.Votes: 0GitHub stars: 2
- Principle Guard The Context WindowApply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.Votes: 0GitHub stars: 2
- Principle Laziness ProtocolApply 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.Votes: 0GitHub stars: 2
- Principle Make Operations IdempotentApply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.Votes: 0GitHub stars: 2
- Principle Migrate Callers Then Delete Legacy ApisApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.Votes: 0GitHub stars: 2
- Principle Minimize Reader LoadApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.Votes: 0GitHub stars: 2
- Principle Model The DomainApply 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.Votes: 0GitHub stars: 2
- Principle Never Block On The HumanApply 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.Votes: 0GitHub stars: 2
- Principle Outcome Oriented ExecutionApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.Votes: 0GitHub stars: 2
- Principle Prove It WorksApply 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.'Votes: 0GitHub stars: 2
- Principle Redesign From First PrinciplesApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.Votes: 0GitHub stars: 2
- Principle Separate Before Serializing Shared StateApply 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.Votes: 0GitHub stars: 2
- Principle Sequence Verifiable UnitsApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.Votes: 0GitHub stars: 2
- Principle Subtract Before You AddApply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.Votes: 0GitHub stars: 2
- Principle Test Behavior Not ImplementationApply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test.Votes: 0GitHub stars: 2
- Principle Type System DisciplineApply 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.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
- Setup PstackConfigure which models pstack uses per role. Detects the models your Agent tool accepts and writes `~/.claude/pstack-models.md`, which overrides the skill defaults. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.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
- Replay BackAsk the agent to restate the user's goals and the problem they are trying to solve, in its own words. Use when the user invokes /replay-back or wants to check the agent has understood them before work continues.Votes: 0GitHub stars: 2
- Resolve Oss IssueResolve a GitHub issue in an open-source repo from start to finish, whether it reports a bug or asks for a feature. Check that it is not already reported or fixed, turn the issue's asks into an acceptance list, reproduce bugs in the real app, match features to the app's existing behaviour, test first, verify on the same surface, and open a PR. Use when the user describes a bug and asks to check whether it is a known issue, fix or implement a GitHub issue, "repro and resolve", or work an issue...Votes: 0GitHub stars: 2
- VidProduce a narrated mp4 of one of three kinds. explainer (default) is a cinematic animated deck on how something works. tutorial records a real web app driven live with a visible cursor, step by step. marketing is a 30 to 60 second product spot. An Opus 5.5 agent writes the deck or the step script, xAI "liora" voices it, Playwright records, ffmpeg muxes. Use for /vid <kind> <topic>, /vid <topic>, "make an explainer video", "record a tutorial of X", "make a promo video for X".Votes: 0GitHub stars: 2