claude-code-optimizer
Claude Code productivity patterns including EPCC workflow, context management, and extended thinking triggers. Use when starting sessions or managing context.
When & Why to Use This Skill
The Claude Code Optimizer is a high-performance productivity framework designed to streamline software development workflows within Claude. By implementing the structured EPCC (Explore, Plan, Code, Commit) pattern and advanced context management protocols, it ensures high-quality code output, prevents context-related quality degradation, and leverages extended thinking triggers for complex architectural and algorithmic challenges.
Use Cases
- Complex Feature Implementation: Using the EPCC pattern to systematically explore existing codebases and create detailed implementation plans before writing a single line of code.
- Long-Session Context Optimization: Monitoring context usage with the /context command and performing structured 'Document & Clear' routines to maintain AI reasoning speed and accuracy during extended development sessions.
- Advanced Problem Solving: Triggering 'ultrathink' or 'analyze thoroughly' modes to handle high-stakes tasks like security audits, complex refactoring, or performance optimization.
- Project Handoff and Continuity: Generating comprehensive progress-logs (progress-[project]-[date].md) that capture the current state and next steps, allowing for seamless session resumes after clearing context.
| name | claude-code-optimizer |
|---|---|
| description | "Claude Code productivity patterns including EPCC workflow, context management, and extended thinking triggers. Use when starting sessions or managing context." |
Claude Code Optimizer
Maximize productivity through proven workflow patterns.
Critical Rule
Never execute git commands. Output all git commands for manual execution.
EPCC Pattern
The core workflow for every session: Explore → Plan → Code → Commit
1. Explore (No code yet)
Read CLAUDE.md and relevant source files.
Summarize the current state. Do not write code yet.
2. Plan (Think first)
Think hard about implementing [feature].
Consider edge cases and affected files.
Output the plan. Do not implement yet.
3. Code (Execute)
Implement step 1 of the plan.
Run tests after changes.
4. Commit (Output only)
Generate git commands for manual execution.
Do not run git commands.
Extended Thinking Triggers
| Phrase | Use For |
|---|---|
| "think hard" | Architecture decisions |
| "ultrathink" | Complex algorithms, security |
| "think step by step" | Multi-step procedures |
| "analyze thoroughly" | Refactoring, debugging |
Context Management
Monitor
/context
Document & Clear
Before clearing:
Dump progress to progress-[project]-[date].md:
- What was accomplished
- Current state
- Next steps
- Git commands to run
After clearing:
/clear
Read CLAUDE.md and progress file. Continue with [next task].
When to Clear
- After completing major task
- When switching projects
- Context >50% full
- Quality degradation noticed
Troubleshooting
Context overflow: /clear, then read only essential files
Stuck in loop: "Stop. Summarize what's not working. Try different approach."
Quality issues: "Pause. Re-read requirements. Think hard. Start fresh."
See references/claude-md-template.md for CLAUDE.md template.