Skill Creator

barrydobson

41 published skills · 0 GitHub stars across the catalog. View on GitHub ↗

encapsulating-complexity

barrydobson's avatarfrom barrydobson

Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)

maintaining-consistent-abstractions

barrydobson's avatarfrom barrydobson

Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns

reducing-complexity

barrydobson's avatarfrom barrydobson

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

commenting-intent

barrydobson's avatarfrom barrydobson

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

designing-before-coding

barrydobson's avatarfrom barrydobson

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

exploring-alternatives

barrydobson's avatarfrom barrydobson

Try 2-3 different approaches before implementing - don't settle for first design you think of

keeping-routines-focused

barrydobson's avatarfrom barrydobson

Each routine does one thing and does it well - extract when routines have multiple responsibilities

localizing-variables

barrydobson's avatarfrom barrydobson

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

domain-focused-naming

barrydobson's avatarfrom barrydobson

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

naming-variables

barrydobson's avatarfrom barrydobson

Choose names that fully and accurately describe what the variable represents

refactoring-safely

barrydobson's avatarfrom barrydobson

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

simplifying-control-flow

barrydobson's avatarfrom barrydobson

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

single-purpose-variables

barrydobson's avatarfrom barrydobson

Use each variable for exactly one purpose - no hybrid coupling or hidden meanings

validating-inputs

barrydobson's avatarfrom barrydobson

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

writing-evergreen-comments

barrydobson's avatarfrom barrydobson

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

brainstorming-ideas-into-designs

barrydobson's avatarfrom barrydobson

Interactive idea refinement using Socratic method to develop fully-formed designs

dispatching-parallel-agents

barrydobson's avatarfrom barrydobson

Use multiple Claude agents to investigate and fix independent problems concurrently

executing-plans

barrydobson's avatarfrom barrydobson

Execute detailed plans in batches with review checkpoints

finishing-a-development-branch

barrydobson's avatarfrom barrydobson

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

code-review-reception

barrydobson's avatarfrom barrydobson

Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation

remembering-conversations

barrydobson's avatarfrom barrydobson

Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search

requesting-code-review

barrydobson's avatarfrom barrydobson

Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding

subagent-driven-development

barrydobson's avatarfrom barrydobson

Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks

using-git-worktrees

barrydobson's avatarfrom barrydobson

Create isolated git worktrees with smart directory selection and safety verification