CC-BEST(1)

NAME

cc-best โ€” ๐ŸŽญ cc-best: Turn Claude Code into a full dev team โ€” PMโ†’Leadโ†’Devโ†’QA autonomous workflow. 40 commands ยท 17 skills ยท 8โ€ฆ

SYNOPSIS

$https://github.com/xiaobei930/cc-best/releases

INFO

39 stars
2 forks
0 views

DESCRIPTION

๐ŸŽญ cc-best: Turn Claude Code into a full dev team โ€” PMโ†’Leadโ†’Devโ†’QA autonomous workflow. 40 commands ยท 17 skills ยท 8 agents ยท 33 rules ยท 21 hooks ยท auto-learning pipeline. | ไธ€ไธชๆ’ไปถ๏ผŒๅฎŒๆ•ดๅผ€ๅ‘ๅ›ข้˜Ÿใ€‚

README

CC-Best

Role-Driven Development Workflow for Claude Code

License: MIT Release Validate Plugin GitHub stars Homepage

English | ไธญๆ–‡ | ๐ŸŒ Homepage


Transform Claude into a complete development team. From product requirements to code review โ€” one plugin, full workflow.

44 commands ยท 19 skills ยท 8 agents ยท 35 rules ยท 19 hooks

CC-Best autonomous iteration demo

Quick Start โ€ข Features โ€ข Workflow โ€ข Commands โ€ข FAQ

Why CC-Best?

๐ŸŽฏ The Problem: Claude Code is powerful, but configuring workflows, coding standards, and safety rules from scratch takes hours.

โœจ The Solution: Pre-configured roles (PM โ†’ Lead โ†’ Designer โ†’ Dev โ†’ QA) that mirror real team collaboration, with safety guardrails built-in.

โšก Quick Start

# Add marketplace and install
/plugin marketplace add xiaobei930/cc-best
/plugin install cc-best@xiaobei930

Verify installation (30 seconds)

/cc-best:status

Start using

/cc-best:iterate "implement user authentication"

๐Ÿ’ก Enable Hooks: After installation, run /cc-best:setup --hooks to activate safety guards and automation hooks. See Hooks Configuration for details.

Plugin vs Clone: Command Format

InstallationCommand formatExample
Plugin โญ/cc-best:command/cc-best:iterate "add feature"
Clone/command/iterate "add feature"

๐Ÿ’ก Recommended: Install via plugin for automatic updates and easier management. All documentation uses plugin format (/cc-best:xxx). Clone users: run convert-to-local.js.

Setup Demo

๐Ÿ“ฆ Alternative: Clone for full customization
git clone https://github.com/xiaobei930/cc-best.git .claude
cd .claude && bash scripts/shell/init.sh

# Convert command format from /cc-best:xxx to /xxx
node scripts/node/convert-to-local.js

Use clone when you need to customize all files in your repo.

โš ๏ธ Important: All documentation uses plugin format (/cc-best:xxx). Run the conversion script to update to local format (/xxx).

๐Ÿ—‘๏ธ Uninstall
# Remove the plugin
/plugin uninstall cc-best@xiaobei930

# Remove marketplace (optional)
/plugin marketplace remove xiaobei930/cc-best

No files are left behind.

What Happens Next?

After running /cc-best:iterate "implement user authentication", Claude will:

1. ๐Ÿ“‹ /cc-best:pm     โ†’ Analyze requirements, create task breakdown
2. ๐Ÿ—๏ธ /cc-best:lead   โ†’ Design technical solution
3. ๐Ÿ’ป /cc-best:dev    โ†’ Write code, create tests
4. ๐Ÿงช /cc-best:qa     โ†’ Run tests, verify quality
5. โœ… /cc-best:commit โ†’ Commit changes with proper message

You just watch. Intervene only when needed.

Common Workflows

I want to...CommandWhat Claude does
Build a feature/cc-best:iterate "add dark mode toggle"Full cycle: plan โ†’ code โ†’ test โ†’ commit
Fix a bug/cc-best:iterate "fix login timeout issue"Investigate โ†’ fix โ†’ verify โ†’ commit
Review code/cc-best:pm "review recent changes"Analyze code, suggest improvements
Learn the codebase/cc-best:pairStep-by-step exploration with explanations

