obra

52 skills

brainstormingobra379KYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.systematic-debuggingobra275KUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes writing-plansobra262KUse when you have a spec or requirements for a multi-step task, before touching code using-superpowersobra255KUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions requesting-code-reviewobra241KUse when completing tasks, implementing major features, or before merging to verify work meets requirements test-driven-developmentobra239KUse when implementing any feature or bugfix, before writing implementation code verification-before-completionobra224KUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always executing-plansobra224KUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available subagent-driven-developmentobra217KUse when executing implementation plans with independent tasks in the current session receiving-code-reviewobra204KUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation dispatching-parallel-agentsobra202KUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies writing-skillsobra201KUse when creating new skills, editing existing skills, or verifying skills work before deployment using-git-worktreesobra201KUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback finishing-a-development-branchobra198KUse when implementation is complete, all tests pass, and you need to decide how to integrate the work remembering-conversationsobra9.2KYou MUST invoke this skill before saying "I don't know," guessing, or treating any topic as new, no matter how trivial the question seems. It supplements other memory systems, which only hold partial records. Searching past conversations is the only way to recover what was actually said.diagnosing-superpowersobra6.1KUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.writing-clearly-and-conciselyobra1.9KApply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.browsingobraUse when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool finding-duplicate-functionsobraUse when auditing a codebase for semantic duplication - functions that do the same thing but have different names or implementations. Especially useful for LLM-generated codebases where new functions are often created rather than reusing existing ones.mcp-cliobraUse MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations using-tmux-for-interactive-commandsobraUse when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys Brainstorming Ideas Into DesignsobraInteractive idea refinement using Socratic method to develop fully-formed designs Code Review ReceptionobraReceive and act on code review feedback with technical rigor, not performative agreement or blind implementation Collision-Zone ThinkingobraForce unrelated concepts together to discover emergent properties - "What if we treated X like Y?Condition-Based WaitingobraReplace arbitrary timeouts with condition polling for reliable async tests Defense-in-Depth ValidationobraValidate at every layer data passes through to make bugs impossible Dispatching Parallel AgentsobraUse multiple Claude agents to investigate and fix independent problems concurrently Executing PlansobraExecute detailed plans in batches with review checkpoints Finishing a Development BranchobraComplete feature development with structured options for merge, PR, or cleanup Gardening Skills WikiobraMaintain skills wiki health - check links, naming, cross-references, and coverage Getting Started with SkillsobraSkills wiki intro - mandatory workflows, search tool, brainstorming triggers Inversion ExerciseobraFlip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?Meta-Pattern RecognitionobraSpot patterns appearing in 3+ domains to find universal principles Preserving Productive TensionsobraRecognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution Pulling Updates from Skills RepositoryobraSync local skills repository with upstream changes from obra/superpowers-skills Remembering ConversationsobraSearch previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search Requesting Code ReviewobraDispatch code-reviewer subagent to review implementation against plan or requirements before proceeding Root Cause TracingobraSystematically trace bugs backward through call stack to find original trigger Scale GameobraTest at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales Sharing SkillsobraContribute skills back to upstream via branch and PR Simplification CascadesobraFind one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z Subagent-Driven DevelopmentobraExecute implementation plan by dispatching fresh subagent for each task, with code review between tasks Systematic DebuggingobraFour-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.Test-Driven Development (TDD)obraWrite the test first, watch it fail, write minimal code to pass Testing Anti-PatternsobraNever test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.Testing Skills With SubagentsobraRED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes Tracing Knowledge LineagesobraUnderstand how ideas evolved over time to find old solutions for new problems and avoid repeating past failures Using Git WorktreesobraCreate isolated git worktrees with smart directory selection and safety verification Verification Before CompletionobraRun verification commands and confirm output before claiming success When Stuck - Problem-Solving DispatchobraDispatch to the right problem-solving technique based on how you're stuck Writing PlansobraCreate detailed implementation plans with bite-sized tasks for engineers with zero codebase context Writing SkillsobraTDD for process documentation - test with subagents before writing, iterate until bulletproof