个人作者

Darwin Smith

K8s, Golang, Python. Sr. Platform/Backend Dev

所在地 · Detroit, MI更新于 2026-11-14

Skills
51
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 0

Darwin Smith 的 Skills 51

dwin
dwin/skills

visual-explainer

Render interactive visual explanations, architecture simulators, option tradeoff matrices, permission or blast-radius maps, and phased rollout cards on the host's native visual surface. Use when answering a question that compares three or more options across multiple dimensions, traces a multi-gate request or state flow, maps permissions or blast radius, lays out a multi-phase architecture plan, or when the user asks to visualize or sends `viz`.

★ 0
dwin
dwin/skills

writing-for-agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

★ 0
dwin
dwin/skills

wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

★ 0
dwin
dwin/skills

why

Find out why code is the way it is from its history, reviews, tickets, docs, and other records, and say how sure each answer is. Use when the user asks why something is built, written, or behaves a certain way, why a choice was made, or where a number or limit came from.

★ 0
dwin
dwin/skills

whats-next

Match a task to the skill, flow, or playbook that fits it. Use when the user asks what to do next or which workflow applies, when a task fits no other skill, and for these kinds of work, which have playbooks here - proving a property of concurrent or stateful code with a model checker or verifier, matching a UI pixel for pixel, and diagnosing a live process or a captured profile, trace, or heap snapshot.

★ 0
dwin
dwin/skills

wayfinder

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

★ 0
dwin
dwin/skills

wait-what

Stop. That last message did not land — re-pitch it.

★ 0
dwin
dwin/skills

verifying-claims

Establish the state of a pull request, check, branch, secret, deployed resource, or file by observing it rather than inferring it. Use before stating that something is ready, passing, merged, deployed, configured, or absent, when relaying another agent's report, when work depends on external state, or when another skill needs a reusable evidence discipline.

★ 0
dwin
dwin/skills

verifier

Create a project-local skill that proves changes by driving the real app the way a user does, or bring an existing one back in line with the code. Use for "make a verify skill for this repo" or "audit the verify skill".

★ 0
dwin
dwin/skills

unslop

Remove the marks of machine-written prose from text while keeping every fact and the author's voice. Use when the user asks to unslop, humanize, or de-AI a draft, says text sounds like AI wrote it, or wants prose for people checked for AI tells before it is posted or sent.

★ 0
dwin
dwin/skills

triage

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

★ 0
dwin
dwin/skills

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

★ 0
dwin
dwin/skills

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

★ 0
dwin
dwin/skills

to-questionnaire

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

★ 0
dwin
dwin/skills

technical-writing

Write technical prose that a tired engineer understands on the first read. Use when writing, rewriting, or reviewing documentation, a README, a design note, a pull request description, a commit message, or a technical message for people to read.

★ 0
dwin
dwin/skills

tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

★ 0
dwin
dwin/skills

swarm

Coordinate work done by other agents. Brief each worker, track lanes in a ledger, verify what workers report, and stay reachable until every lane is done. Use when delegating a task to another agent or model, when running two or more lanes of work in parallel, or when the user assigns models to roles such as implementer and reviewer.

★ 0
dwin
dwin/skills

sharpen

Rewrite a prompt into a deeper version of the same task before it is sent, without doing the task. Use for "sharpen this prompt" or "make this ask deeper, not bigger".

★ 0