> For the complete documentation index, see [llms.txt](https://jordan-7.gitbook.io/jordan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jordan-7.gitbook.io/jordan-docs/internal/design.md).

# Design docs

Working design references for the front-end overhaul (`feat/ui-overhaul`).

| Doc                                                                                                                          | What it is                                                                                                                                                                                                                                                                             | Live link                                                                        |
| ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [`room-control-panel.html`](https://github.com/jordan9811/MegaChat/tree/v0-ui-migration/docs/design/room-control-panel.html) | Every streamer-editable room parameter, an audit of why the current create-room page fails, and the proposed create/manage split. Built from a browser audit of the running dashboard plus a source trace through `rooms-store.js`, `dashboard-routes.js`, `letters.js`, `rewards.js`. | [Artifact](https://claude.ai/code/artifact/4cd4298e-45c9-415a-bdc5-45656d02dbe2) |

Open the HTML files directly in a browser — they are self-contained, no build step.

## Related

* **Landing / app direction canvas** — the Round 1 → Round 2 design decision record (landing directions, the picked Landing V1, and Booth as the app page): <https://claude.ai/code/artifact/33a1b197-8bdb-4bcc-8e59-d5aed118f3c6>
* **Create-room mocks** — three interactive directions (Stack, Ribbon, Split preview): <https://claude.ai/code/artifact/70b4e2d6-296b-42a1-8389-2668f2c8e0b0>
* **Design rules** — [`../../DESIGN.md`](https://github.com/jordan9811/MegaChat/tree/v0-ui-migration/DESIGN.md) (lifecycle gating, spacing, uppercase budget, glow budget). Still authoritative for behavior; its neon-noir visual language was retired in the overhaul.
* **Backlog** — [`../../OPEN-ISSUES.md`](https://github.com/jordan9811/MegaChat/tree/v0-ui-migration/OPEN-ISSUES.md), including the bounty price-floor spec.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://jordan-7.gitbook.io/jordan-docs/internal/design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
