Design HQ · homebase · kit chrome · 2026-08-20

MystFlo Design HQ — one language, every surface

The homebase for every mockup. Tabs below are the same chrome as design-foundations.html — not a second system. Cards open the HTML next to this hub. On a phone, each mockup opens the 375 frames so you can scroll. Turn the phone sideways for a desktop slide deck — swipe between screens. Size buttons still override. Nothing builds without a mockup, your sign-off, and a pixel review against it.

black & white luxury white/gray glows only lantern = needs you flat hairline rows single-theme dark
§ Core — how design works here

Ritual, layout tiers, and the system file. Pixel tokens live in design-foundations.html · Core 0 is the V3 contract.

                     /design  (STRICT ritual — every non-trivial design task)
┌──────────────────────────────────────────────────────────────────────────────┐
│ 1 PRE-FLIGHT   read kit decisions+lessons · foundations · canon · archetypes │
│ 2 FRAME        intent · principle · constraints                              │
│ 2b BRIEFS      Chief Product + Chief Researcher (+ domain agent)            │
│                ≤10-line insight briefs — insights land BEFORE pixels         │
│ 3-4 OPTIONS    Chief Designer (Fable) sketches → Peyton picks                 │
│ 4b MOCKUP      Chief Designer authors/updates the HTML mockup here            │
│    GATE        mobile + tablet + desktop, every state → Peyton signs off     │
│                ── nothing builds without it ──                               │
│ 5 BUILD        Platform Frontend Dev (Sonnet) implements the mockup verbatim  │
│ 6 SCREENSHOTS  375px first → tablet → desktop, scored vs the mockup frames   │
│ 6b REVIEW      Chief Designer (Fable) reviews rendered pixels — blockers stop │
│ 7 MEMORY       decisions → kit ledger · misses → kit lessons                 │
└──────────────────────────────────┬───────────────────────────────────────────┘
                                   ▼
                     /ship  gate 4.4d  (every UI-surface PR)
        Chief Designer (Fable) BLOCKING review — screenshots vs mockup;
        no mockup coverage = automatic blocker · then quality/security/CTO

· Hierarchy: Peyton (CPO) owns every sign-off → Chief Designer (Fable) owns design judgment, mockup authorship, both review gates → Chief Product + Chief Researcher feed briefs → Platform Frontend Dev (Sonnet) executes, never designs
· Scope changes update the SAME mockup first, republish at the same URL, then build
· Written version: docs/design/design-artifacts/README.md · docs/architecture/agents/agent-orchestration.md §5

Mobile · 375px — designed FIRST, scored first Tablet · ~768px Desktop · 1280px+ — the authored composition

· Passes desktop but fails a smaller tier = FAIL, not a partial pass
· Every artifact carries mobile + desktop frames · tablet frames landing progressively, required in all NEW mockups

3757681280+

These three are samples along a continuum, not the only sizes that exist. Content — spacing, type, card widths, gaps — scales smoothly at every width in between, the way a photo scales rather than jumps. Structure is different: a rail collapsing into a drawer, a row turning into a stack, a grid losing a column — those have no in-between state, so they change only at a few fixed, deliberate widths and never drift anywhere else.

1 · Foundations 2 · Assistant lifecycle 3 · App shell 4 · Overlays then pages in any order
Tokens · type · rows
$41.20
A1 · System
Design system foundations
The reference sheet every other artifact obeys — color, type, rows, badges, pills, buttons. Mark / Thread / Seal / lantern live here. Platform, Website, and Social dialects share the same core.
§ Mark — Thread, Seal, lantern

The drawable kit is authored once, in the foundations file. This hub does not redraw it.

Core 0 · Mark
Mark · Thread · Seal
Kit · system
Open Mark in design foundations
Stem in frame. Edge · you vs Edge · double. Lantern is needs-you, never a status, never on the logo.
§ Platform — the app

MF-Platform · dark-glass dialect · frames in docs/design/design-artifacts/ · reviewed against design-canon.md · tabbed walkthrough, same chrome as Brain.

Wrkspc
Acct
Preview
$41.20 · Peyton
Page content· · ·
A2 · System
App shell Built
Header, left rail, and footer for every logged-in page. Header is one quiet line — balance · name · sign-out — with a PREVIEW badge. Rail groups Workspace / Support / Account. Covers desktop, collapsed rail, mobile drawer, and every failure that stays inside the shell.
← Billing · Wallet activity
Top-up+$50.00
Support run−$0.08
A3 · System
Overlay choreography
Which overlay to use — do something ⇧ bottom sheet · go somewhere ⇦ slide-over · confirm = centered dialog — plus stacking, the z-map, and the system toast.
A4 · Page flow
Explore Built
Browse → card → detail sheet → activation wizard (Personalize → Connect → Try) → live in Pulse. Persona tabs are hosts-first.
On-Brand Support142 runs
Retreat Bookingpaused
Waitlist + Launchidle
A5 · Page flow
Pulse Built
Overview, Attention inbox, lists, run detail, and empty states. Health is Needs you / N failed — never a percent while the inbox is open.
What the Brain found
Retreats from $1,800 · deposits 30%
Voice: warm, direct, no fluff
Cancellation policy — confirm?
A6 · Page flow
Brain Partly built
The founder’s knowledge page on this preview — tabbed Import → Live. Playbook is her words; Our read is ours. Identity gate, Teach door, shelf of books.
SavedPermanent
A7 · Page flow
Team Not yet built
Saved (pre-activation) and Permanent (post) tabs, both detail modals, empty states. Reuses the Pulse card.
WhatsAppConnected
Google SheetsReconnect
StripePending
A8 · Page flow
Connects Not yet built
Catalog → picker → OAuth / key → Connected. Reconnect and Pending are the only two verbs. WhatsApp duplicate-number error is field-scoped, not a form-wide fail.
Wallet balance
$41.20
Top-up+$50.00
A9 · Page flow
Billing Built
Wallet overview, add-funds sheet, activity drill-overs, and the receipt stack — desktop and mobile.
A10 · Page flow
Usage Not yet built
KPIs, spend chart, cost by assistant, AI actions, period picker.
NamePeyton
Emailpeyton@mystflo.com
Member since2026
A11 · Page flow
Account & guest Not yet built
Account fields, guest-mode banner, the signup gate, waitlist — the guest-to-member journey.
How does billing work?+
What connects to what?+
Is my data private?
A12 · Page flow
Support surfaces Not yet built
Wishlist, Feedback, Support, FAQ, About, Legal — six quiet pages in the same shell. Feedback review frames live in shell.html. Desktop frames; mobile not yet drawn.
/feedback · quiet column
General platform
Assistant-specific
Your feedback…Submit
A12b · Page flow
Feedback Route shipped
Review inside shell.html: form, sent (Seal), guest (Mark). Thread under the title. Header is Private Beta + Feedback. Do not use feedback.html.
§ Assistants — lifecycle + per-assistant flows

