Skip to content

feat(design): Quackback AI in the builder, and matching a brand from its website - #921

Draft
mortondev wants to merge 11 commits into
feat/builder-4-builderfrom
feat/builder-5-ai
Draft

mortondev wants to merge 11 commits into
feat/builder-4-builderfrom
feat/builder-5-ai

Conversation

@mortondev

Copy link
Copy Markdown
Member

Part 5 of 6 of the portal builder stack. Review and merge in order.

Design AI scoped to the selection, with one-line summaries and Undo;
looks from a website, a logo or screenshots; the website reader that
measures colours, fonts and logos, with optional rendered capture; the
design MCP tools for reading and editing the draft.

Each part typechecks, lints and passes its own tests on top of the part below it. Together the six parts are the builder branch with main merged in.

…ts website

Design AI scoped to the selection, with one-line summaries and Undo;
looks from a website, a logo or screenshots; the website reader that
measures colours, fonts and logos, with optional rendered capture; the
design MCP tools for reading and editing the draft.
Each test ran the font match on the same synthetic pixels, most of them on a
fresh worker, and the matches measure full-size screenshots in plain JS, so
on a shared CI runner the file passed its 20s cap under load. The type match
is now memoised per page kind (brand-fonts.test.ts covers the worker) and the
file allows 60s a test.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant