Explain Electrical Design Tradeoffs To Clients
Use this when a non-technical client must choose between two or more electrical design options and needs the tradeoffs in plain language.
Prompts for your job
Use this when a non-technical client must choose between two or more electrical design options and needs the tradeoffs in plain language.
Need a clear, practical explanation of encryption methods for a specific application, software, or industry.
Have a flexbox or grid layout that is not behaving as expected and you need a plain-English explanation of why.
Need to hand a game system's logic to a programmer as clear pseudocode or a state-machine description.
Need to understand or review a Terraform, CloudFormation, or Kubernetes diff before applying it.
Inherit unfamiliar Solidity code and need a plain-English walkthrough of its functions, state, and risks.
Need the derivation or a worked example for your arm's specific geometry.
Have load flow output and need a clear explanation of bus voltages, system losses and overloaded branches.
Are choosing between model architectures and want the trade-offs explained clearly before you commit.
Need a plain-English summary of what your model does and its risks.
Need to justify partitioning, clustering, or indexing choices for a large table to your team.
Need to understand PID tuning effects and get safe starting values for a temperature, flow, or pressure loop.
Have Kubernetes pod events and container logs showing CrashLoopBackOff and need a triage of likely causes and next diagnostic checks.
Need to describe why a prompt works or fails in technical terms.
Are reading a reference manual and need a plain-English walkthrough of which register bits to set and why.
Need a non-technical summary of a robot design for a customer, manager, or integrator.
Have to pick an org-wide default and want the access and risk implications in plain terms before deciding.
Use this when a security metric has worsened and you need to explain the cause and plan to your board in plain language.
Need to justify a security spend, project, or change to executives who do not speak technical jargon.
Are setting up a firewall, WAF, EDR, or cloud security service and need plain-English explanations of what each setting changes.
Are unsure how a pattern like upgradeable proxies, access control, or pull payments works and want it explained with a small example.
Need clear explanations and real-world examples of common software design patterns.
Need to translate velocity, burn-down, or cycle time into plain language for people outside the team.
Need to explain a vulnerability to a client in plain English with business impact.