Claude Skills by smnatale

Simplify implementations and keep code clean. Use on all coding tasks to avoid unnecessary abstraction, dependencies, and indirection.

Restate the last message in plain human language, with no jargon.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".

States the user's code comment preferences - short, single-line, and a signal to fix the code when a longer one feels needed. Use before writing or reviewing a code comment.

A relentless interview to sharpen a plan or design.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Run typecheck, lint, and tests on changed files as the last step before declaring a task complete - don't let the user be the one who discovers a broken build. Use before reporting any code change as finished.

Add test coverage for new hooks, utilities, queries, and mutations without being asked, and state it explicitly before calling a task done. Use after writing any new hook, util, query, or mutation, and before reporting a task complete.

States the user's general TypeScript preferences - type safety defaults, export/naming conventions, and React prop typing. Use when writing or reviewing any .ts or .tsx file.

Cut AI tells from any writing. Must always apply.