Built by RM Catalog →
← Learn · free lesson

How to make an HQ for your project.

One page that says where a project stands. You open it instead of re-reading chats, and so does Claude.

What an HQ is

A plain web page on your own computer. It reads one small data file and shows: what the project is, what is done, what is waiting on you, and what comes next. Nothing is hosted, nothing is public.

It solves one problem: a project with many files and many chats has no single place that says what is true today.

Build it in five steps

  1. Decide what it shows. Four blocks are enough: State (one sentence), Done and checked, Waiting on you, Next.
  2. Keep the facts in one data file. A file called hq.json next to the page. The page only displays it. You never edit HTML to change a fact.
  3. Ask Claude to build the page with the prompt below.
  4. Open it. In the project folder run python3 -m http.server 4900, then open localhost:4900 in your browser. (Double-clicking index.html usually fails: browsers block a page from reading a local file next to it.)
  5. Make updating a rule. Add one line to the project instructions: “At the end of every session, update hq.json.” An HQ nobody updates is worse than none.

The prompt

Paste this into Claude in an empty project folder:

Build a one-page HQ for this project in this folder.
Files: index.html and hq.json only. No frameworks, no external scripts, no tracking.
hq.json fields: project, state (one sentence), updated (date), done (list of
{text, how_checked}), waiting (list of {text, on_whom}), next (list of text).
index.html loads hq.json and shows four blocks: State, Done and checked,
Waiting on you, Next. Dark background, readable at phone width (390 px) and desktop.
Show the updated date at the top and turn it red if it is older than 7 days.
Fill hq.json with placeholder text I can replace. Tell me how to open it.
Then look at it at 390 px and at desktop width and tell me what you saw.

A starter hq.json, if you want to see the shape:

{
  "project": "My website",
  "state": "Live; contact form needs testing on a phone.",
  "updated": "2026-10-28",
  "done": [{"text": "Homepage live", "how_checked": "opened the live URL"}],
  "waiting": [{"text": "Photos for the about page", "on_whom": "me"}],
  "next": ["Test the contact form on a phone"]
}

Why the “how checked” field matters

It makes every “done” carry its proof. Claude is happy to write “done” for things it only edited. A line that says how it was checked is much harder to fake, and easier for you to doubt.

The catch

  • It goes stale. If updating it is not a rule, in a week it lies to you.
  • It is a display, not a memory. It shows what you or Claude wrote. It does not check anything by itself.
  • No secrets in the data file. Passwords, API keys and private numbers do not belong in hq.json.
  • Local only. Do not put it on a public address unless you have removed everything private.

Next

The longer version, with several projects on one page and a shared log, is a paid lesson later. Not on sale yet. See what’s coming.

WhoRomen, Groningen NL. One person, not an agency.
What Claude doesI build with Claude, Anthropic’s AI. It drafts and codes; I check every page, product and video before it goes out.
AI labelAnything made with AI is marked AI where it appears, like the logo.
PaymentsCheckout runs on the payment provider’s page. This site never asks for card details.