architecture

Summary

How Charades is built, in three small diagrams and one overview, opened from the architecture chip in the bar.

Raw wireframes

• .context/designs/mobile/architecture/<overview|who-plays|how-it-works|relies-on>.html — the screens
• .context/designs/architecture/<name>.json — each diagram's source; <name>.html is drawn from it by Archify

Why it is drawn this way

• One question per diagram: who plays, how the app is built, what it relies on. Charades has no server, so there is no backend diagram.
• These screens are not in the phone frame: a 390px frame is too narrow to read a diagram, so they fill the window under the bar.
• The diagrams are generated assets: edit the .json, then run archify finalize architecture <name>.json <name>.html --quality showcase inside designs/architecture/.
• The overview is architecture and cost only: the stack with versions and the monthly cost. Why each choice was made is in the product's own CLAUDE.md.

Related

• home · score

Sources

• CLAUDE.md, package.json