know what you own, and where.

Build me a personal inventory as a single web page, for insurance and for knowing what I own.

Ask me first:
- How I want things grouped: by room, by category, or something else.
- Which fields matter to me per item — name, value, purchase date, serial number, warranty expiry, notes — and which of those are optional.
- Whether I want a total value, per group and overall.
- Whether this is a whole household, one collection, or something narrower.

Build from my answers. Do not invent items, values, or an insurance schedule.

WHAT IT DOES

- Adding an item is fast and forgiving: name first, everything else optional. A list of two hundred things only gets made if each one takes ten seconds.
- Groups as I described, collapsible, with counts and totals per group if I asked for values.
- Search across every field, matching as I type.
- Sort by name, value or date within a group.
- Editing and deleting items, and moving an item between groups.
- A total value, clearly labelled as the sum of what I entered rather than any kind of appraisal.

EXPORT — THIS ONE MATTERS

- Export everything as JSON for reimport.
- Also export a plain readable version — a table or CSV — that I could send to an insurer or a loss adjuster.
- Import from the JSON.
- Say on the page that browser storage is the only copy and that this particular list is worth exporting somewhere else, since the reasons you would need it are the same reasons the device might be gone.

DESIGN

- Dense and tabular on a laptop, since that is where a long list gets entered and read.
- Usable on a phone for adding one thing as you buy it.
- Plain. This is a reference document, not a showcase.

BE HONEST ON THE PAGE

- Say the inventory is stored in this browser only and is not uploaded anywhere.
- Do not embed photographs into storage — explain that images belong in my own photo library, referenced by name, because browser storage is not the place for them.
- Do not value anything for me, estimate depreciation, or describe the total as an insured amount.

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="personal-inventory">

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