the material, reorganised for revision.

Build me a study guide as a single web page, from material I will paste in.

Ask me first:
- For the material — notes, handouts, a syllabus, past paper questions. Ask me to paste it, in as many messages as it takes.
- What the exam or assessment is, and its format if I know it.
- Whether there are topics I already know well and would rather see condensed.
- Whether I want worked examples kept in full or summarised.

BUILDING THE GUIDE

- Use only what I give you. Do not add facts, definitions, examples, formulas or context from your own knowledge, even where you are confident and even where my notes are clearly incomplete.
- Where my notes are thin or contradictory, list that in a "gaps and open questions" section rather than smoothing it over. That section is one of the most useful things on the page.
- Reorganise by theme rather than by the order I was taught. Say which sections of my material each theme came from.
- Collect every definition into one place, in my course's wording.
- Keep worked examples intact unless I said to summarise them.
- Where two parts of my notes connect, say so explicitly — the connections are what notes in chronological order hide.

WHAT THE PAGE DOES

- A contents list at the top, linking to each theme.
- Each theme: a short summary, then the detail, then anything unresolved.
- A search across the whole guide.
- Print styles that produce something readable on paper.
- No quiz, no flashcards, no interactivity beyond navigation — this is a document.

BE HONEST ON THE PAGE

- State that the guide was built from my own notes and contains no material from anywhere else.
- Keep the gaps section visible rather than buried at the bottom.

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="study-guide">

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