# PayGo FigCraft build

Regenerates `../PayGo App Design.figcraft` from source. The design is built as a
script of FigCraft commands, so the whole file can be rebuilt deterministically.

```sh
pip install svgelements
python build.py paygo_build.json
"/c/Program Files/FigCraft/figcraft-cli.exe" run paygo_build.json \
  --out "../PayGo App Design.figcraft"
```

- `paygo_lib.py`     — tokens, layout primitives, icon + logo vector helpers
- `paygo_ui.py`      — PayGo atoms (buttons, cards, nav, status bar, QR, screen shell)
- `build_screens.py` — the 12 screens
- `build.py`         — foundations page, variables, styles, entry point

Node ids are predicted client-side (sequential from 2); `instance.create` consumes
one id per node in the main component's subtree, which `instance(component, size)`
accounts for. Keep that in mind when adding commands mid-script.

## The HTML page

`build_html.py` rebuilds `../paygo-app-design.html` from the SVGs in
`../assets/`, inlining each one and namespacing its internal ids so filters and
clip paths don't collide across the 48 inlined graphics. Text is left live (not
outlined) and Poppins is loaded from Google Fonts — which is why the SVGs are
inlined in the DOM rather than referenced as `<img>`, where page fonts would not
reach them. `build_artifact()` emits `paygo-artifact.html`, the same page shaped
for publishing as a Claude Artifact.

`proto.py` wires the click-through prototype (button → screen navigation, the
bottom-nav tabs on the three main components, and the two flow starting points).

Re-exporting the SVGs after editing the .figcraft:
`figcraft-cli run svg_exports.json --in "../PayGo App Design.figcraft"`.