Diagnose a Failed Materials Synthesis
Have a failed reaction or material batch and need possible causes to check.
Prompts for your job
Have a failed reaction or material batch and need possible causes to check.
Use this when a transaction reverts and you want likely causes worked out from the error message, call data, and gas used.
Have a deposition, hearing, or meeting recording that is too quiet, skipping, cutting out, or failing to save and you need troubleshooting steps from the symptoms.
Use this when a variant underperformed in an A/B test and you need structured hypotheses about what went wrong.
Need to understand why an email or mail appeal underperformed and what to test next.
Use this when a machine or component is misbehaving and you need a ranked set of likely causes and the checks that confirm or rule them out.
Have a user crash report and need ranked likely causes and fixes.
Use this when a customer describes a sound and you want a short ranked list of likely sources to check.
Use this when a pipeline job has failed and you have error logs but need help pinpointing the cause.
Need to turn a customer's description of a faulty product into a short list of likely causes to check.
Use this when a campaign missed its targets and you need likely causes plus the next tests to run.
Need to identify causes of network latency and get actionable optimization strategies.
Use this when your mesh has non-manifold errors and you want likely causes and step-by-step fixes.
Use this when a finished or nearly finished dish tastes unbalanced, looks wrong, or fails quality expectations and you need fast corrective direction.
Use this when an API call is failing and you have the request details and the response but no clear cause.
Use this when your single-page app shows a blank screen in production on Vercel but works locally.
Use this when your render fails or looks noisy and you need a structured set of troubleshooting steps.
Use this when a feature works in one browser but fails in another and you need ranked likely causes with quick tests.
See data drift alerts and need to diagnose the root cause.
Use this when a clinician or technician describes a device malfunction and you need a structured differential of causes and safe next steps.
Photograph a rig setup or an error screen and want possible explanations before you call for service.
Use this when an ERP module throws an error after a configuration change and you need likely causes and safe fixes to try.
Have a stack trace, event log, or error output and want likely root causes and next checks ranked by probability.
Use this when a machine or line has stopped and you only have the operator's description to work from.