Fork, clone to ~/.clank, run installer, edit CLAUDE.md
원문 언어: 영어
메뉴
수집된 skill 37개 중 37개를 표시합니다.
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
원문 언어: 영어
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
원문 언어: 영어
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
원문 언어: 영어
Interactive idea refinement using Socratic method to develop fully-formed designs
원문 언어: 영어
Execute detailed plans in batches with review checkpoints
원문 언어: 영어
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
원문 언어: 영어
Complete feature development with structured options for merge, PR, or cleanup
원문 언어: 영어
Create isolated git worktrees with smart directory selection and safety verification
원문 언어: 영어
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
원문 언어: 영어
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
원문 언어: 영어
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
원문 언어: 영어
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
원문 언어: 영어
Run verification commands and confirm output before claiming success
원문 언어: 영어
TDD for process documentation - test with subagents before writing, iterate until bulletproof
원문 언어: 영어
Write the test first, watch it fail, write minimal code to pass
원문 언어: 영어
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
원문 언어: 영어
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
원문 언어: 영어
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
원문 언어: 영어
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
원문 언어: 영어
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
원문 언어: 영어
Try 2-3 different approaches before implementing - don't settle for first design you think of
원문 언어: 영어
Each routine does one thing and does it well - extract when routines have multiple responsibilities
원문 언어: 영어
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
원문 언어: 영어
Name code by what it does in the domain, not how it's implemented or its history
원문 언어: 영어
Choose names that fully and accurately describe what the variable represents
원문 언어: 영어
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
원문 언어: 영어
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
원문 언어: 영어
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
원문 언어: 영어
Check all external inputs for validity - garbage in, nothing out, never garbage out
원문 언어: 영어
Write comments explaining WHAT and WHY, never temporal context or history
원문 언어: 영어
Maintain skills wiki health - check links, naming, cross-references, and coverage
원문 언어: 영어
Managing complexity is software's primary technical imperative - all other goals are secondary
원문 언어: 영어
Design in pseudocode first, iterate approaches, then translate to code
원문 언어: 영어
Use multiple Claude agents to investigate and fix independent problems concurrently
원문 언어: 영어
Validate at every layer data passes through to make bugs impossible
원문 언어: 영어
Systematically trace bugs backward through call stack to find original trigger
원문 언어: 영어
Replace arbitrary timeouts with condition polling for reliable async tests
원문 언어: 영어