the board, on the wall, on a link.

Build me a fantasy draft board as a single web page.

Ask me first:
- The league name and the teams, in draft order.
- Snake or linear, and any twist we use — a third-round reversal, keepers already assigned to teams, anything non-standard.
- How many rounds, and what the roster slots are.
- Whether we use a pick clock, and how long.
- Whether I want to mark positions or just names.

Take the league rules exactly as I describe them. Do not invent teams, players, rankings or projections, and do not include a player list — I will type names as they are picked.

WHAT IT DOES

- The board is a grid: rounds down, teams across, picks filling in as they happen.
- Entering a pick is the fastest possible interaction. The current slot is already focused; I type a name and press enter; it advances to the next pick automatically. This is the single most important thing on the page.
- Whose pick it is must be unmissable from across a room — name, round and pick number, large.
- Implement the draft order exactly, including the snake turn and any twist I described. Handle keepers by pre-filling their slots and skipping those picks.
- If we use a clock: a countdown on the current pick, startable and pausable, with a visible warning near the end. Do not auto-pick when it expires; just make it obvious.
- Undo the last pick, and edit any pick, because someone will be misheard.
- Export the finished draft as text I can paste into a chat, and as JSON.

DESIGN

- Built to be projected or cast onto a television, and still usable on the laptop driving it. Large type, high contrast, no reliance on colour alone.
- The grid should fit as much as possible on screen without scrolling during a pick.
- No animation that delays the next entry.

BE HONEST ON THE PAGE

- Say the board is stored on this device only, so it should run on one machine and everyone else should watch the screen.
- Do not claim player data, rankings, projections or any connection to a fantasy platform.

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="fantasy-draft-board">

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