Claude Code Mastering

A batteries-included .claude/ configuration boilerplate for Claude Code. Drop it into any project and get a structured, opinionated development workflow powered by MCP tools, slash commands, custom agents, and more.

How It Works

Every command you give flows through three MCP servers working together.

1. You Give a Command A task, bug fix, feature request, or question — anything you need Claude to do.
2. Sequential Thinking Analyzes Breaks down the problem step-by-step, consulting Context7 for up-to-date library docs when needed.
3. Serena Executes Loads previous context from memory, navigates and edits code with LSP-powered tools, then saves new context.

One-Click Setup

The fastest way to get started. Copy the prompt below and paste it into Claude Code inside your project directory.

Set up the Claude Code Mastering boilerplate in this project. Follow these steps:

1. Clone the boilerplate repo to a temp directory and copy the config files:
   - git clone https://github.com/yusupsupriyadi/claude-code-mastering.git /tmp/claude-code-mastering
   - Copy the .claude/ folder, .mcp.json, and CLAUDE.md from /tmp/claude-code-mastering into this project root
   - Remove the temp clone: rm -rf /tmp/claude-code-mastering

2. After copying, ask me the following questions to customize the boilerplate:
   a. "What is your project name?" → Replace all "your-project-" placeholders in .claude/ files
   b. "What tech stack are you using?" (e.g., Python/FastAPI backend, React frontend, etc.)
      → Remove irrelevant components:
        - No backend? Delete .claude/commands/backend/, remove backend section from .claude/rules/deployment.md
        - No frontend? Delete .claude/commands/frontend/, .claude/rules/frontend.md, .claude/agents/frontend-builder.md
   c. "What is your preferred communication language?" → Update the language setting in CLAUDE.md (default is Bahasa Indonesia)

3. After customization, show me a summary of:
   - Which files were copied
   - Which components were removed (if any)
   - Which placeholders were replaced
   - What slash commands are available (list all /command-name)

4. Finally, verify the setup by checking that .claude/ folder exists with the correct structure.

Manual Setup

For those who prefer full control over the installation process.

Prerequisites

# Option A: Clone as a starting point for a new project
git clone https://github.com/yusupsupriyadi/claude-code-mastering.git my-project
cd my-project
rm -rf .git && git init

# Option B: Copy into an existing project
git clone https://github.com/yusupsupriyadi/claude-code-mastering.git /tmp/ccm
cp -r /tmp/ccm/.claude your-project/.claude
cp /tmp/ccm/.mcp.json your-project/.mcp.json
cp /tmp/ccm/CLAUDE.md your-project/CLAUDE.md
rm -rf /tmp/ccm

.claude/rules/
├── backend.md          # Backend dev rules (Docker, testing)
├── frontend.md         # Frontend dev rules (npm, builds)
├── deployment.md       # Pre-deploy checklists
├── documentation.md    # Documentation standards
├── code-style.md       # Code style conventions
└── planning.md         # Task planning requirements

# Start Claude Code — MCP servers auto-initialize
claude

# Inside Claude Code, test each MCP:
# Sequential Thinking — automatic, used on every request
# Serena — type: /backend:test or ask Claude to analyze code
# Context7 — ask Claude about any library docs

# Inside Claude Code, run:
# > activate_project with your project path
# > onboarding to index the codebase

Project Structure

A well-organized directory layout designed for maximum Claude Code effectiveness.

Slash Commands

Run these inside Claude Code:

Bug Workflow

A streamlined 4-phase workflow for tracking and resolving bugs:

Each phase creates structured documents in .claude/bugs/{bug-name}/.

Spec-Driven Development

A full specification workflow for building features methodically:

MCP Servers

Three MCP servers power the intelligent workflow. All are configured in .mcp.json and auto-start with Claude Code.

Optional

Custom Agents

Specialized sub-agents that Claude delegates to for focused, high-quality work.

Customization Guide

Extend the boilerplate with your own rules, commands, agents, and skills.

Adding New Rules

Create a new .md file in .claude/rules/:

# Your Custom Rules

- Follow project naming conventions
- Write tests for all new features
- Use dependency injection pattern

Adding New Commands

Create a new .md file in .claude/commands/:

---
description: Run database seed script
allowed-tools: Bash(docker compose exec:*)
argument-hint: "[environment: dev|test]"
---

Seed the database for the specified environment.

Adding New Agents

Create a new .md file in .claude/agents/:

---
name: my-agent
description: What this agent does
model: sonnet
tools: [Read, Grep, Bash(specific:*)]
---

## Agent Instructions

Your detailed instructions here...

Adding New Skills

Create a new directory in .claude/skills/ with a SKILL.md:

---
name: my-skill
description: Auto-activates when [trigger]
allowed-tools: Read, Write, Grep
---

## Skill Instructions

Your skill's specialized knowledge...

Removing Unused Components

• No backend? Delete commands/backend/, remove backend section from rules/deployment.md
• No frontend? Delete commands/frontend/, rules/frontend.md, agents/frontend-builder.md

Requirements

Tools needed for each stack component.

FAQ