docs: add DESIGN.md describing Orca's visual identity#981
Open
docs: add DESIGN.md describing Orca's visual identity#981
Conversation
Adds a DESIGN.md following the google-labs-code/design.md alpha spec so agents and contributors have a single structured source of truth for Orca's tokens (colors, typography, rounded, spacing, components) and the prose rationale for when and how to apply them. Tokens are derived from src/renderer/src/assets/main.css and the Button CVA in src/renderer/src/components/ui/button.tsx, with a parallel dark-colors block for the .dark theme remap. Tightens muted-foreground (#737373 -> #6B6B6B) and ring (#a1a1a1 -> #8E8E8E) to the WCAG AA / non-text 3:1 thresholds; an a11y note flags these as the normative target for the CSS variables. Passes the official `npx @google/design.md lint` with 0 errors.
Contributor
Author
|
This is a bit long IMO, I prob will try to slim it down before merge. |
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.
Summary
DESIGN.mdat the repo root following the google-labs-code/design.md alpha spec, so agents and contributors have a single structured source of truth for Orca's tokens and design rationale.src/renderer/src/assets/main.cssand the Button CVA insrc/renderer/src/components/ui/button.tsx; prose covers colors, typography, layout, elevation, shapes, component anatomy (titlebar agent badge, sidebar, buttons, diff comments, scrollbars), and do's/don'ts.muted-foreground#737373 → #6B6B6B(~4.89:1 on muted) andring#a1a1a1 → #8E8E8E(~3.28:1 on background). An inline a11y note flags these as the normative target the CSS variables should be aligned to.dark-colors:block so a build script can emit.darkCSS variables without re-parsing the prose.Validation
npx @google/design.md lint DESIGN.md→ 0 errors, 20 warnings, 1 info. All warnings areorphaned-tokensfor semantic colors consumed directly by CSS / Monaco / the git-decoration layer (not via thecomponentsmap), which is expected.Test plan
DESIGN.mdand confirm section order matches the spec (Overview → Colors → Typography → Layout → Elevation → Shapes → Components → Do's and Don'ts).button-primary,sidebar,input,card, etc.) correspond to the shadcn components insrc/renderer/src/components/ui/.dark-colors:match the.darkblock insrc/renderer/src/assets/main.css.--muted-foregroundand--ringinmain.cssto match the normative DESIGN.md values so runtime UI also clears WCAG AA / non-text 3:1.