Jesse Vincent

Write comments explaining WHAT and WHY, never temporal context or history

The English summary is being prepared. Showing the original description.

Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features

The English summary is being prepared. Showing the original description.

Choose names that fully and accurately describe what the variable represents

The English summary is being prepared. Showing the original description.

Name code by what it does in the domain, not how it's implemented or its history

The English summary is being prepared. Showing the original description.

Skills wiki intro - mandatory workflows, search tool, brainstorming triggers

The English summary is being prepared. Showing the original description.

Managing complexity is software's primary technical imperative - all other goals are secondary

The English summary is being prepared. Showing the original description.

Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels

The English summary is being prepared. Showing the original description.

Check all external inputs for validity - garbage in, nothing out, never garbage out

The English summary is being prepared. Showing the original description.

Complete feature development with structured options for merge, PR, or cleanup

The English summary is being prepared. Showing the original description.

Design in pseudocode first, iterate approaches, then translate to code

The English summary is being prepared. Showing the original description.

Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)

The English summary is being prepared. Showing the original description.

Declare variables in smallest possible scope, initialize close to first use, minimize span and live time

The English summary is being prepared. Showing the original description.

Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.

The English summary is being prepared. Showing the original description.

Write the test first, watch it fail, write minimal code to pass

The English summary is being prepared. Showing the original description.

Replace arbitrary timeouts with condition polling for reliable async tests

The English summary is being prepared. Showing the original description.

RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes

The English summary is being prepared. Showing the original description.

Fork, clone to ~/.clank, run installer, edit CLAUDE.md

The English summary is being prepared. Showing the original description.

TDD for process documentation - test with subagents before writing, iterate until bulletproof

The English summary is being prepared. Showing the original description.

Run verification commands and confirm output before claiming success

The English summary is being prepared. Showing the original description.

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

The English summary is being prepared. Showing the original description.

Systematically trace bugs backward through call stack to find original trigger

The English summary is being prepared. Showing the original description.

Validate at every layer data passes through to make bugs impossible

The English summary is being prepared. Showing the original description.

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context

The English summary is being prepared. Showing the original description.

Create isolated git worktrees with smart directory selection and safety verification

The English summary is being prepared. Showing the original description.