write down what you ate.

Build me a food log as a single web page. It is a diary, not a calorie database.

Ask me first:
- The meals I eat regularly, so they can be saved as one-tap entries.
- Whether I want to count anything numeric — calories, protein, both, or nothing.
- Whether I log by meal (breakfast/lunch/dinner/snack) or just by time of day.
- Whether I want to note anything else alongside food, such as how I felt afterwards.

Build from that. Do not invent meals, portion sizes, or nutrition numbers. If I want calories, I will tell you them — never estimate them for me.

WHAT IT DOES

- Today is the page. My saved regular meals are buttons; tapping one logs it with the current time.
- A free-text box logs anything not saved, with no required fields. "two slices of the leftover pizza" is a valid entry and must not be rejected or turned into a form.
- Let me save any free-text entry as a new regular, so the button list grows into my actual diet.
- If I asked to count something: a total for the day, shown plainly, and the number attached to each saved meal editable at any time. State on the page that these are numbers I supplied, not looked up.
- A week view I can read back — days in rows, entries in order. This is the part that makes a pattern visible.
- Editing and deleting entries has to be easy.

WHAT IT MUST NOT HAVE

- No search box against a food database. There is no database.
- No barcode scanning. A self-contained page cannot do it.
- No estimated calories, no macro breakdown you inferred, no "healthy" or "unhealthy" labelling of anything I ate.
- No daily target unless I asked for one, and no commentary when I go over or under it.

DESIGN

- Fast and quiet. Logging should feel like writing a line, not filling a form.
- Mobile-first: this gets used standing in a kitchen holding a plate.

BE HONEST ON THE PAGE

- Say the log is stored in this browser only.
- Say that any numbers are arithmetic on what I entered, with no nutritional database behind them, and that this is not nutritional or medical advice.

STORING THE DATA

- Save everything to localStorage in the browser, automatically, as I go. No
  accounts, no login, no server call.
- On the page, say plainly that data lives in this browser only and does not
  sync to other devices. Do not bury it.
- Give me an "export" button that copies or downloads everything as JSON, and an
  "import" that reads the same JSON back. That is the only way my data can move
  between devices, so it is not optional.
- Never lose what I have already entered. If the stored data is from an older
  version of the page, read what you can rather than throwing it away.

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="food-tracker">

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