Skip to content

Adopt Syndicate's own theme tokens (dark + light), from its published style #127

Closed

Description

@Skeyelab

Parent

#12

Why

The user wants the app to follow Syndicate's color theme. Syndicate's own user guide (untitledaudiosyndicate.com/user-guide) ships its brand tokens as CSS variables. A comment there says they come from "the app's LookAndFeel greys, paper #EDEDEA and Signal Green (Syndicate Branding/spec/tokens.json)". These are better than the #34 values we sampled from screenshots.

Dark (Syndicate's default):

ground #171717  window #1b1b1b  panel-top #1e1f20  panel-bot #171819
rail #1b1b1b  well #111213  slot #0f0f10  field #0a0a0a
key-top #232323  key #1e1e1e  key-bot #191919  key-line #000
row-line #131313  th #161616  rule #2e2e2e
fg #ededea  fg-body #d0d0cd  fg-label #d8d8d8  fg-btn #bdbdbd  fg-dim #7e7e7e  fg-faint #6e6e6e
sel #555555  hl #2a2a2a
signal #00ff48  signal-lo #00d93d  on-signal #111111

Light (Syndicate has a LIGHT MODE): ground #e6e6e4, window #dcdcda, panel-top #d6d6d4, panel-bot #dededc, well #e0e0de, slot #e8e8e6, field #f2f2f0, key-top #dadad8, key #d6d6d4, key-bot #bcbcba, key-line #9a9a9a, row-line #cdcdcb, th #d1d1cf, rule #c7c7c5, fg #1b1b1b. Get the rest from the guide's light block.

The factory TOXIC cue palette, per the same file: slot 1 #d7ff27, 3 #00bc78, 5 #168acd, 6 #635ceb, 7 #be3de4, 8 #f65a91 (slots 2 and 4 aren't listed). This differs from the palette the Python bridge used. So the #123 fallback deck colors should come from this source, or from a real ColorPalette capture, and live palette feedback always wins.

What to build

  • Replace the App/Theme and Presentation palette tokens with the dark values above, renamed to match (ground, panel, key, rule, fg-*, signal). The live/connected color is Signal Green #00ff48 (the text variant may need -lo for contrast).
  • Light mode: follow the macOS appearance by default, plus a setting ("Match macOS", "Dark", "Light"). Syndicate's own LIGHT MODE can't be read over OSC, so the user picks it to match.
  • Keep every existing contrast test, re-run against both themes. If a pair fails, adjust the token's use (for example, signal-lo for text), not the test.
  • Re-render all snapshots in both themes.

Acceptance criteria

  • Tokens are traced to the guide's CSS, with a comment citing the source.
  • Both themes pass the contrast tests.
  • The Settings appearance option works and is saved.
  • Test-first with /tdd for the token and contrast logic; snapshots for the views.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions