ask-style

Ask Style — Structured Request Formatter

Take the user's raw request and reformat it into a clear, actionable prompt.

Structure

Every well-formed request should have:

1. Context — What exists today. What's the current state.
2. Goal — What the end result should look like. Be specific.
3. Constraints — What must not change. Performance budgets, backward compatibility, style rules.
4. Acceptance criteria — How do we know it's done? Concrete, checkable items.

Steps

1. Read the user's original request.
2. Ask clarifying questions if critical information is missing (max 3 questions).
3. Output the reformatted request using the structure above.
4. Ask the user to confirm before proceeding with the work.

Example

Raw: "make the login faster"

Reformatted:

Context: The login page at /auth/login currently takes ~3s to load on a cold start. Goal: Reduce initial load to under 1s. Constraints: Must keep the existing OAuth flow. No changes to the auth provider. Acceptance criteria:

• Lighthouse performance score > 90
• Time to interactive < 1s on 4G throttled connection
• No regressions in login success rate