feat(hub): UI mockups with low-fi wireframes in every blueprint - #86
Merged
Merged
Conversation
Each of the seven Hub blueprints now carries three `mockup` nodes for its key user-facing screens, each with a hand-authored low-fi SVG wireframe in the same style the AI wireframe generator uses (grayscale, one accent). - illustrates -> the blueprint's own requirements (e.g. Checkout shows the provider-hosted card fields behind "No Card Data at Rest"; Case Review shows per-field extraction confidence below the review threshold) - presented-by -> the webapp / container that renders the screen - navigates-to -> the next screen in the same user flow - descriptions use the blueprint's template params, so they are substituted on import - placed in a new row below the ADRs; existing content is unchanged (the diff is purely additive) The Hub viewer (canvas / wiki / table) needed no changes. The blueprint import picker labelled groups from a hard-coded map, so mockups (and people) showed up as raw type ids; unknown types now fall back to the Hub theme's plural label. A new catalogue test checks every blueprint: mockups exist and each has a presented-by relation, mockup relations are valid per the governance metamodel, relation endpoints exist, and stored wireframes are already sanitised (sanitizeWireframeSvg leaves them unchanged). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Each of the seven Hub blueprints now has three
mockupnodes, one per key user-facing screen. Every mockup includes a hand-drawn low-fi SVG wireframe. The wireframes follow the same style asai/mockupWireframe.ts: grayscale with one accent colour.illustratespoints to the requirements already in each blueprint. Two examples:presented-bypoints to the webapp or container that renders the screen.navigates-tolinks screens that belong to the same user flow.{{CHECKOUT_P95_MS}}), so they are substituted on import.Hub. The Hub viewer (canvas, wiki, table) needed no changes. The blueprint import picker labelled groups from a hard-coded map, so mockups and people appeared as raw type ids. Types missing from that map now use the plural label from the Hub theme.
Type of change
Checklist
npm testpasses (398/398)npm run typecheckpasses with no errorstests/hubCatalogue.test.tschecks every blueprint for:presented-byrelationsanitizeWireframeSvgreturns them unchanged)Test plan
npm run dev:webwith headless Chromium:?hub=bp-ecommerce-platform: the picker shows "Mockups (3)" and "People (2)". The import adds 3 mockups with their wireframes and all 9 of their relations.🤖 Generated with Claude Code