Translate Metric Requests Into Logic
Need to convert a vague business request like active customer into calculable rules.
Prompts for your job
Need to convert a vague business request like active customer into calculable rules.
Get vague client feedback like 'make it pop' or 'I don't like it' and need concrete, defensible design revisions.
Need to set up or improve a translation management system integrated with AI for efficient localization.
Need to evaluate the cost-benefit of adopting new technologies in your transportation operations.
Need to create visualizations that highlight trends in financial data, such as revenue growth, expense patterns, or market correlations.
Need to automate the collection and analysis of trend data from various sources to identify insights and patterns.
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.
Use this when a CSS style is not applying to an element and you want ranked possible causes with concrete fixes.
Have a slow dashboard and want likely causes and optimization steps.
Encounter errors or issues while integrating an API and need help diagnosing and resolving them.
Have a board that will not boot and you can describe the LEDs, rail voltages, and serial output you observe.
Can describe a broken interaction in your game and need likely causes plus next steps to share with art and code.
Have voltage, current or waveform readings from a prototype circuit and need likely causes plus the next checks to run.
Have symptoms and recent changes and want a ranked list of likely causes and next checks.
Need step-by-step guidance to resolve software problems like crashes, error messages, or compatibility issues.
Need step-by-step guidance to resolve basic technical problems without escalation.
Need to diagnose and resolve problems in database replication, such as network issues, configuration errors, or constraint violations.
Are encountering issues or unexpected behavior while implementing a specific design pattern.
Need a structured path to diagnose and fix a DNS problem.
Need to diagnose and resolve EIGRP problems like neighbor adjacency failures or route inconsistencies.
Use this when an ERP user reports a confusing issue during post-go-live support and you need clear diagnostic steps rather than guesswork.
Have a payload or exploit failing and need possible causes and next troubleshooting steps from the error text.
Use this when someone reports a vague problem such as 'the app is slow since Tuesday' and you need a focused set of questions and tests.