refactor: consolidate duplicate CSS design token namespaces

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
css
Domain
frontend

Research direction

Start in apps/app/src/app/globals.css and search the components that use --text-primary, --color-text-primary, --border-default, --color-border, --surface-primary, and --color-container. Choose one namespace convention or an alias approach, then verify that the duplicate namespaces are no longer used independently and that all usages follow the chosen convention.

Written by the indexing model from the issue text.

Description

enhancement

Description

Severity: P2 — Consistency

In apps/app/src/app/globals.css, there are duplicate design token namespaces:

  • `--text-primary` vs `--color-text-primary`
  • `--border-default` vs `--color-border`
  • `--surface-primary` vs `--color-container`

Both sets are used across different components.

Failure mode

Confusion about which token to use; risk of visual inconsistency when one set is updated but not the other.

Suggested fix

Consolidate to a single namespace. Either alias one to the other or migrate all usages to one convention.

From self-review finding F08

Dominant language
TypeScript
Stars
1.6k
Forks
202
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CopilotKit/OpenGenerativeUI

All issues in CopilotKit/OpenGenerativeUI

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.