prompt optimizer

AI Community

Skill notes

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

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/ears_syntax.md for complete syntax rules. Five core patterns: Ubiquitous: The system shall <action> Event-driven: When <trigger>, the system shall <action> State-driven: While <state>, the system shall <action>

Step 3: Identify Domain Theories

Match requirements to established frameworks. See references/domain_theories.md for full catalog. Common domain mappings: Productivity → GTD, Pomodoro, Eisenhower Matrix Behavior Change → BJ Fogg Model (B=MAT), Atomic Habits UX Design → Hick's Law, Fitts's Law, Gestalt Principles

Step 4: Extract Concrete Examples

Generate specific examples with real data: User scenarios: "When user logs in on mobile device..." Data examples: "Product: 'Laptop', Price: $999, Stock: 15" Workflow examples: "Task: Write report → Sub-tasks: Research (2h), Draft (3h), Edit (1h)" Examples must be realistic, specific, varied (success/error/edge cases), and testable.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview prompt-optimizer.preview
# Step 4: Extract Concrete Examples

- User scenarios: "When user logs in on mobile device..."
- Data examples: "Product: 'Laptop', Price: $999, Stock: 15"
- Workflow examples: "Task: Write report → Sub-tasks: Research (2h), Draft (3h), Edit (1h)"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.