only the units you use.

Build me a unit converter as a single web page, with only the conversions I actually use.

Ask me first:
- Which conversions I want. Push me for specifics — not "weight" but "grams to ounces".
- Whether any of them are ingredient-specific, such as grams to cups for particular baking ingredients.
- What precision each one needs, and whether any should show fractions rather than decimals.
- Whether any involve a rate I set myself, such as a currency.

Only include the conversions I name. Do not add a general unit picker and do not include categories I did not ask for.

WHAT IT DOES

- Each conversion is its own row, all visible at once. No dropdowns, no category selection, no search.
- Each row converts in both directions: typing in either field updates the other.
- Precision per conversion, as I specified. A temperature to one decimal and a machining dimension to three are different requirements.
- Where I asked for fractions — fractional inches, for example — show the nearest useful fraction as well as the decimal.
- Ingredient-specific volume conversions use the density for that specific ingredient, and label which ingredient each row is for.
- If a conversion uses a rate I set, put the rate on screen as an editable field with the date I set it, so it is never mistaken for a live figure.

DESIGN

- One screen, no scrolling if the number of conversions allows.
- Large numeric inputs with a numeric keypad on mobile.
- Monospace for numbers so they do not jump around as they update.

BE HONEST ON THE PAGE

- Say that any currency or custom rate is one I entered and is not live.
- Where a conversion is approximate — cups of flour, most obviously — say so rather than implying three decimal places of accuracy.

DELIVERY

- Produce one self-contained HTML file. Inline the CSS and JavaScript.
- No build step, no server, no framework, no package install, no external
  requests at runtime.
- Mobile-first and responsive; it has to be usable one-handed on a phone and
  still look right on a laptop.
- Accessible: semantic HTML, real contrast, visible keyboard focus, labelled
  controls, touch targets big enough to hit, and respect reduced-motion.
- Use placeholders where information is missing. Do not invent facts, numbers,
  names, dates, prices, or results I have not given you.
- Before you call it finished, use it yourself: enter real-looking data, reload
  the page, and confirm nothing is lost or mangled.

PUBLISHING

Publish the finished page to HTMLShare and give me the link.

Use exactly one of the two paths below, preferring the first. Make the call
directly. Do not route it through a code sandbox, container, or computer-use
session — that is where the request gets blocked, and it is never necessary.

1. An HTMLShare integration or connector, if you have one configured.
   The page is permanent and owned by my account. Report the url and the
   siteId. There is no claimUrl or manageToken on this path — do not go
   looking for one, and do not switch paths in order to produce one.

2. Otherwise, publish anonymously over REST. No account, key, or signup is
   needed:

    POST https://api.htmlshare.net/v1/publish
    content-type: application/json

    {"html": "<!doctype html> ... "}

   The reference is https://htmlshare.net/docs and, for the full schema,
   https://api.htmlshare.net/openapi.json

   Report these from the response, in your reply and never inside the page:
     url          the public page
     claimUrl     a private link that is mine alone. opening it is how I keep
                  the page past its 24-hour expiry, or set an email reminder
                  before it goes. it carries the manage token, so it must
                  never appear in the published HTML or anywhere a visitor
                  could see it.
     manageToken  the only thing that can edit or delete this page later. it is
                  returned once and never again, so tell me what it is.

Tell me which of the two you used. If the path you reach for first is
unavailable in your environment, say so and tell me what you are switching to
before you publish — a permanent page on my account and a 24-hour anonymous
page are different things, and which one I get is my decision, not a detail.

If I ask for a change afterwards, update the existing page instead of
publishing again, so the URL I have already shared keeps working — through the
same integration on path 1, or with the manage token as an X-Manage-Token
header on path 2.

RECIPE MARKER

Include this tag in the <head>, exactly as written:

    <meta name="htmlshare-recipe" content="unit-converter">

It tells htmlshare which recipe the page came from, so the library can count
that this one was actually made. It carries nothing else.