Translate Vague Client Feedback Into Revisions
Get vague client feedback like 'make it pop' or 'I don't like it' and need concrete, defensible design revisions.
Prompts for your job
Get vague client feedback like 'make it pop' or 'I don't like it' and need concrete, defensible design revisions.
Have a source text and a client-specified register or style and want the first-pass draft to match it from the start.
Use this when a trip involves visas, vaccinations or specific gear and you need a checklist with nothing missed.
Get a production alert or customer report and need a ranked list of likely causes before you change anything.
Use this when a security alert comes in and you need a quick, structured summary of what may be happening.
Have a queue of charts and need to decide which ones require deeper coding review first.
Receive a facility problem report and need to sort urgency and next steps.
Have a backlog of internal communication requests and need to sort them by urgency, audience and channel before committing time or send slots.
Have a written description of a building system problem and need likely causes and questions to ask.
Must decide whether a problem needs emergency service or a routine visit.
Use this when staff have reported building problems and you need to sort, prioritise and route each one to the right person.
Have a batch with a defect such as separation, caking, or off-flavor and you want likely causes, checks to run, and immediate actions.
See unexplained patterns in your reduced images and want likely causes plus the checks to confirm them.
Use this when a client reports a problem with a wheelchair, splint, or adaptive tool and you need possible fixes.
Receive a description of a technical error from a client and need to diagnose the likely cause and next steps.
Use this when a CSS style is not applying to an element and you want ranked possible causes with concrete fixes.
Need to diagnose why a partner's deal registration failed, stalled, or was rejected and decide the next steps.
Have notes from a failed assay and need to identify possible causes and next steps.
Use this when a client says their payment did not go through and describes what happened.
Use this when a reaction did not work as expected and you need ranked possible causes and practical fixes.
Use this when a tractor or implement is acting up and you want an ordered list of things to check before calling a mechanic.
Get a guest description or photo of a leak, noise, or broken item and need likely causes.
Are on site, a vendor is running late, and you need fast options to adjust the run of show or layout.
Need to diagnose a user-reported software problem from a description or screenshot.