prompt-optimizer

原文涵盖的主题

• Prompt Optimizer
• When to Use
• Do Not Use When
• How It Works
• Analysis Pipeline
• Phase 0: Project Detection
• Phase 1: Intent Detection
• Phase 2: Scope Assessment

Analyze a draft prompt, critique it, match it to ECC ecosystem components, and output a complete optimized prompt the user can paste and run. User says "optimize this prompt", "improve my prompt", "rewrite this prompt" User says "help me write a better prompt for..." User says "what's the best way to ask Claude Code to..." User says "优化prompt", "改进prompt", "怎么写prompt", "帮我优化这个指令" User pastes a draft prompt and asks for feedback or enhancement User says "I don't know how to prompt for this" User says "how should I use ECC for..." User explicitly invokes /prompt-optimize User wants the task done directly (just execute it) User says "优化代码", "优化性能", "optimize this code", "optimize performance" — these are refactoring tasks, not prompt optimization User is asking about ECC configuration (use configure-ecc instead) User wants a skill inventory (use skill-stocktake instead) User says "just do it" or "直接做" Advisory only — do not execute the user's task. Do NOT write code, create files, run commands, or take any implementation action. Your ONLY output is an analysis plus an optimized prompt. If the user says "just do it", "直接做", or "don't optimize, just execute", do not switch into implemen

这里只展示节选，请以完整原文和当前要求为准。