download dots

🔄 Convert Units Without Getting It Wrong

Build the calculator you keep rebuilding in a spreadsheet, then put it on a link anyone can use. These prompts turn a formula into a working app: clean inputs, a result people trust, a saved record of every calculation, and an assistant that explains what the number means. Useful on your own desk, and useful in public as the page that brings people to you.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Convert Units Without Getting It Wrong

Copy

My team makes conversion mistakes on site and generic converters have far too many options. Build me a unit conversion tool for my trade. Keep the conversions as editable records so I decide exactly which ones appear, each with a from unit, a to unit, the factor, and the rounding appropriate for the job. Include derived conversions specific to my work such as coverage per unit or weight per volume, where I supply the reference figure. Let a value be converted in either direction with one tap, and keep a short list of recent conversions for reuse. Add an AI agent that sanity checks a result against a plausible range for that conversion and warns when a number looks like a decimal point error or a wrong unit was chosen. Automate a scheduled quarterly reminder to review the conversion list and remove ones nobody uses. Two logins: a field user who converts, and an owner who maintains the list and factors. It must work well on a phone.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Convert Units Without Getting It Wrong

Build the small set of trade-specific unit conversions your team uses daily, including derived units and sanity checks.

// the spark catches · intelligence awakens · the answer unfolds

Generic converters do not know your trade. This builds the handful you use daily, including the mixed and derived ones that cause real mistakes.

What's Included

  • Only the conversions you use so nobody hunts through a hundred options.
  • Trade-specific derived units such as coverage or density.
  • Both directions with sensible rounding for the job.
  • An assistant that catches a result that is obviously out.

How To Use

  1. Build only what your team uses. A short list gets used, a long one does not.
  2. Set rounding to what the job needs, not to what is mathematically pure.
  3. Include the awkward derived conversions. Those are where errors happen.
  4. Save recent conversions so a repeated one takes no time at all.

Feed the results into the material calculator, and use them on site with field service prompts.

Related from the blog