home / skills / popup-studio-ai / bkit-claude-code / claude-code-learning

claude-code-learning skill

/skills/claude-code-learning

This skill helps you configure and optimize Claude Code across projects, guiding setup, learning paths, and automatic environment adjustments.

npx playbooks add skill popup-studio-ai/bkit-claude-code --skill claude-code-learning

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.7 KB
---
name: claude-code-learning
description: |
  Claude Code learning and education skill.
  Teaches users how to configure and optimize Claude Code settings.
  Works across any project and any language.

  Start learning/setup with "learn" or "setup".

  Use proactively when user is new to Claude Code, asks about configuration,
  or wants to improve their Claude Code setup.

  Triggers: learn claude code, claude code setup, CLAUDE.md, hooks, commands, skills,
  how to configure, 클로드 코드 배우기, 설정 방법, Claude Code 학습,
  クロードコード学習, 设置方法, how do I use claude code,
  aprender claude code, configuración, cómo configurar,
  apprendre claude code, configuration, comment configurer,
  Claude Code lernen, Konfiguration, wie konfigurieren,
  imparare claude code, configurazione, come configurare

  Do NOT use for: actual coding tasks, debugging, or feature implementation.
argument-hint: "[learn|setup|upgrade] [level]"
agent: claude-code-guide
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
  - AskUserQuestion
user-invocable: true
imports:
  - ${PLUGIN_ROOT}/templates/shared/naming-conventions.md
next-skill: null
pdca-phase: null
task-template: "[Learn] Claude Code {level}"
# hooks: Managed by hooks/hooks.json (unified-stop.js) - GitHub #9354 workaround
---

# Claude Code Learning Skill

> Master Claude Code configuration and optimization

## Actions

| Action | Description | Example |
|--------|-------------|---------|
| `learn` | Start learning guide | `/claude-code-learning learn 1` |
| `setup` | Auto-generate settings | `/claude-code-learning setup` |
| `upgrade` | Latest features guide | `/claude-code-learning upgrade` |

### learn [level]

Learning content by level:
- **Level 1**: Basics - Writing CLAUDE.md, Using Plan Mode
- **Level 2**: Automation - Commands, Hooks, Permission management
- **Level 3**: Specialization - Agents, Skills, MCP integration
- **Level 4**: Team Optimization - GitHub Action, Team rule standardization
- **Level 5**: PDCA Methodology - bkit methodology learning

### setup

Auto-generate appropriate settings after analyzing current project:
1. Analyze/generate CLAUDE.md
2. Check .claude/ folder structure
3. Suggest required configuration files

### upgrade

Guide to latest Claude Code features and best practices.

## Learning Levels

### Level 1: Basics (15 min)

```markdown
## What is CLAUDE.md?

A shared knowledge repository for the team. When Claude makes mistakes,
add rules to prevent the same mistakes from recurring.

## Example

# Development Workflow

## Package Management
- **Always use `pnpm`** (`npm`, `yarn` prohibited)

## Coding Conventions
- Prefer `type`, avoid `interface`
- **Never use `enum`** → Use string literal unions

## Prohibited
- ❌ No console.log (use logger)
- ❌ No any type
```

### Level 2: Automation (30 min)

```markdown
## What are Slash Commands?

Execute repetitive daily tasks with `/command-name`.

## Command Location

.claude/commands/{command-name}.md

## PostToolUse Hook

Auto-formatting after code modification:

// .claude/settings.local.json
{
  "hooks": {
    "PostToolUse": [{
      "matcher": "Write|Edit",
      "hooks": [{
        "type": "command",
        "command": "pnpm format || true"
      }]
    }]
  }
}
```

### Level 3: Specialization (45 min)

```markdown
## What are Sub-agents?

AI agents specialized for specific tasks.

## What are Skills?

Domain-specific expert context. Claude auto-references when working on related tasks.

## MCP Integration

Connect external tools (Slack, GitHub, Jira, etc.) via .mcp.json.
```

### Level 4: Team Optimization (1 hour)

```markdown
## PR Automation with GitHub Action

Mention @claude in PR comments to auto-update documentation.

## Team Rule Standardization

1. Manage CLAUDE.md with Git
2. Add rules during PR review
3. Gradually accumulate team knowledge
```

### Level 5: PDCA Methodology

```markdown
## What is PDCA?

Document-driven development methodology.

Plan → Design → Do → Check → Act

## Folder Structure

docs/
├── 01-plan/      # Planning
├── 02-design/    # Design
├── 03-analysis/  # Analysis
└── 04-report/    # Reports

## Learn More

Use /pdca skill to learn PDCA methodology.
```

## Output Format

```
📚 Claude Code Learning Complete!

**Current Level**: {level}
**Learned**: {summary}

🎯 Next Steps:
- Continue learning with /claude-code-learning learn {next_level}
- Auto-generate settings with /claude-code-learning setup
- Check latest trends with /claude-code-learning upgrade
```

## Current Settings Analysis

Files to analyze:
- CLAUDE.md (root)
- .claude/settings.local.json
- .claude/commands/
- .claude/agents/
- .claude/skills/
- .mcp.json

Overview

This skill teaches how to configure and optimize Claude Code for any project and language. It guides users through progressive learning levels, automatic setup of Claude-related files, and practical team and PDCA practices to improve AI-driven development. Start with "learn" or run "setup" to generate recommended settings for your project.

How this skill works

The skill inspects common Claude Code artifacts (CLAUDE.md, .claude settings, commands, agents, skills, and .mcp.json) and provides step-by-step learning or auto-generated configuration suggestions. Use the learn action to follow leveled lessons from basics to PDCA methodology, and use setup to produce a tailored CLAUDE.md and folder suggestions. An upgrade action summarizes new features and best practices.

When to use it

  • You are new to Claude Code and need a guided onboarding path.
  • You want an auto-generated CLAUDE.md and project-specific settings.
  • You need to add automation: commands, hooks, or post-tool hooks.
  • You’re standardizing team rules or adding PR automation for Claude.
  • You want to adopt PDCA methodology for AI‑native development.

Best practices

  • Start at learn level 1 and progress incrementally to level 5 for team adoption.
  • Keep CLAUDE.md under version control and update it with PR-driven rules.
  • Use .claude/commands and PostToolUse hooks for repeatable automation (format, lint, tests).
  • Separate concerns: agents for task specialization, skills for domain context, .mcp.json for external integrations.
  • Document PDCA steps in docs/ with clear plan → design → do → check → act folders.

Example use cases

  • Run /claude-code-learning learn 1 to create an initial CLAUDE.md with dev rules and conventions.
  • Use /claude-code-learning setup to analyze a repo and output a suggested .claude folder layout and settings.local.json hooks.
  • Teach maintainers to add slash commands for CI tasks, auto-formatting, or release notes via .claude/commands.
  • Train a team with level 4 material to enable PR automation and standardized review rules.
  • Adopt level 5 PDCA guidance to structure docs/ and iterate on process improvements.

FAQ

How do I start learning with this skill?

Use the learn action (e.g., "learn 1") to open level 1 content and follow stepwise lessons.

What does setup produce?

Setup analyzes project files and suggests a CLAUDE.md, .claude folder structure, required config files, and hook examples to automate workflows.