Improve Prompt
Turn the user's rough request into a stronger prompt that another agent can act on.
Output rules
- Return only the improved prompt in chat.
- Do not explain what you changed.
- Do not solve, implement, or review the task.
- Preserve the user's intent, constraints, and requested outcome.
- Add useful detail: context, scope, expected behavior, edge cases, quality criteria, and verification steps when they fit.
- Do not invent product requirements, technical choices, files, or constraints. If key information is missing, write a prompt that asks for it or states a sensible assumption.
- Match the length to the task. Make small requests only a little clearer. Make complex requests detailed enough to guide good work.
- Use direct language and concrete acceptance criteria.
- Keep the prompt easy to copy and paste. Do not wrap it in commentary or quotation marks.
Detail level
Choose the smallest useful level:
- Tiny change: State the exact change and the main constraint.
- Focused feature: Include the target area, behavior, important states, and acceptance criteria.
- Large or unclear task: Include the goal, current context if provided, scope, constraints, decisions to resolve, edge cases, and validation.
When the user gives a vague request, improve its precision without turning it into a long project plan.
Examples
Input:
Make this hero section better
Output:
Improve the hero section so its value proposition is clear within a few seconds. Strengthen the heading and supporting copy, make the primary call to action more prominent, improve visual hierarchy and spacing, and ensure the layout works well on mobile and desktop. Keep the existing brand style and avoid adding unrelated sections. Verify that the result is accessible and that the primary action remains easy to find at every viewport size.
Input:
Make the button bigger
Output:
Increase the button's size enough to improve readability and tap comfort without making it dominate the surrounding UI. Preserve its existing visual style, alignment, responsive behavior, and interaction states.
Input:
Add user settings
Output:
Add a user settings area where users can view and update their account preferences. Identify the existing account and navigation patterns first, then add the smallest consistent settings flow for the supported preferences. Include loading, success, validation, error, and unsaved-change states. Protect sensitive settings, preserve existing data, and add tests or other suitable checks for the update behavior.
1---2name: improve-prompt3description: Rewrite a user's rough request into a clear, specific, and actionable prompt without doing the requested work. Use only when the user explicitly invokes improve-prompt or asks to improve a prompt.4---56# Improve Prompt78Turn the user's rough request into a stronger prompt that another agent can act on.910## Output rules1112- Return only the improved prompt in chat.13- Do not explain what you changed.14- Do not solve, implement, or review the task.15- Preserve the user's intent, constraints, and requested outcome.16- Add useful detail: context, scope, expected behavior, edge cases, quality criteria, and verification steps when they fit.17- Do not invent product requirements, technical choices, files, or constraints. If key information is missing, write a prompt that asks for it or states a sensible assumption.18- Match the length to the task. Make small requests only a little clearer. Make complex requests detailed enough to guide good work.19- Use direct language and concrete acceptance criteria.20- Keep the prompt easy to copy and paste. Do not wrap it in commentary or quotation marks.2122## Detail level2324Choose the smallest useful level:2526- **Tiny change:** State the exact change and the main constraint.27- **Focused feature:** Include the target area, behavior, important states, and acceptance criteria.28- **Large or unclear task:** Include the goal, current context if provided, scope, constraints, decisions to resolve, edge cases, and validation.2930When the user gives a vague request, improve its precision without turning it into a long project plan.3132## Examples3334Input:3536```text37Make this hero section better38```3940Output:4142```text43Improve the hero section so its value proposition is clear within a few seconds. Strengthen the heading and supporting copy, make the primary call to action more prominent, improve visual hierarchy and spacing, and ensure the layout works well on mobile and desktop. Keep the existing brand style and avoid adding unrelated sections. Verify that the result is accessible and that the primary action remains easy to find at every viewport size.44```4546Input:4748```text49Make the button bigger50```5152Output:5354```text55Increase the button's size enough to improve readability and tap comfort without making it dominate the surrounding UI. Preserve its existing visual style, alignment, responsive behavior, and interaction states.56```5758Input:5960```text61Add user settings62```6364Output:6566```text67Add a user settings area where users can view and update their account preferences. Identify the existing account and navigation patterns first, then add the smallest consistent settings flow for the supported preferences. Include loading, success, validation, error, and unsaved-change states. Protect sensitive settings, preserve existing data, and add tests or other suitable checks for the update behavior.68```
dobroslavradosavljevic