Claude Skills by chris-hendrix

This skill should be used when creating or modifying Claude Code components including skills, slash commands, agents, and hooks. It provides naming conventions, structure guidelines, best practices, and antipatterns.

This skill should be used when creating, scaffolding, or setting up Claude Code plugins and marketplace configurations.

Consolidated research-plan-implement workflow. Use when the user wants to brainstorm an idea, research a codebase or the web, create an implementation plan, or implement from a plan. Keywords: brainstorm, research codebase, research web, plan, implement all, implement phase N.

This skill should be used when working with git commits, branches, GitHub issues, and GitHub PRs. Provides workflow strategy for draft PRs, squash merging, and Graphite-style development.

This skill should be used when executing engineering tasks using the Ralph workflow methodology. Applies to task execution with researcher, coder, verifier, and reviewer agents in sequence.

This skill should be used when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes.

This skill should be used when assessing artifacts, outputs, or content across multiple dimensions - provides frameworks for dimension selection, parallel evaluation, and concrete upgrade paths to achieve 10/10 quality.

This skill should be used when the user wants to "implement this", "execute a plan", "work on a ticket or issue", "build from a description", mentions implementation execution, or is working on implementing from plans, tickets or issues, or descriptions.

This skill should be used when investigating code, understanding implementations, finding patterns, locating files, or gathering context about how a codebase works. Applies to tasks like "find where X is implemented", "how does Y work", "find examples of Z", or general codebase exploration.

This skill should be used when searching the web for information, researching topics online, finding documentation, looking up technical solutions, or gathering information from external sources.

This skill should be used when the user wants to "start a doc", "write documentation", "create notes", "research something", "document findings", "write up", "create a thought doc", mentions ".thoughts", "thoughts folder", or mentions needing to capture information, specs, or research in a markdown file. For implementation plans, see the `writing-plans` skill instead.

This skill should be used when the user wants to "create a plan", "write an implementation plan", "plan a feature", "design a solution", "plan implementation", mentions "implementation plan", "technical plan", "architecture plan", or is working on creating detailed implementation plans for features or changes.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use whenever the user wants to stress-test a plan, get grilled on their design, mentions "grill me", "challenge my thinking", "poke holes in this", "play devil's advocate", "review my approach", "what am I missing", "pressure test", "tell me why this won't work", or asks for feedback on a plan, proposal, architecture decision, or technical design. Even if the...