Recently Added
Fresh skills just added to the collection. Be the first to try them out!
Finding Open Access Papers
by kthorn
Use Unpaywall API to find free full-text versions of paywalled papers
Getting Started with Skills
by obra
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Brainstorming Ideas Into Designs
by obra
Interactive idea refinement using Socratic method to develop fully-formed designs
Executing Plans
by obra
Execute detailed plans in batches with review checkpoints
Subagent-Driven Development
by obra
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Finishing a Development Branch
by obra
Complete feature development with structured options for merge, PR, or cleanup
Writing Plans
by obra
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Verification Before Completion
by obra
Run verification commands and confirm output before claiming success
Code Review Reception
by obra
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Systematic Debugging
by obra
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Requesting Code Review
by obra
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Remembering Conversations
by obra
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Encapsulating Complexity
by obra
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Localizing Variables
by obra
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
Maintaining Consistent Abstractions
by obra
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Domain-Focused Naming
by obra
Name code by what it does in the domain, not how it's implemented or its history
Commenting Intent
by obra
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Naming Variables
by obra
Choose names that fully and accurately describe what the variable represents
Exploring Alternatives
by obra
Try 2-3 different approaches before implementing - don't settle for first design you think of
Refactoring Safely
by obra
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
Keeping Routines Focused
by obra
Each routine does one thing and does it well - extract when routines have multiple responsibilities
Simplifying Control Flow
by obra
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
Single Purpose Variables
by obra
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
Validating Inputs
by obra
Check all external inputs for validity - garbage in, nothing out, never garbage out