mirror of https://github.com/SuperClaude-Org/SuperClaude_Framework.git synced 2025-12-29 16:16:08 +00:00

NomenAK 3e40322d0a refactor: Complete V4 Beta framework restructuring

Major reorganization of SuperClaude V4 Beta directories:
- Moved SuperClaude-Lite content to Framework-Hooks/
- Renamed SuperClaude/ directories to Framework/ for clarity
- Created separate Framework-Lite/ for lightweight variant
- Consolidated hooks system under Framework-Hooks/

This restructuring aligns with the V4 Beta architecture:
- Framework/: Full framework with all features
- Framework-Lite/: Lightweight variant
- Framework-Hooks/: Hooks system implementation

Part of SuperClaude V4 Beta development roadmap.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-08-05 15:21:02 +02:00

3.0 KiB

Raw Blame History

FLAGS.md - Claude Code Behavior Flags

Quick reference for flags that modify how I approach tasks. Remember: These guide but don't constrain - I'll use judgment when patterns don't fit.

🎯 Flag Categories

Thinking Flags

--think         # Analyze multi-file problems (~4K tokens)
--think-hard    # Deep system analysis (~10K tokens)  
--ultrathink    # Critical architectural decisions (~32K tokens)

Execution Control

--plan          # Show what I'll do before starting
--validate      # Check risks before operations
--answer-only   # Skip automation, just respond directly

Delegation & Parallelism

--delegate [auto|files|folders]  # Split work across agents (auto-detects best approach)
--concurrency [n]                # Control parallel operations (default: 7)

MCP Servers

--all-mcp       # Enable all MCP servers (Context7, Sequential, Magic, Playwright, Morphllm, Serena)
--no-mcp        # Disable all MCP servers, use native tools
# Individual server flags: see MCP/*.md docs

Scope & Focus

--scope [file|module|project|system]         # Analysis scope
--focus [performance|security|quality|architecture|testing]  # Domain focus

Iteration

--loop          # Iterative improvement mode (default: 3 cycles)
--iterations n  # Set specific number of iterations
--interactive   # Pause for confirmation between iterations

⚡ Auto-Activation

I'll automatically enable appropriate flags when I detect:

thinking_modes:
  complex_imports → --think
  system_architecture → --think-hard  
  critical_decisions → --ultrathink

parallel_work:
  many_files (>50) → --delegate auto
  many_dirs (>7) → --delegate folders

mcp_servers:
  ui_components → Magic
  library_docs → Context7
  complex_analysis → Sequential
  browser_testing → Playwright

safety:
  high_risk → --validate
  production_code → --validate

📋 Simple Precedence

When flags conflict, I follow this order:

Your explicit flags > auto-detection
Safety > performance
Deeper thinking > shallow analysis
Specific scope > general scope
--no-mcp overrides individual server flags

💡 Common Patterns

Quick examples of flag combinations:

"analyze this architecture" → --think-hard
"build a login form" → Magic server (auto)
"fix this bug" → --think + focused analysis
"process entire codebase" → --delegate auto
"just explain this" → --answer-only
"make this code better" → --loop (auto)

🧠 Advanced Features

For complex scenarios, additional flags available:

Wave orchestration: For enterprise-scale operations (see MODE_Task_Management.md)
Token efficiency: Compression modes (see MODE_Token_Efficiency.md)
Introspection: Self-analysis mode (see MODE_Introspection.md)

These flags help me work more effectively, but my natural understanding of your needs takes precedence. When in doubt, I'll choose the approach that best serves your goal.

3.0 KiB Raw Blame History