Who Is This For?

You are...Recommended modeWhy
Team with multiple rolesFull workflowPM โ†’ Lead โ†’ Dev โ†’ QA mirrors your process
Solo developer/cc-best:iterateLet Claude handle the boring parts
Learning Claude Code/cc-best:pairUnderstand each step before proceeding
Need quick fixesDirect commands/cc-best:dev "fix the typo" for simple tasks

โœจ Core Features

FeatureWhat it does
๐ŸŽญ Role-Based WorkflowPM โ†’ Lead โ†’ Designer โ†’ Dev โ†’ QA โ€” complete development cycle
๐Ÿ”„ Autonomous Mode/cc-best:iterate runs tasks without intervention until completion
๐Ÿ›ก๏ธ Safety HooksBlocks rm -rf /, git push --force, and other risky commands
๐Ÿ“ Multi-Language Standards8-dir layered structure: common + Python/frontend/Java/C#/C++/embedded/UI rules
๐Ÿง  Memory BankPersists progress and decisions across sessions
๐Ÿ‘ฅ Pair Programming/cc-best:pair โ€” step-by-step collaboration with 5 confirmation checkpoints
๐Ÿ”— Knowledge Pipelineobserve โ†’ analyze โ†’ learn โ†’ evolve โ€” self-improving knowledge loop
๐ŸŒ Cross-PlatformWindows, macOS, Linux โ€” auto-detects package manager

While CC-Best is built for Claude Code, the methodology (Dao-Fa-Shu-Qi) and role-driven patterns are framework-agnostic and can be adapted for other AI coding assistants.

What Makes CC-Best Different

๐ŸŽญ Role-Driven Development Pipeline

Not just a prompt template collection โ€” CC-Best simulates real team collaboration:

  • 7 roles with clear boundaries: PM โ†’ Lead โ†’ Designer โ†’ Dev โ†’ QA โ†’ Verify โ†’ Commit
  • Each role has explicit MUST/SHOULD/NEVER rules, output templates, and handoff protocols
  • Automatic flow: PM creates REQ โ†’ Lead reviews & creates DES/TSK โ†’ Dev implements โ†’ QA validates
  • Downstream correction (A3): Lead can adjust PM decisions; QA distinguishes implementation bugs from requirement assumption errors
  • Document traceability: REQ-XXX โ†’ DES-XXX โ†’ TSK-XXX numbered chain
๐Ÿ”„ Autonomous Iteration Engine

/cc-best:iterate enables fully autonomous development:

Read progress.md โ†’ Select role โ†’ Execute โ†’ Verify โ†’ Commit โ†’ Next task (no waiting)
  • Smart role selection: 8 state conditions determine which role activates
  • A1-A5 decision principles: Context inference (A1), decision recording (A2), downstream correction (A3), MVP fallback (A4), issue classification (A5)
  • 4 strict stop conditions: All tasks done, user interrupt, fatal error, external dependency
  • Cross-session continuity: memory-bank + progress.md rolling window
๐Ÿ”— Self-Evolving Knowledge Pipeline

CC-Best learns from your development patterns:

observe โ†’ analyze โ†’ learn โ†’ evolve
  • observe: observe-patterns.js hook automatically tracks tool usage patterns
  • analyze: /cc-best:analyze mines git history and usage data
  • learn: /cc-best:learn extracts reusable knowledge
  • evolve: /cc-best:evolve generates new commands, skills, or agents from learned patterns

๐Ÿ“ Directory Structure

