feat(design): VS Code extension UI mockups (roadmap WS4 stage 1)#103
Open
SamPlvs wants to merge 1 commit into
Open
feat(design): VS Code extension UI mockups (roadmap WS4 stage 1)#103SamPlvs wants to merge 1 commit into
SamPlvs wants to merge 1 commit into
Conversation
Nine browser-viewable screens + shared tokens.css simulating the VS Code workbench in the ZO brand system, depicting one canonical MNIST-demo moment. Approval artifact gating all Stage-2 extension work. Includes the 2026-07 feature roadmap persisted to platform memory (PR-046) and session-040 records.
SamPlvs
force-pushed
the
claude/vscode-design-mockups
branch
from
July 12, 2026 13:55
9aefcf9 to
3376743
Compare
Deploying zero-operators with
|
| Latest commit: |
3376743
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2993c702.zero-operators.pages.dev |
| Branch Preview URL: | https://claude-vscode-design-mockups.zero-operators.pages.dev |
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
1 participant
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.
What
Stage 1 of the VS Code extension workstream from the 2026-07 feature roadmap: nine static, browser-viewable design mockups + a shared
tokens.css, simulating the full extension UI in the ZO brand system before any extension code is written. Your sign-off on these screens gates all Stage-2 work (headless-tmux engine,zo-vscodeextension).Also included per the memory protocol: the roadmap itself persisted to
memory/zo-platform/roadmaps/2026-07-feature-roadmap.md(plan of record for WS1-WS4), session-040 records, and PRIORS PR-046 (plans referenced from tracked memory must themselves be tracked — the session-028 internal plan file was found to have vanished from~/.claude/plans).How to review
Open
design/vscode/00-overview.htmlin a browser — it indexes all eight screens with review guidance. On each page: toggle dark/light (top right), and read the "Implementation notes" block at the foot (each UI region is tied to its data source in the planned.zo/runtime/contract).All nine pages depict one canonical moment: the public MNIST demo resuming into phase_4, exp-003 at epoch 6/8, the upcoming gate at test_accuracy 0.9912 (could_pass). A consistency pass reconciled timeline and metric values across all screens and verified both themes render.
Screens
Open question for you
Em-dashes: kept throughout as the design-file house glyph (they mirror
design/brand-system.html's list markers and label separators), even though prose copy elsewhere bans them. Say the word and I'll purge the prose instances in a follow-up.Notes
tokens.csscarries one external dependency (Google Fonts import) annotated as browser-preview convenience; production bundles Geist/JetBrains Mono/Instrument Serif as woff2 under the webview CSP.