Agent skill · writing content · daymade
prompt-optimizer
Transforms vague prompts or feature requests into precise, testable specifications using EARS (Easy Approach to Requirements Syntax) grounded in relevant domain theories (GTD, BJ Fogg, Gestalt). Use when requirements lack triggers or measurable outcomes, or the user asks to "optimize my prompt" / "improve this requirement" / "make this more specific".
Why this skill is useful
Provides structured methodologies and frameworks for transforming vague requirements into precise specifications that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
Prompt Optimizer Overview Optimize vague prompts into precise, actionable specifications using EARS (Easy Approach to Requirements Syntax) - a Rolls-Royce methodology for transforming natural language into structured, testable requirements. Methodology inspired by: This skill's approach to combining EARS with domain theory grounding was inspired by 阿星AI工作室 (A-Xing AI Studio), which demonstrated practical EARS application for prompt enhancement. Four-layer enhancement process: 1. EARS syntax transformation - Convert descriptive language to normative specifications 2. Domain theory grounding - Apply relevant industry frameworks (GTD, BJ Fogg, Gestalt, etc.) 3. Example extraction - Surface concrete use cases with real data 4. Structured prompt generation - Format using Role/Skills/Workflows/Examples/Formats framework When to Use Apply when: User provides vague feature requests ("build a dashboard", "create a reminder app") Requirements lack specific conditions, triggers, or measurable outcomes Natural language descriptions need conversion to testable specifications User explicitly requests prompt optimization or requirement refinement Six-Step Optimization Workflow Step 1: Analyze Original Requirement Identify weaknesses: Overly broad - "Add user authentication" → Missing password requirements, session management Missing triggers - "Send notifications" → Missing when/why notifications trigger Ambiguous actions - "Make it user-friendly" → No measurable usability criteria No constraints - "Process payments" → Missing security, compliance requirements Step 2: Apply EARS Transformation Convert requirements to EARS patterns. See references/earssyntax.md for complete syntax rules. Five core patterns: 1. Ubiquitous: The system shall <action> 2. Event-driven: When <trigger>, the system shall <action> 3. State-driven: While <state>, the system shall <action> 4. Conditional: If <condition>, the system shall <action> 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/prompt-optimizer