Claude Skills by dkstm95

Interview the person before implementation when requirements, scope, expected behavior, design, or an important assumption needs shared agreement.

Use when someone asks to explain or review a GitHub pull request as an evidence-linked, self-contained offline HTML review.

Use only when someone explicitly invokes $hope:sweep in Codex, /hope:sweep in Claude Code, or the host's explicit Hope Sweep command to apply behavior-preserving maintenance across a codebase and its directly supporting material. Do not use for ordinary maintenance questions, reviews, planning, bug fixes, feature changes, or product decisions.

Use for a strict, skeptical, risk-focused review of a named work product without attacking people or inventing criticism.

Use as the cross-cutting language standard whenever clearer language would improve any task, including standalone drafts, edits, and reviews and language within implementation or another Skill; preserve meaning, facts, uncertainty, citations, exact text, and voice.

Create, refine, or review an explanatory diagram or data chart when spatial relationships or quantitative shape make the meaning materially clearer. Use within another task without replacing its workflow or artifact; do not use for decorative illustration, simple lists or tables, or UI screen design.