prompt-optimizer_skill

Overview

This skill analyzes user prompts and produces clearer, more specific, and actionable versions. It supports a fast Direct Analysis mode and an Interactive Questionnaire mode to collect missing details and turn vague requests into complete specifications.

How this skill works

The skill inspects prompts for vagueness, missing context, undefined success criteria, absent technical specs, and structure or actionability problems. By default it runs a Direct Analysis that lists issues and returns an optimized prompt; for complex or user-requested guidance it runs the Interactive Questionnaire to collect targeted answers and then composes a final specification.

When to use it

• When a request uses vague words like "something", "it", "this", or "that"
• When prompts lack technical details (language, framework, versions)
• When success criteria, edge cases, or constraints are missing
• When the request is broad or ambiguous (e.g., "build an app")
• When you want a structured, ready-to-run prompt for an agent or developer

Best practices

• Start with Direct Analysis for quick improvements; switch to Interactive Mode for medium/complex tasks
• Provide minimal context up front (goal, audience, platform) to speed optimization
• Specify required outputs and success criteria to make prompts actionable
• Use the questionnaire to capture stack, styling, features, and constraints
• Accept the optimized prompt as a base and iterate if you need different trade-offs

Example use cases

• Turn "Make a button" into a detailed component spec with props, states, and example usage
• Clarify a bug report by adding reproduction steps, error messages, and expected behavior
• Refine a broad request like "Build a dashboard" into a scoped feature list, data sources, and tech stack
• Collect stack and UI preferences for a front-end component via the interactive questionnaire
• Produce a ready-to-send prompt for an LLM or developer with clear acceptance criteria