the grid you would rather not break.

Build me a habit tracker as a single web page.

Ask me first:
- Which habits I am tracking. Push back gently if I list more than about six — a grid I cannot read is a grid I will not use.
- For each one, how often it is meant to happen: daily, weekdays, a number of times a week, or something else.
- Whether the week starts on Monday or Sunday for me.
- Whether I want any counters or streaks at all, or just the grid.

Do not invent habits or schedules. Do not add habits you think I should have.

WHAT IT DOES

- The current week is the top of the page and the biggest thing on it: habits as rows, days as columns, one tap to fill a square. Tapping again clears it.
- Below it, the same grid for the month, smaller, so the record is visible at a glance.
- Respect each habit's own schedule. A weekdays-only habit shows no expectation on Saturday, and a three-times-a-week habit shows progress against three, not against seven.
- Today's column is visually distinct without being loud.
- Let me add a short note to any day.
- Let me add, rename, reorder and archive habits from the page itself. Archiving keeps the history; deleting is separate and asks first.
- If I asked for counters, keep them factual: how many times this week, this month. If I said no, do not add streaks, badges or encouragement anyway.

DESIGN

- Mobile-first, one-handed, tappable without precision.
- The grid must be legible at a glance — this is a page people look at more often than they interact with.
- No celebration animations. No red for a missed day; a gap is information, not a failure state.

BE HONEST ON THE PAGE

- Say the record is stored in this browser only and does not sync between devices.
- Do not claim reminders or notifications; a published page cannot send them.

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="habit-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.