mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-03-30 13:43:26 +08:00
83f6d5679c
* feat(skills): add prompt-optimizer skill and /prompt-optimize command Adds a prompt-optimizer skill that analyzes draft prompts, matches them to ECC components (skills/commands/agents), and outputs a ready-to-paste optimized prompt. Advisory role only — never executes the task. Features: - 6-phase analysis pipeline (project detection, intent, scope, component matching, missing context, workflow + model recommendation) - Auto-detects project tech stack from package.json, go.mod, etc. - Maps intents to ECC commands, skills, and agents by type and tech stack - Recommends correct model tier (Sonnet vs Opus) based on task complexity - Outputs Full + Quick versions of the optimized prompt - Hard gate: never executes the task, only produces advisory output - AskUserQuestion trigger when 3+ critical context items are missing - Multi-prompt splitting guidance for HIGH/EPIC scope tasks - Feedback footer for iterative refinement Also adds /prompt-optimize command as an explicit invocation entry point. * fix: keep prompt optimizer advisory-only * fix: refine prompt optimizer guidance --------- Co-authored-by: Affaan Mustafa <affaan@dcube.ai>
39 lines
2.0 KiB
Markdown
39 lines
2.0 KiB
Markdown
---
|
|
description: Analyze a draft prompt and output an optimized, ECC-enriched version ready to paste and run. Does NOT execute the task — outputs advisory analysis only.
|
|
---
|
|
|
|
# /prompt-optimize
|
|
|
|
Analyze and optimize the following prompt for maximum ECC leverage.
|
|
|
|
## Your Task
|
|
|
|
Apply the **prompt-optimizer** skill to the user's input below. Follow the 6-phase analysis pipeline:
|
|
|
|
0. **Project Detection** — Read CLAUDE.md, detect tech stack from project files (package.json, go.mod, pyproject.toml, etc.)
|
|
1. **Intent Detection** — Classify the task type (new feature, bug fix, refactor, research, testing, review, documentation, infrastructure, design)
|
|
2. **Scope Assessment** — Evaluate complexity (TRIVIAL / LOW / MEDIUM / HIGH / EPIC), using codebase size as signal if detected
|
|
3. **ECC Component Matching** — Map to specific skills, commands, agents, and model tier
|
|
4. **Missing Context Detection** — Identify gaps. If 3+ critical items missing, ask the user to clarify before generating
|
|
5. **Workflow & Model** — Determine lifecycle position, recommend model tier, and split into multiple prompts if HIGH/EPIC
|
|
|
|
## Output Requirements
|
|
|
|
- Present diagnosis, recommended ECC components, and an optimized prompt using the Output Format from the prompt-optimizer skill
|
|
- Provide both **Full Version** (detailed) and **Quick Version** (compact, varied by intent type)
|
|
- Respond in the same language as the user's input
|
|
- The optimized prompt must be complete and ready to copy-paste into a new session
|
|
- End with a footer offering adjustment or a clear next step for starting a separate execution request
|
|
|
|
## CRITICAL
|
|
|
|
Do NOT execute the user's task. Output ONLY the analysis and optimized prompt.
|
|
If the user asks for direct execution, explain that `/prompt-optimize` only produces advisory output and tell them to start a normal task request instead.
|
|
|
|
Note: `blueprint` is a **skill**, not a slash command. Write "Use the blueprint skill"
|
|
instead of presenting it as a `/...` command.
|
|
|
|
## User Input
|
|
|
|
$ARGUMENTS
|