القائمة
Switch between optimized workflow modes — design, saas, marketing, research, writing, night, yolo, unhinged, caveman, normal
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Visual, filterable catalog of every CC Commander skill, agent, and command. Cascades from broad category picker into 4-at-a-time detail cards. Use when the user types…
Visual, filterable catalog of every CC Commander skill, agent, and command. Cascades from broad category picker into 4-at-a-time detail cards. Use when the user types…
Build something new — web app, API, CLI, or mobile. Guided spec interview routes to the right template, then scaffolds. Use when: 'build something', 'new project', 'create app'.
Show what changed in the latest CC Commander update. Reads CHANGELOG.md and renders the most-recent version section in a digestible summary. Use when the user types…
CC Commander interactive discovery tool. Renders a live flow diagram of every /ccc-* workflow by reading the plugin directly as single source of truth. Use when the…
Adversarial multi-agent debate (antfooding): fan out N agents that argue and critique a design or diff from distinct lenses until issues resolve, then synthesize a verdict.
| name | mode-switcher |
| description | Switch between optimized workflow modes — design, saas, marketing, research, writing, night, yolo, unhinged, caveman, normal |
| tags | ["mode","workflow","configuration"] |
One command to reconfigure Claude Code for a specific workflow. Loads skills, sets behavioral rules, adjusts permissions.
A mode is a preset configuration that:
Modes are not exclusive — you can switch at any time. Switching modes replaces the previous mode's instructions.
/cc mode <name> # Switch to a mode
/cc mode # Show current mode + list all
/cc mode normal # Reset to default
Or reference naturally in conversation: "switch to design mode", "go yolo", "enter night mode".
| # | Mode | Loads | Permission | Key Behavior |
|---|---|---|---|---|
| 1 | normal | — | acceptEdits | Default balanced workflow. Standard coding with full confirmation. |
| 2 | design | ccc-design | acceptEdits | Visual-first. Impeccable suite. Component-focused. Screenshots/previews encouraged. |
| 3 | saas | ccc-saas + ccc-devops | acceptEdits | Full-stack SaaS. Auth, billing, DB, CI/CD. Production-readiness focused. |
| 4 | marketing | ccc-marketing + ccc-seo | acceptEdits | Content creation, SEO, CRO. Copywriting focused. A/B test suggestions. |
| 5 | research | ccc-research | acceptEdits | Parallel agent research. Extended thinking. Deep analysis. Source attribution. |
| 6 | writing | — | acceptEdits | Minimal tech noise. Prose-focused. Grammar/style. Long-form content. |
| 7 | night | all relevant CCC domains | autoAccept | Fully autonomous overnight. Auto-checkpoints. Self-verify. Detailed logs. |
| 8 | yolo | user's choice | autoAccept | Max speed. Skip confirmations. Hooks as safety net. Minimal explanation. |
| 9 | unhinged | all CCC domains | autoAccept | YOLO + max creativity. Bold architecture. Aggressive refactoring. Comprehensive testing. |
| 10 | caveman | — | acceptEdits | Token-saving mode. ~75% less output tokens. Three levels: lite/full/ultra. Code stays normal. |
The baseline. No special skills loaded, standard confirmation flow. Use this when switching away from a specialized mode or when doing general-purpose work that doesn't fit a category.
When to use: General coding, maintenance, debugging, mixed tasks.
Activates the full ccc-design ecosystem: animations, visual effects, Impeccable polish suite, landing page builder, component design. Claude prioritizes visual output, suggests screenshots/previews, and thinks component-first.
When to use: UI work, landing pages, design systems, animations, visual polish.
Loads ccc-saas (auth, billing, DB, API, frontend, growth) plus ccc-devops (CI/CD, infrastructure, monitoring). Claude thinks in production terms — error handling, scaling, security, billing edge cases.
When to use: Building or extending SaaS products. Full-stack feature work.
Combines ccc-marketing (content, email, ads, social) with ccc-seo (technical SEO, content SEO, analytics). Claude writes like a marketer — compelling copy, conversion-focused, data-driven recommendations.
When to use: Content creation, SEO optimization, email campaigns, landing page copy, CRO.
Activates ccc-research for deep analysis workflows. Claude uses extended thinking, spawns parallel research agents, cites sources, and produces structured findings.
When to use: Technical research, competitive analysis, architecture evaluation, deep dives.
No special skills — just behavioral tuning. Claude minimizes technical jargon, focuses on prose quality, grammar, flow, and structure. Ideal for long-form content, documentation, blog posts.
When to use: Blog posts, documentation, copywriting, any prose-heavy work.
The overnight workhorse. All relevant CCC domains loaded, full auto-accept permissions. Claude auto-checkpoints every 5 edits, self-verifies before marking tasks done, saves session before compacting, and writes detailed execution logs.
When to use: Large batch tasks you want done by morning. Set task list, enter night mode, walk away.
Full auto-accept with whatever skills you choose. Claude skips explanations, minimizes confirmation overhead, and just builds. Hooks remain active as the safety net.
When to use: When you know exactly what you want and speed matters more than discussion.
Everything YOLO offers plus maximum creative freedom. All CCC domains loaded. Claude makes bold architectural choices, aggressively refactors, and pushes boundaries — but backs it up with comprehensive testing.
When to use: Greenfield projects, major refactors, creative exploration where you trust Claude to make big moves.
Ultra-compressed output mode. Strips articles, filler, pleasantries, and hedging from all prose responses. Technical content — code blocks, error messages, exact terms — is untouched. Three intensity levels: lite (no fluff, grammar intact), full (fragments, no articles), ultra (telegraphic, abbreviations, arrow notation). Stacks with any other mode.
When to use: Long debugging sessions, architecture discussions, any work where explanation volume is high and you want to cut output costs by ~65-75%. Deactivate with /caveman off.
When a mode is activated:
modes/{name}.mdWhen switching between modes, the previous mode's instructions are fully replaced (not layered).
Each mode is defined in modes/{name}.md with: