Claude Skills by williamwue

Ground a nontrivial design, compare distinct caller-first type and module sketches, then implement within scope and redesign when evidence contradicts the shape.

Compare independent candidates for the same artifact, cross-judge them, select a base, integrate stronger ideas, and verify the result.

Create or revise a scoped, discoverable Skill and validate that its instructions change useful decisions.

Turn a user's recurring working conventions into a concise personal mode Skill with evidence and review.

Drive one bounded engineering task through evidence-based iterations to a fixed predicate without stopping for routine intermediate prompts.

Run an explicitly authorized queue through one-owner-per-change build, independent root verdict, and owner-executed landing until its bounded completion predicate is reached.

Build, independently verify, and arrange an authorized queue as one linear reviewable change stack while reserving every landing decision for the operator.

Inspect or drive a pull request toward merge-ready while keeping status checks, repair authority, and merge authority separate.

Find downstream breakage a diff may cause and prove its load-bearing safety assumptions against real code.

Restate the assistant's immediately preceding message in clear, concise, everyday language.

Diagnose and fix a reproducible software defect with bounded scope, same-surface evidence, and independent root verification.

Create a project-local Skill that launches and drives the real user surface, captures evidence, and cleans up safely.

Run a blinded, repeatable comparison of workflow or model variants using real artifacts and a frozen rubric.

Add or intentionally change behavior through an evidence-backed design, bounded implementation, and matching-surface verification.

Design and execute an auditable plan for a complex task that lacks a narrower workflow.

Improve one measurable outcome through bounded, single-change experiments against a frozen harness.

Explain how a code path or subsystem works through evidence-backed exploration and a verified architectural walkthrough.

Run an adversarial multi-session review with identical inputs, frozen findings, independent synthesis, and root-owned judgment.

Answer a read-only engineering question from repository evidence without changing implementation files.

Audit a project verification Skill against source and live user paths, correcting proven drift in its own files.

Build a local control page that submits validated actions to an authenticated webhook, with optional private-network access.

Write a reviewable dependency plan with verifiable units, owner boundaries, live checks, and explicit execution gates.

Review comments and suppressions in a scoped diff, remove redundant ones, and encode real constraints in structure where feasible.

Prepare and, only when explicitly requested, publish a reviewed branch as a ready pull request with verified scope and evidence.

Coordinate a standing multi-session engineering program through durable briefs, bounded rolling work, independent verification, and a continuously safe integration frontier.

Stop explicitly requested in-flight engineering work at a durable boundary and leave a checkpoint another session can validate and resume.

Fix one performance defect using representative before and after traces and a correctness gate.

Route a software-engineering request to the smallest admitted Oh My Stack workflow while preserving root ownership and evidence boundaries.

Apply 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.

Build an isolated throwaway experiment that produces evidence for one explicit design or behavior decision.

Verify that this workflow package can load a Skill and report concrete read-only workspace evidence.

Reconstruct recent work from scoped conversation history, current repository state, and available shared records.

Improve code structure while pinning and proving unchanged externally observable behavior.

Review a scoped conversation for recurring lessons and propose evidence-backed corrections to existing Skills.

Reproduce 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.

Diagnose a live process from captured runtime evidence and connect the observed mechanism to source.

Resume or take over prior in-flight engineering work from a checkpoint, transcript, or branch without repeating completed work or inheriting stale authority.

Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

Preview and configure pstack-style per-workflow models, review panels, and reasoning budget from the current runtime inventory.

Land an explicitly authorized pull request or stack only after independent revision-bound verdicts establish a contiguous safe frontier.

Keep a reviewable, append-only decision trail for long-running, delegated, or unattended work.

Run bounded parallel coverage or races, drain all started workers, verify their evidence, and consolidate outcomes and gaps into one report.

Teach a change or subsystem in plain language by composing verified mechanics and historical rationale, preserving uncertainty and the learner's pace.

Diagnose an existing trace, profile, heap snapshot, or spindump without recapturing the process.

Triage 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.

Review or edit TypeScript types and boundaries when TS or TSX code is in scope.

Edit prose to remove recurring AI writing patterns when writing cleanup is requested.

Migrate a UI while proving agreed visual equivalence against frozen baseline captures.

Investigate design rationale, historical tradeoffs, regressions, and thresholds using cited history and available evidence sources.

Audit and reclaim explicitly scoped Git worktrees and disposable simulator state while preserving active and uncommitted work.