your-project/
โ”œโ”€โ”€ CLAUDE.md          # Project constitution
โ”œโ”€โ”€ commands/          # 44 slash commands
โ”œโ”€โ”€ skills/            # 19 development skills
โ”œโ”€โ”€ agents/            # 8 specialized agents
โ”œโ”€โ”€ rules/             # 33 coding standards (8 dirs)
โ”œโ”€โ”€ hooks/             # Safety hooks
โ”œโ”€โ”€ scripts/           # Automation (node/python/shell)
โ”œโ”€โ”€ memory-bank/       # Progress & architecture docs
โ””โ”€โ”€ .claude/           # Claude Code config
๐Ÿ“‚ Detailed structure
DirectoryContents
commands/Role commands (pm, lead, dev, qa), Mode commands (iterate, pair), Tool commands (build, test, commit)
skills/Backend, Frontend, Testing, Security, DevOps, Architecture, Git
agents/architect, build-error-resolver, code-reviewer, code-simplifier, planner, requirement-validator, security-reviewer, tdd-guide
rules/35 rules in 8 dirs: common/ + python/, frontend/, java/, csharp/, cpp/, embedded/, ui/
scripts/Cross-platform hooks in Node.js (default), with Python/Bash alternatives
memory-bank/progress.md (rolling window), architecture.md, tech-stack.md

๐Ÿ”„ Workflow

Standard Development Cycle

flowchart LR
    PM["/pm<br/>Requirements"] --> Clarify["/clarify<br/>Clarify"]
    Clarify --> Lead["/lead<br/>Design"]
    Lead --> Designer["/designer<br/>UI Design"]
    Designer --> Dev["/dev<br/>Implement"]
    Dev --> QA["/qa<br/>Test"]
    QA --> Verify["/verify<br/>Verify"]
    Verify --> Commit["/commit<br/>Commit"]
    Commit --> Clear["/clear<br/>Clear Context"]
    Clear -.->|Loop| PM

Three Development Modes

ModeCommandUse CaseCharacteristics
Autonomous Iteration/cc-best:iterateClear task listFully autonomous, no intervention needed
Pair Programming/cc-best:pairLearning, sensitive operationsConfirm each step, human-machine collaboration
Long-Running Loop/cc-best:cc-ralphHour-level batch tasksRequires ralph-loop plugin (/plugin install ralph-loop@claude-plugins-official)
How /cc-best:iterate selects roles automatically
Current StateRole SelectedAction
No requirements doc/cc-best:pmRequirement analysis
REQ has low-confidence items/cc-best:clarifyRequirement clarification
Has REQ, no design/cc-best:leadTechnical design
Has design, frontend tasks/cc-best:designerUI design guidance
Has tasks to implement/cc-best:devCoding implementation
Code ready for verification/cc-best:verifyBuild + type + lint + test + security
Verification passed/cc-best:qaFunctional acceptance

Core behavior: Task complete โ†’ Update progress.md โ†’ Read next task โ†’ Execute immediately (no waiting).

Stop conditions: All tasks done | User interrupt (Ctrl+C) | Fatal error | External dependency needed.

How /cc-best:pair collaboration works

5 mandatory confirmation checkpoints:

CheckpointExample
Understanding"I understand you need X. Correct?"
Design choice"Option A or B? I recommend A because..."
Destructive action"About to delete X. Confirm?"
External call"Will call production API. Proceed?"
Commit"Commit message: '...'. OK?"

Learning mode: /cc-best:pair --learn "teach me unit testing" โ€” Claude explains every step in detail.

Safe autonomy: Even in pair mode, Claude can freely read files, search code, run tests, and format code.

๐Ÿ“– Detailed usage guide: See MODES.md for comprehensive documentation on each mode, including when to use, how to control, and best practices.


๐Ÿ“‹ Command Reference

44 commands organized into categories:

