claude-code-learning

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: claude-code-learning
classification: capability
classification-reason: Highly likely to be subsumed by model's native capabilities
deprecation-risk: high
effort: low
description: |
  Claude Code learning — configure and optimize Claude Code settings, tips, and workflows.
  Triggers: learn, setup, claude code, optimize
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}"
---

# 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

## Agent Teams (v1.5.1)

Parallel PDCA execution with multiple AI agents working simultaneously.

Requirements:
  CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

Usage:
  /pdca team {feature}     Start team mode
  /pdca team status        Check teammate progress
  /pdca team cleanup       End team session

Team composition by level:
  Dynamic:    2 teammates (developer, qa)
  Enterprise: 4 teammates (architect, developer, qa, reviewer)
```

### 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.