stateofthehart

stateofthehart/claude-code-config

Command Claude Code

You are debugging a bug. Follow this sequence exactly. Do NOT skip steps.

stateofthehart/claude-code-config

Command Claude Code

You are debugging an issue where the cause is unknown. This is different from /bugfix — here you don't know what's wrong yet. Follow this sequence.

stateofthehart/claude-code-config

Command Claude Code

You are implementing a feature. Follow this sequence. Do NOT start writing code until Step 3.

stateofthehart/claude-code-config

Command Claude Code

List all Claude Code sessions with their sizes. Run.

stateofthehart/claude-code-config

Command Claude Code

Run the session pruner. If the user passed no arguments (i.e. $ARGUMENTS is empty), run.

stateofthehart/claude-code-config

Command Claude Code

You are refactoring code. The goal is to improve structure WITHOUT changing behavior. Follow this sequence.

stateofthehart/claude-code-config

Command Claude Code

You are reviewing code. Use a subagent with fresh eyes — do NOT review in the same context you wrote the code. If you wrote the code in this session, spawn an independent reviewer subagent.

stateofthehart/claude-code-config

Command Claude Code

You are writing tests for existing code. The goal is to catch real bugs, not achieve coverage metrics.

stateofthehart/claude-code-config

Skill Claude CodeCodex

This skill should be used when the conversation is getting long, context feels bloated, Claude mentions compaction or context limits, the user asks about "context", "pruning", "memory", "compaction", or when Claude notices tool outputs are very large. Also activate when resuming a session, starting a large task, or…