Claude Skills by yuchi-chang

Use when starting a new feature, component, or project whose requirements are underspecified or ambiguous — before designing or writing code

Use when planned work will outlive the current session — persisting a plan to disk, resuming work from an on-disk plan, or landing changes a plan file describes

Use when repeated attempts at the same problem keep failing without producing new evidence — before trying another variation of the last fix

Use when starting a new project or significant feature from a vague idea — before clarifying details or planning, especially when the user already has a preferred approach

Use when writing error handling — try/catch blocks, fallback values, default parameters, retries, or any code path that handles failure

Use when asked to improve performance, or when about to optimize code believed to be slow

Use when receiving code review comments, reviewer suggestions, or technical corrections — before implementing any of them

Use when encountering a bug, test failure, regression, flaky test, or unexpected behavior — before proposing or applying any fix

Use when restructuring, renaming, moving, or extracting code that already works — before making the first edit

Use when writing database schema migrations or changing tables, columns, indexes, or constraints on a system with real data

Use when editing existing code — bug fixes, small features, or any change inside a codebase you didn't just write

Use when about to claim work is complete, fixed, or passing — before committing, opening a PR, marking a task done, or relaying a subagent's success report

Use when writing or modifying tests, adding mocks, or tempted to add test-only methods to production code

Use when designing or planning a multi-step feature, refactor, or spec before implementation begins