CategoryCommandsPurpose
Role/cc-best:pm, /cc-best:lead, /cc-best:dev, /cc-best:qa, /cc-best:designer, /cc-best:clarify, /cc-best:verifyDevelopment workflow roles
Mode/cc-best:iterate, /cc-best:pair, /cc-best:cc-ralph, /cc-best:mode, /cc-best:modelAutonomous/pair modes & model strategy
Build/cc-best:build, /cc-best:test, /cc-best:run, /cc-best:fixBuild and test automation
Git/cc-best:commit, /cc-best:pr, /cc-best:git-guideVersion control
Context/cc-best:compact-context, /cc-best:checkpoint, /cc-best:catchup, /cc-best:context, /cc-best:memorySession management
Quality/cc-best:cleanup, /cc-best:docs, /cc-best:learn, /cc-best:analyze, /cc-best:evolveCode quality & knowledge
Ops/cc-best:fix-issue, /cc-best:release, /cc-best:service, /cc-best:hotfixIssue fix, release, hotfix, services
Setup/cc-best:setup, /cc-best:setup-pm, /cc-best:status, /cc-best:self-check, /cc-best:confidence-check, /cc-best:security-auditConfiguration & diagnostics

๐Ÿ“– Full reference: See COMMANDS.md for all parameters and usage examples.


๐Ÿ› ๏ธ Skills

19 development skills organized by domain:

DomainSkillsCoverage
Backendbackend, api, databasePython, TS, Java, Go, C#
Frontendfrontend, nativeWeb + iOS/macOS/Tauri
Qualityquality, testing, security, debugTDD, OWASP, profiling
Architecturearchitecture, devops, gitADR, CI/CD, branching
RoutingmodelTaskโ†’model recommendation
Sessionsession, learning, compact, explorationLifecycle + knowledge management
Researchsearch-first, second-opinionSearch strategy, cross-validation

๐Ÿ“– Full reference: See skills/README for detailed skill documentation.


๐Ÿ—๏ธ Architecture Overview

CC-Best uses a four-tier architecture:

flowchart TB
    subgraph User["๐Ÿ‘ค You"]
        CMD["/cc-best:iterate 'add feature'"]
    end
subgraph Commands[&quot;๐Ÿ“‹ Commands (44)&quot;]
    PM[&quot;/pm&quot;] --&gt; Lead[&quot;/lead&quot;] --&gt; Dev[&quot;/dev&quot;] --&gt; QA[&quot;/qa&quot;]
end

subgraph Skills[&quot;๐Ÿ› ๏ธ Skills (19)&quot;]
    S1[&quot;backend ยท frontend ยท testing ยท security&quot;]
    S2[&quot;architecture ยท devops ยท git&quot;]
    S3[&quot;learning ยท compact ยท exploration&quot;]
end

subgraph Agents[&quot;๐Ÿค– Agents (8)&quot;]
    A1[&quot;architect ยท planner ยท code-reviewer&quot;]
    A2[&quot;code-simplifier ยท security-reviewer&quot;]
    A3[&quot;tdd-guide ยท build-error-resolver ยท requirement-validator&quot;]
end

subgraph Safety[&quot;๐Ÿ›ก๏ธ Safety Hooks (18)&quot;]
    H1[&quot;PreToolUse: validate, secrets, protect&quot;]
    H2[&quot;PostToolUse: format, typecheck, observe&quot;]
end

CMD --&gt; Commands
Commands -.-&gt;|&quot;auto-inject&quot;| Skills
Commands -.-&gt;|&quot;delegate&quot;| Agents
Commands -.-&gt;|&quot;guard&quot;| Safety

LayerTriggerPurpose
CommandsUser types /xxxRole workflow, user-initiated actions
SkillsAuto-injectedBest practices, coding standards
AgentsTask tool delegationSpecialized sub-tasks (review, planning)
HooksLifecycle eventsSafety guards, auto-format, pattern learning

8 specialized agents: architect, build-error-resolver, code-reviewer, code-simplifier, planner, requirement-validator, security-reviewer, tdd-guide

๐Ÿ“ Full documentation: See ARCHITECTURE.md for component relationships and call chains.

๐Ÿค– Agent details: See agents/README for agent capabilities and invocation.


๐Ÿ”Œ Plugin Compatibility

CC-Best is designed to work seamlessly with official Claude Code plugins. Our built-in agents and skills complement (not replace) official plugins.

Relationship with Official Plugins

