项目文件夹

文件
NomenAK f16ce67a1f Refactor SuperClaude Modes and MCP documentation for concise behavioral guidance
Transform 10 framework files from verbose technical documentation into concise
behavioral guides focusing on Claude's cognitive enhancement:

Modes/ - Behavioral mindset modifiers:
- MODE_Token_Efficiency: Symbol systems and compression communication (360→75 lines)
- MODE_Introspection: Meta-cognitive analysis and self-reflection (266→39 lines)
- MODE_Task_Management: Orchestration and delegation mindset (302→41 lines)
- MODE_Brainstorming: Collaborative discovery dialogue (84→44 lines)

MCP/ - External tool decision guides:
- MCP_Context7: Library documentation lookup (98→30 lines)
- MCP_Sequential: Multi-step reasoning engine (103→33 lines)
- MCP_Magic: UI component generation (93→31 lines)
- MCP_Playwright: Browser automation (102→32 lines)
- MCP_Morphllm: Pattern-based editing (159→31 lines)
- MCP_Serena: Semantic understanding and memory (207→32 lines)

Enhanced structure: Purpose, Activation Triggers, Behavioral Changes/Choose When,
Outcomes/Works Best With, Examples. Focus on WHEN to shift cognitive approaches
and HOW behavior transforms, not technical implementation details.

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

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-15 16:01:09 +02:00

1.6 KiB

Sequential MCP Server

Purpose: Multi-step reasoning engine for complex analysis and systematic problem solving

Triggers

  • Complex debugging scenarios with multiple layers
  • Architectural analysis and system design questions
  • --think, --think-hard, --ultrathink flags
  • Problems requiring hypothesis testing and validation
  • Multi-component failure investigation
  • Performance bottleneck identification requiring methodical approach

Choose When

  • Over native reasoning: When problems have 3+ interconnected components
  • For systematic analysis: Root cause analysis, architecture review, security assessment
  • When structure matters: Problems benefit from decomposition and evidence gathering
  • For cross-domain issues: Problems spanning frontend, backend, database, infrastructure
  • Not for simple tasks: Basic explanations, single-file changes, straightforward fixes

Works Best With

  • Context7: Sequential coordinates analysis → Context7 provides official patterns
  • Magic: Sequential analyzes UI logic → Magic implements structured components
  • Playwright: Sequential identifies testing strategy → Playwright executes validation

Examples

"why is this API slow?" → Sequential (systematic performance analysis)
"design a microservices architecture" → Sequential (structured system design)
"debug this authentication flow" → Sequential (multi-component investigation)
"analyze security vulnerabilities" → Sequential (comprehensive threat modeling)
"explain this function" → Native Claude (simple explanation)
"fix this typo" → Native Claude (straightforward change)