Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By rahulsub
Coding best practices for LLM-assisted development. Based on insights from Karpathy and Anthropic's Claude Code best practices.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin rahulsub-code-practices-pluginSystematic code cleanup after completing features. Use after refactoring or periodically to remove dead code, console statements, TODOs, and tech debt.
Review code like a skeptical senior engineer. Use when reviewing PRs, after generating significant code, or before merging changes.
Manage Claude Code sessions effectively. Use during long sessions, multi-step tasks, or when responses start degrading. Covers /clear, checklists, and subagents.
Structured workflow for non-trivial tasks. Read files first, create detailed plan, get approval, then implement. Prevents premature coding.
Define success criteria instead of step-by-step instructions. Enables autonomous LLM iteration toward testable goals.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Improve and test AI prompts for better Claude Code interactions
Opinionated workflow guides and best practices - the preacher's proven patterns for Claude Code projects
Claude Code workflow patterns: prompting, CLAUDE.md maintenance, multi-agent orchestration
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
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 rahulsub/code-practices-plugin
/plugin marketplace add ~/code-practices-plugin
| Skill | Command | Description |
|---|---|---|
| Explore-Plan-Code | /explore-plan-code | Read files → plan → approve → implement workflow |
| Goal-Driven | /goal-driven | Define success criteria instead of step-by-step instructions |
| Test-First | /test-first | Write failing tests before implementation |
| Naive-Then-Optimize | /naive-then-optimize | Implement obvious solution first, then optimize |
| Skill | Command | Description |
|---|---|---|
| Code-Review | /code-review | Review code like a skeptical senior engineer |
| Simplify | /simplify | Remove over-engineering and unnecessary abstractions |
| Cleanup | /cleanup | Systematically remove dead code and tech debt |
| Surface-Assumptions | /surface-assumptions | Identify and validate hidden assumptions |
| Tradeoffs | /tradeoffs | Present multiple approaches with explicit tradeoffs |
| Skill | Command | Description |
|---|---|---|
| Visual-Iteration | /visual-iteration | UI feedback loop with screenshots |
| Context-Management | /context-management | Manage long sessions with /clear, checklists, subagents |
| Multi-Claude | /multi-claude | Run parallel Claude instances for writer+reviewer patterns |
| Headless-Automation | /headless-automation | CI/CD integration, fan-out migrations, pipelines |
/explore-plan-code
Claude will read relevant files, create a plan, and wait for your approval before coding.
/code-review
Review the changes for hidden assumptions, over-engineering, and edge cases.
/naive-then-optimize
Implement the obvious correct solution first, then optimize while preserving behavior.
These practices are based on:
MIT