CC-Best ContentOfficial PluginRelationship
code-reviewer agentcode-review pluginBuilt-in: lightweight local version; Official: more powerful with auto-trigger
security-reviewer agentsecurity-guidanceBuilt-in: OWASP checklist; Official: automatic security analysis
code-simplifier agentcode-simplifierSimilar function; official plugin has more context
/cc-best:cc-ralph commandralph-loop pluginCC-Best wrapper; requires plugin for cross-session persistence
hookify exampleshookify pluginBuilt-in: examples; Official: full hook management

Recommended Plugin Configuration

{
  "enabledPlugins": {
    "code-review@claude-plugins-official": true,
    "hookify@claude-plugins-official": true,
    "security-guidance@claude-plugins-official": true
  }
}

When to Use Which

  • No plugins installed: Built-in agents/skills work standalone
  • With plugins: Use official plugins for advanced features, CC-Best for quick local checks
  • Best practice: Install official plugins, use built-in agents for immediate feedback, official plugins for deep analysis

โš™๏ธ Customization Guide

Adding New Rules

Create a file in rules/:

---
paths:
  - "**/*.your-ext"
---

Rule Title

Rule Content

...

Adding New Commands

Create a file in commands/:

---
allowed_tools:
  - Read
  - Edit
  - Write
  - Bash
---

/your-command - Command Name

Responsibilities

...

Execution Steps

  1. ...
  2. ...

Configuring Hooks

Edit .claude/settings.local.json:

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "python scripts/your-script.py",
            "timeout": 5
          }
        ]
      }
    ]
  }
}

Pre-configured Hooks

โš ๏ธ Important: Hooks Require Manual Setup

Due to a known Claude Code issue, plugin hooks are disabled by default. To enable the safety guards and automation hooks, run:

/cc-best:setup --hooks

This command configures hooks with absolute paths. See the FAQ for more details.

All hooks default to Node.js for cross-platform compatibility. Python/Bash alternatives available in scripts/.

TriggerFunctionScript (Node.js)
PreToolUseValidate dangerous commandsvalidate-command.js
PreToolUseConfirm before git pushpause-before-push.js
PreToolUseProtect sensitive filesprotect-files.js
PreToolUseBlock random .md creationblock-random-md.js
PreToolUseLong-running task warninglong-running-warning.js
PostToolUseAuto-format codeformat-file.js
PostToolUseCheck console.logcheck-console-log.js
PostToolUseTypeScript type checktypescript-check.js
SessionStartSession health checksession-check.js
PreCompactSave state before compactpre-compact.js

๐Ÿ’ก Best Practices

1. Keep CLAUDE.md Concise

  • Keep it under 100 lines
  • Put detailed specifications in rules/

2. Use the Memory Bank

  • Update progress.md after each task completion
  • Record important decisions in architecture.md

3. Context Management

  • Normal mode: Use /clear frequently to avoid context overflow
  • /cc-best:iterate mode: Don't clear manually, maintain loop continuity

4. Don't Overload MCP

  • Enable no more than 10 MCP servers per project
  • Use disabledMcpServers to disable unused ones

5. Regular Cleanup

  • Delete unused language rules
  • Remove unused commands

6. MCP Temporary Directory Management

MCP tools auto-create temporary directories in your project:

DirectorySourcePurpose
.playwright-mcp/MCP auto-createdPlaywright MCP temporary files
.claude/mcp-data/MCP auto-createdMCP shared data
*-mcp/MCP auto-createdOther MCP tool directories
.claude/screenshots/Template-definedManually saved screenshots (meaningful)

Cleanup Script: Use cleanup.sh for regular maintenance:

# Preview files to delete (dry run)
bash scripts/shell/cleanup.sh --dry-run

Clean files older than 7 days (default)

bash scripts/shell/cleanup.sh

Clean files older than 3 days

bash scripts/shell/cleanup.sh --days 3

Clean all MCP temporary files

bash scripts/shell/cleanup.sh --all


โ“ FAQ

๐Ÿ“– Full FAQ: See FAQ.md for comprehensive troubleshooting guides.

Quick Answers

Hooks not working?

