All authors
Claude Skills by williamwue
github.com/williamwue250 skills3 installs68 views
- 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
- PrototypeBuild an isolated throwaway experiment that produces evidence for one explicit design or behavior decision.Votes: 0GitHub stars: 2
- Prove It WorksVerify that this workflow package can load a Skill and report concrete read-only workspace evidence.Votes: 0GitHub stars: 2
- RecallReconstruct recent work from scoped conversation history, current repository state, and available shared records.Votes: 0GitHub stars: 2
- RefactoringImprove code structure while pinning and proving unchanged externally observable behavior.Votes: 0GitHub stars: 2
- ReflectReview a scoped conversation for recurring lessons and propose evidence-backed corrections to existing Skills.Votes: 0GitHub stars: 2
- Reproduce And Fix IssuesReproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.Votes: 0GitHub stars: 2
- Runtime ForensicsDiagnose a live process from captured runtime evidence and connect the observed mechanism to source.Votes: 0GitHub stars: 2
- Session PickupResume or take over prior in-flight engineering work from a checkpoint, transcript, or branch without repeating completed work or inheriting stale authority.Votes: 0GitHub stars: 2
- Setup BennyConfigure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.Votes: 0GitHub stars: 2
- Setup Oh My StackPreview and configure pstack-style per-workflow models, review panels, and reasoning budget from the current runtime inventory.Votes: 0GitHub stars: 2
- ShippingLand an explicitly authorized pull request or stack only after independent revision-bound verdicts establish a contiguous safe frontier.Votes: 0GitHub stars: 2
- Show Me Your WorkKeep a reviewable, append-only decision trail for long-running, delegated, or unattended work.Votes: 0GitHub stars: 2
- SwarmRun bounded parallel coverage or races, drain all started workers, verify their evidence, and consolidate outcomes and gaps into one report.Votes: 0GitHub stars: 2
- TddUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.Votes: 0GitHub stars: 2
- TeachTeach a change or subsystem in plain language by composing verified mechanics and historical rationale, preserving uncertainty and the learner's pace.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
- Trace ForensicsDiagnose an existing trace, profile, heap snapshot, or spindump without recapturing the process.Votes: 0GitHub stars: 2
- Triage Issue ReportsTriage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.Votes: 0GitHub stars: 2
- Typescript Best PracticesReview or edit TypeScript types and boundaries when TS or TSX code is in scope.Votes: 0GitHub stars: 2
- UnslopCut AI tells from any writing. Must always apply.Votes: 0GitHub stars: 2
- Visual ParityMigrate a UI while proving agreed visual equivalence against frozen baseline captures.Votes: 0GitHub stars: 2
- WhyInvestigate design rationale, historical tradeoffs, regressions, and thresholds using cited history and available evidence sources.Votes: 0GitHub stars: 2
- Worktree CleanupAudit and reclaim explicitly scoped Git worktrees and disposable simulator state while preserving active and uncommitted work.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
- 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
- CorrectEliminate repeated repository mistakes through architecture, types, diagnostic checks, and behavior tests, with proof against real past failures.Votes: 0GitHub stars: 2
- Poteto HelpAnswer Oh My Stack setup and workflow questions with verified sources and one usable prompt; route explicit work requests through poteto-mode.Votes: 0GitHub stars: 2
- Benchmark ChecklistVet performance measurements before reporting or acting on them.Votes: 0GitHub stars: 2
- CorrectPrevent repeated repository mistakes with structural checks and failing proof.Votes: 0GitHub stars: 2
- Poteto HelpAnswer setup and workflow questions with a usable prompt and verified source.Votes: 0GitHub stars: 2
- Principle Explain The NumberExplain what a measured number means and rule out misleading results.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
- CorrectEliminate repeated repository mistakes through architecture, types, diagnostic checks, and behavior tests, with proof against real past failures.Votes: 0GitHub stars: 2
- Poteto HelpAnswer Oh My Stack setup and workflow questions with verified sources and one usable prompt; route explicit work requests through poteto-mode.Votes: 0GitHub stars: 2
- Poteto HelpGuides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.Votes: 0GitHub stars: 2