The master structure first, then each public assistant that has a full-flow mockup.

ExploreTeamPersonalizeConnectTryPulseBilling
M1 · Master structure
Assistant lifecycle — every surface, one generic assistant
The path every assistant takes — Explore → Team → Personalize → Connect → Try → live on Pulse → Billing → reactivation. Primary build contract; per-assistant files inherit it.
card → live → monitored
01 guest DMs → 02 Brain answers → 03 tricky → Slack → ◎ helped in your voice
F1 · Assistant flow
On-Brand Support — full flow
Catalog card → Personalize / Connect / Try → live WhatsApp thread → Slack escalation → Pulse. Founder: Discover → Evaluate → Activate → Monitor. Guest: Trigger → Interact → Outcome.
card → Personalize → guest DM → Pulse
01 required date → 02 booking capture → 03 payment relay (fixed) → 04 confirmation/reminder → ◎ Pulse
F2 · Assistant flow
Workshop Booking — proposed flow Partly built
Catalog card → Personalize → guest DM → activation → Pulse. Booking link shows the full wa.me URL. WhatsApp reminders required; email optional. Post-activation detail sheet lives in the artifact (sec-8b).
card → Personalize → Launch now → guest DM
01 3-question setup → 02 make it richer → 03 pre-sale/sold-out → 04 ⚡ Launch now (tier-cap + US-pause aware) → ◎ Pulse
F3 · Assistant flow
Waitlist + Launch — proposed flow Not yet built
TMPL-WAITL1. Three-question setup plus launch channels. Launch Now shows WhatsApp tier cap, US pause, and wallet cost. Founder: Discover → Activate → Monitor. Subscriber: Trigger → Interact → Outcome.
Explore → Overview → Personalize → Connect → Try → Activated → Pulse
01 coming-soon card → 02 program facts + static preview → 03 Brain Check (hard gate) → activation writes the v1 kit → Pulse review/refine → Google Doc / copy
F4 · Assistant flow
Program Launch Kit — full journey Partly built
TMPL-WMKT01. Catalog → Personalize (write a kit) → Brain Check → activation writes v1 → Pulse to review and rewrite. Workshop and Retreat lenses; no swap.
Explore → detail → Personalize → Connect → Try → Pulse → overdue verdict → guest WhatsApp
01 beta card → 02 roster + deposit/balance + relay link + sign-off → 03 read-only bindings → 04 one real test → ◎ Pulse chase feed → Mark paid · Extend · Release
F5 · Assistant flow
Retreat Booking — full journey Beta
TMPL-RTBK01. Deposit and balance, T-30/14/7 chase, overdue verdict (Mark paid · Extend · Release). Payments relay through the founder’s own link. Sibling of Workshop Booking.
Standing placeholder
Catch-all for the next assistant flow.
F6 · Assistant flow
Remaining live assistants Not yet drawn
Every public assistant gets its own full-flow mockup, on the same pattern as On-Brand Support, before further UI work touches it.
Not yet published
§ Email

Letter gallery in Brand System V3 chrome. Dialect pixels also live on the Email tab of design-foundations.html.

V3 · paper white · one bronze CTA
MystFlo
28 active templates · Georgia headline · lantern-ink pill
E1 · Email
Email templates
28 active Resend letters in the light dialect — paper, Double Leaf, Thread, one bronze CTA. Inbox is not a MystFlo surface.
Website — marketing site

mystflo-website · full-token dialect, the parity reference · same core, page-flow mockups arrive as website design work goes mockup-first

Same core · website dialect
locked-scale visuals · Georgia display
W1 · Website
Website dialect
Website tokens inside the unified foundations file. Page-flow mockups arrive when website work goes mockup-first.
Social & marketing materials

Feed-legible mono-card dialect + deck treatment · direction-level today — detail earns its spec when those surfaces mature

Same core · feed dialect
high-contrast mono card · one focal line · no hairline subtlety at feed scale
S1 · Social / Marketing
Social & deck dialect
Feed-scale dialect inside the unified foundations file — what carries from the core and what changes at feed size.
§ Motion

Seal states, reduced-motion holds, and earned motion — authored in the foundations file.

Proposed · Motion
Seal · idle → mid → done
Kit · system
Open Motion in design foundations
Seal states and reduced-motion holds. Do not paint the halfway arc gold.
· Repo HTML is the source of truth — each artifact republishes from it at the same URL, so the board always shows the latest signed-off state
· Built by build agents from real page code · Chief Designer (Fable) canon review gates publishing
· Written companion: docs/design/design-artifacts/README.md