Run /cc-best:setup --verify to diagnose. Common fixes:

  • Clone users: cp .claude/settings.local.json.example .claude/settings.local.json
  • Plugin users: Run /cc-best:setup --hooks to configure absolute paths
  • Windows: See FAQ.md for ${CLAUDE_PLUGIN_ROOT} workarounds
/cc-best:iterate vs /pair?
ModeControlUse Case
/cc-best:iterateFully autonomousClear task list
/cc-best:pairConfirm each stepLearning, sensitive ops
How to stop /iterate?
  • Interrupt: Press Ctrl+C (or Esc in some terminals)
  • Pause: Type anything โ€” Claude will wait for your input
  • Resume: Just continue the conversation

Claude saves progress to memory-bank/progress.md, so you can always resume later.

What if /cc-best:qa fails?

Claude will:

  1. Analyze the failure
  2. Return to /cc-best:dev to fix the issue
  3. Re-run /cc-best:qa to verify

If stuck after 3 attempts, Claude will ask for your input. You can:

  • Provide hints: "Try checking the database connection"
  • Skip the test: "Skip this test for now"
  • Take over: "I'll fix this manually"
MCP configuration?

Edit .claude/settings.local.json:

{ "enabledMcpjsonServers": ["memory", "sequential-thinking"] }

Best practice: Enable โ‰ค10 MCP servers per project.

CC-Best vs Superpowers?

Both are excellent. Choose based on your needs:

ScenarioRecommendedWhy
Team collaborationCC-BestRole workflow (PMโ†’Leadโ†’Devโ†’QA)
Multi-language stackCC-Best7 language coding standard dirs
Chinese teamCC-BestBilingual docs
Solo developerSuperpowersLighter, git worktree automation
Need git worktreeSuperpowersAuto-creates isolated branches

๐Ÿ’ก They can coexist! Use CC-Best for workflows, Superpowers for git automation.


๐Ÿ”ง Requirements

DependencyVersionNotes
Claude CodeLatest recommendedHooks require recent versions
Node.js16+For cross-platform hooks (default)
Python3.8+For some hook scripts
Bash/Git BashAny versionOptional for bash hooks

Optional MCP Servers

Some commands use MCP (Model Context Protocol) tools for enhanced functionality:

MCP ServerUsed ByPurpose
Playwright/cc-best:designer, /cc-best:dev, /cc-best:pmBrowser automation for UI testing and screenshots
Firecrawl/cc-best:pm, /cc-best:leadWeb scraping for requirement research

Note: These are optional. Commands work without MCP servers but with reduced functionality. Install via Claude Code settings: Settings > MCP Servers

Supported Languages

LanguageRule FileFormatterTest Framework
Pythonpython-style.mdBlack + isortpytest
Vue/TS/JSfrontend-style.mdPrettierVitest
C++cpp-style.mdclang-formatGoogle Test
Javajava-style.mdgoogle-java-formatJUnit
C#csharp-style.mddotnet formatxUnit/NUnit
Gobackend/go.mdgofmttesting
Swiftnative/ios.mdswift-formatXCTest

๐Ÿ“š References

Official Resources

Plugin Documentation

Community Projects


๐ŸŒ Note on Internal Files

CC-Best's internal files (commands/, rules/, skills/) are written in Chinese. This is intentional:

  • Claude understands Chinese - All Claude models can read and follow Chinese instructions perfectly
  • No translation burden - Maintaining dual-language internal files would be impractical
  • Focus on users - The README (this file) is fully English for international users

If you prefer English internal files, community contributions for English translations are welcome!


๐Ÿค Contributing

Contributions are welcome! See CONTRIBUTING.md for details.

Contribution TypeDescription
โญ StarShow your support
๐Ÿ› Bug ReportReport issues
๐Ÿ’ก Feature RequestSuggest features
๐Ÿ“ DocumentationImprove docs
๐Ÿ”ง CodeAdd commands, rules, skills

๐Ÿ“„ License

MIT License - Free to use and modify


๐ŸŒ Visit Homepage ยท โญ Star on GitHub

If CC-Best helps you, please give it a โญ Star!

Star History

Star History Chart

SEE ALSO

clihub3/4/2026CC-BEST(1)