myb-p-mockup-templateslisted

# MyBusiness interactive mockups Make the proposed user journey usable locally: a reviewer should be able to navigate, search, open a record, change a value, save it and see the consequence. A screenshot alone is insufficient unless the user explicitly requests a static deliverable. ## Knowledge sources - `../myb-p-kb/references/50-ui-walkthrough/03-mockup-visual-baseline.md` — visual baseline, provenance date, CRM/module shells and measured styles. Read before changing product chrome. - `../myb-p-kb/references/50-ui-walkthrough/01-runtime-app-tour.md` — product screen context; read when choosing a module or checking whether a screen already exists. - `references/template-catalog.md` — page selection, implemented interactions and original HTML references. - `references/interaction-contract.md` — state, navigation, keyboard access, offline boundaries and QA. - `assets/prototype/` — runnable starter with twelve screen patterns and a visual gallery. - `scripts/scaffold.mjs`, `scripts/serve.mjs` — dependency-free project copying and loopback HTTP serving. Running the local starter needs no account or CRM connection. Establishing visual fidelity requires a reference: inspect the authorized current product screen when access is available. Product facts come from the knowledge base and observed UI, not invented sample behavior. ## 1. Turn the brief into a small journey Infer the module, persona, primary action and language from the request. Ask only if a missing decision c