maintaining-consistent-abstractions
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Try 2-3 different approaches before implementing - don't settle for first design you think of
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Managing complexity is software's primary technical imperative - all other goals are secondary
Design in pseudocode first, iterate approaches, then translate to code
Brief description of what this Skill does and when to use it. Include specific trigger phrases. Use when user asks "trigger phrase 1", "trigger phrase 2", or wants to [outcome]. Max 1024 characters.
Brief description of what this Skill does and when to use it. Include specific trigger phrases users would say. Use when user asks "trigger phrase 1", "trigger phrase 2", or wants to [outcome]. Max 1024 charact...
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Choose names that fully and accurately describe what the variable represents
Interactive idea refinement using Socratic method to develop fully-formed designs
Execute implementation work with gate checks and verification. Use when user wants to code, build features, implement iterations, or execute action items. Enforces gates, guides workflow, tracks progress.
Mark tasks and phases complete after verification. Use when finishing tasks, closing phases, or marking work done. Ensures all work verified before completion.
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Execute detailed plans in batches with review checkpoints
Create isolated git worktrees with smart directory selection and safety verification
Complete feature development with structured options for merge, PR, or cleanup
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
TDD for process documentation - test with subagents before writing, iterate until bulletproof
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.