yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Design system tokens #45

New Issue
Closed
opened 2026-08-22 18:48:37 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-22 18:48:37 +01:00
Owner
Copy Link
Copy Source

Author .impeccable/design.json — colours, typography, spacing, the token set
every component consumes. Use the impeccable skill for this; it is what
the file's schema belongs to (CLAUDE.md, design section).

~/tea/arcada has a finished design.json at schemaVersion: 2 worth reading
first for the shape.

Constraints specific to this app:

  • The manual-search view (DESIGN.md §9.3) is dense, tabular and chip-heavy.
    The palette has to carry three verdict states — eligible, waived, rejected —
    legibly at small sizes and against each other, without relying on colour
    alone.
  • Library status (§4.2) is five states, and they are informational rather than
    severity-ranked. Do not borrow an error/warning/success ramp for them.
  • It runs on a NAS dashboard, often on a phone, often in a dark room. Dark mode
    is not an afterthought.

.impeccable/live/config.json is already scaffolded and points at
web/index.html.

Acceptance: components consume tokens, never literal colour or spacing values,
and CI can assert that.

Depends on: #6

Labels: phase/5-ui, area/web, difficulty/moderate, type/feature

Author `.impeccable/design.json` — colours, typography, spacing, the token set every component consumes. **Use the `impeccable` skill for this**; it is what the file's schema belongs to (`CLAUDE.md`, design section). `~/tea/arcada` has a finished `design.json` at `schemaVersion: 2` worth reading first for the shape. Constraints specific to this app: - The manual-search view (`DESIGN.md` §9.3) is dense, tabular and chip-heavy. The palette has to carry three verdict states — eligible, waived, rejected — legibly at small sizes and against each other, without relying on colour alone. - Library status (§4.2) is five states, and they are informational rather than severity-ranked. Do not borrow an error/warning/success ramp for them. - It runs on a NAS dashboard, often on a phone, often in a dark room. Dark mode is not an afterthought. `.impeccable/live/config.json` is already scaffolded and points at `web/index.html`. Acceptance: components consume tokens, never literal colour or spacing values, and CI can assert that. --- **Depends on:** #6 Labels: `phase/5-ui`, `area/web`, `difficulty/moderate`, `type/feature`
naps62-yolo added the phase/5-uiarea/webdifficulty/moderatetype/feature labels 2026-08-22 18:48:37 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/web difficulty/moderate phase/5-ui type/feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#45
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?