A comprehensive plugin toolkit for Claude Code, with a clear separation of concerns.
Anthropic has released powerful features for Claude Code: commands, agents, hooks, and skills. However, finding effective examples of their use remains challenging. One of the common mistakes is defining responsibilities with ambiguous boundaries, which confuses Claude Code and leads to misbehavior.
This project helps you to use these features effectively by providing a set of plugins and core design principles.
- Fullstack Development - Core workflows for full-stack development
- Code Review - Comprehensive code review and PR analysis
- ERD Skill - Database design and ERD creation using DBML format
Launch Claude Code and run the following command:
/plugin marketplace add byunk/claude-code-toolkitUse the following slash commands as needed.
Feature Development:
Recommended to use this command for complex feature development.
/fullstack-dev:feature-dev <Describe the feature in detail>Comprehensive Code Review:
/code-review:code-review Review the PR #123
/code-review:code-review Review the changes in the current branch
/code-review:code-review Review the changes in the FOO moduleQuick Code Review:
Note: This command does not invoke any subagents. Recommend you to use this command with fresh context with /clear command before using it.
/code-review:quick-review Review the changes in the BAR moduleLLMs experience attention degradation over long contexts, known as the Context Rot problem. As more context accumulates, Claude Code tends to forget initial context which typically includes the most important requirements and high-level plans—and instead focuses on implementation details.
To address this, keep the primary context window minimal and focused on high-level orchestration. Delegate low-level details, such as context gathering, sub-planning, and execution, to subagents. While subagents might occasionally gather redundant information by using more tokens, this approach ensures the main agent remains focused on high-level planning without distraction.
Subagents maintain contexts isolated from the main conversation. This keeps the main context clean and focused on orchestration.
For effective isolation, define each subagent with a single, clear, and complete responsibility so it can run tasks independently within a single context window.
One of the best practices is to create a subagent only when there are clear benefits to separating context.
Skills package domain knowledge (instructions, scripts, resources) for specific tools and file types.
However, it might mess up the context window with low-level details. Therefore, skills has to be called carefully with proper context window management. One of the best practices is to call skills by subagents which keep isolated contexts about low-level details.
Claude is a highly capable model. There’s no reason to constrain its reasoning with overly prescriptive instructions. Keep guidance concise and let it infer details and approach as needed.
- claude-code-plugins - A core plugins for development such as PR review, feature development, etc.
- anthropic-agent-skills - A collection of core skills for Claude Code agents.
Contributions are welcome! Whether you have ideas for plugin designs, feedback on existing agents, or suggestions for new workflows, please open an issue or submit a pull request.
Use scripts/dev-install.sh to locally install the plugins for development.
./scripts/dev-install.sh