A collection of coding best practices for LLM-assisted development. These skills help you and your team write better code with Claude Code by applying proven patterns from Karpathy's insights and Anthropic's official best practices.
/plugin marketplace add github.com/rahulsub/code-practices-plugin/plugin marketplace add ~/code-practices-plugin| Skill | Command | Description |
|---|---|---|
| Explore-Plan-Code | /code-practices:explore-plan-code |
Read files → plan → approve → implement workflow |
| Goal-Driven | /code-practices:goal-driven |
Define success criteria instead of step-by-step instructions |
| Test-First | /code-practices:test-first |
Write failing tests before implementation |
| Naive-Then-Optimize | /code-practices:naive-then-optimize |
Implement obvious solution first, then optimize |
| Skill | Command | Description |
|---|---|---|
| Code-Review | /code-practices:code-review |
Review code like a skeptical senior engineer |
| Simplify | /code-practices:simplify |
Remove over-engineering and unnecessary abstractions |
| Cleanup | /code-practices:cleanup |
Systematically remove dead code and tech debt |
| Surface-Assumptions | /code-practices:surface-assumptions |
Identify and validate hidden assumptions |
| Tradeoffs | /code-practices:tradeoffs |
Present multiple approaches with explicit tradeoffs |
| Skill | Command | Description |
|---|---|---|
| Visual-Iteration | /code-practices:visual-iteration |
UI feedback loop with screenshots |
| Context-Management | /code-practices:context-management |
Manage long sessions with /clear, checklists, subagents |
| Multi-Claude | /code-practices:multi-claude |
Run parallel Claude instances for writer+reviewer patterns |
| Headless-Automation | /code-practices:headless-automation |
CI/CD integration, fan-out migrations, pipelines |
/code-practices:explore-plan-code
Claude will read relevant files, create a plan, and wait for your approval before coding.
/code-practices:code-review
Review the changes for hidden assumptions, over-engineering, and edge cases.
/code-practices:naive-then-optimize
Implement the obvious correct solution first, then optimize while preserving behavior.
These practices are based on:
MIT