Agent skill

Token System

by Orange-OpenSource in Orange-OpenSource/Orange-Boosted-Bootstrap

OUDS design token system rules and architecture. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.

Install Token System

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap token-system --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/token-system .claude/skills/token-system && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "token-system" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system into .claude/skills/token-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-system", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap token-system --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/token-system .agents/skills/token-system && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "token-system" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system into .agents/skills/token-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-system", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap token-system --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/token-system .cursor/skills/token-system && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "token-system" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system into .cursor/skills/token-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-system", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git --path .github/skills/token-system

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap token-system --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/token-system .gemini/skills/token-system && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "token-system" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system into .gemini/skills/token-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-system", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap token-system

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/token-system .github/skills/token-system && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "token-system" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system into .github/skills/token-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-system", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap token-system --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/token-system .opencode/skills/token-system && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "token-system" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/token-system into .opencode/skills/token-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-system", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: token-system
GitHub stars: 222
Token cost: ~780 tokens
SKILL.md length: 177 words
Files: 2 (incl. references)
Skills in repo: 13
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

OUDS design token system rules and architecture. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.

Works in 7 steps: Component tokens first, then semantic → CSS custom properties for ALL colors → Never use raw tokens → …
Working with tokens
SKILL.md covers Why tokens matter, Token hierarchy, Rules and Naming convention, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Token System is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. OUDS design token system rules and architecture. Use this skill when working with tokens, adding new component tokens, debugging undefined token errors, working on dark mode, editing variables.scss, or touching any file in packages//scss/tokens/. Covers the 3-tier hierarchy (raw→semantic→component), CSS custom property bridge for dark mode, auto-generated file protections, import order, and the color-mode mixin. For deep architecture details, read references/architecture.md.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/architecture.md`).

It sits in Frontend & Design, covering CSS and styling, Theming and dark mode and Design tokens. The repository describes itself as: OUDS Web is an accessible, ergonomic and Orange branded framework based on Orange Unified Design System and Bootstrap. The licence is MIT.

When your agent uses it

Working with tokens
Adding new component tokens
Debugging undefined token errors
Working on dark mode

Example prompts

“/token-system”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Component tokens first, then semantic
CSS custom properties for ALL colors
Never use raw tokens
Never edit auto-generated files
Import order is critical
New tokens → all 3 brands
Use color-mode() for theme declarations

What it can do on your machine

Read from SKILL.md and the folder at commit f25f7be. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are scss).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Token System loads about 780 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 177 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~124
When it runs · the whole SKILL.md, loaded when a task matches: ~780
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Orange-OpenSource/Orange-Boosted-Bootstrap at commit f25f7be, republished under its MIT licence (© Orange-OpenSource). 177 words, ~780 tokens.

Download SKILL.mdSave it as .claude/skills/token-system/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: token-system
description: OUDS design token system rules and architecture. Use this skill when working with tokens, adding new component tokens, debugging undefined token errors, working on dark mode, editing _variables.scss, or touching any file in packages/*/scss/tokens/. Covers the 3-tier hierarchy (raw→semantic→component), CSS custom property bridge for dark mode, auto-generated file protections, import order, and the color-mode mixin. For deep architecture details, read references/architecture.md.

Token System

Why tokens matter

The token system makes one codebase serve 3 brands. Component SCSS uses token variables → each brand provides different values → same SCSS produces different visual output. Breaking the token contract breaks multi-brand.

Token hierarchy

Raw ($core-ouds-*)       → never use in components
  ↓
Semantic ($ouds-space-*) → use for non-color values
  ↓
Component ($ouds-btn-*)  → preferred when available
  ↓
CSS custom props (--bs-color-*) → use for ALL colors (dark mode)

Rules

1. Component tokens first, then semantic

scss

// ✓ component token
@include border-radius($ouds-button-border-radius-default);

// ✓ no component token → semantic fallback
@include border-radius($ouds-border-radius-default);

2. CSS custom properties for ALL colors

Colors come in light/dark pairs → exposed as CSS custom props → runtime switching.

scss

// ✓
color: var(--#{$prefix}color-content-default);

// ✗ locked to one mode
color: $ouds-color-content-default-light;

3. Never use raw tokens

$core-ouds-*, $core-orange-*, $core-sosh-* — no semantic meaning, breaks on redesign.

4. Never edit auto-generated files

Read-only per brand: _raw.scss, _semantic.scss, _component.scss, _*-custom-props.scss

Only _composite.scss is hand-editable (elevation, fonts, SVG icons, Sass maps).

5. Import order is critical

_raw → _semantic → _semantic-colors-custom-props → _composite → _component-colors-custom-props → _component

6. New tokens → all 3 brands

Add to all: packages/orange/, packages/sosh/, packages/orange-compact/. Each brand can have different values. Temporary fallbacks go in scss/_variables.scss with // TODO:.

7. Use `color-mode()` for theme declarations

scss

@include color-mode(light, true) {
  --#{$prefix}color-action-enabled: #{$ouds-color-action-enabled-light};
}
@include color-mode(dark) {
  --#{$prefix}color-action-enabled: #{$ouds-color-action-enabled-dark};
}

Naming convention

Layer	Pattern	Example
Raw	`$core-ouds-{cat}-{scale}`	`$core-ouds-border-radius-200`
Semantic	`$ouds-{cat}-{variant}`	`$ouds-border-radius-default`
Component	`$ouds-{comp}-{cat}-{variant}`	`$ouds-button-border-radius-default`
CSS prop	`--{$prefix}{cat}-{name}`	`--bs-color-action-enabled`

Deep reference

For the full pipeline (Figma → DTCG → Style Dictionary → SCSS), layer-by-layer explanation, and color flow diagrams, read references/architecture.md in this skill directory.

Files

SKILL.md and 1 other file (references) in .github/skills/token-system of Orange-OpenSource/Orange-Boosted-Bootstrap.

SKILL.md
references/architecture.md

Open the folder on GitHubat commit f25f7be

Compare with similar skills

Token System next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Token System compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Token System this skillOrange-OpenSource/Orange-Boosted-Bootstrap	222	—	~780	Automated safety check: Pass	MIT	today
MCP Developmentcoollabsio/coolify	63k	1 repos	~949	Automated safety check: Pass	MIT	today
Liuguang Banlan UIsickn33/agentic-awesome-skills	47k	1 repos	~2.5k	Automated safety check: Pass	MIT	yesterday
Preline Theme Generatorhtmlstreamofficial/preline	6.5k	—	~619	Automated safety check: Warn	Custom licence	1 mo ago
Tailwind Theme Builderjezweb/claude-skills	1.1k	1 repos	~3.2k	Automated safety check: Pass	MIT	2 days ago
Tailwind V4 Shadcnever-works/ever-works	158	2 repos	~3.8k	Automated safety check: Pass	MIT	yesterday

Similar skills

MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 1 repo~949 tokens
Frontend & DesignAuto-check passed
Liuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
47k GitHub starsUsed in 1 repo~2.5k tokens
Frontend & DesignAuto-check passed
Preline Theme Generator
htmlstreamofficial/preline
Generates light and dark Preline theme CSS from a brand color or mood, previews it, and validates token coverage through bundled local scripts.
6.5k GitHub stars~619 tokensUpdated 1 mo ago
Frontend & DesignAuto-check: warnings
Tailwind Theme Builder
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.
1.1k GitHub starsUsed in 1 repo~3.2k tokens
Frontend & DesignAuto-check passed
Tailwind V4 Shadcn
ever-works/ever-works
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React.
158 GitHub starsUsed in 2 repos~3.8k tokens
Frontend & DesignAuto-check passed
Igniteui Wc Customize Component Theme
IgniteUI/igniteui-webcomponents
Theme and style Ignite UI Web Components (and igniteui-react) apps using CSS custom properties, optional Sass, and the igniteui-theming MCP server.
170 GitHub stars~4.3k tokensUpdated today
Frontend & DesignAuto-check passed

More from Orange-OpenSource/Orange-Boosted-Bootstrap

All 13 skills in this repo

Using Ouds Web Version Major Minor
Orange-OpenSource/Orange-Boosted-Bootstrap
Provides comprehensive knowledge of the OUDS Web library (Orange Unified Design System for Web), a Bootstrap-based CSS/JS framework for building Orange-branded web interfaces.
222 GitHub stars~4.1k tokensUpdated today
Auto-check passed
Code Review
Orange-OpenSource/Orange-Boosted-Bootstrap
OUDS Web compliance code review. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
222 GitHub stars~846 tokensUpdated today
Auto-check passed
Component Patterns
Orange-OpenSource/Orange-Boosted-Bootstrap
SCSS and JS structural patterns for OUDS Web components. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
222 GitHub stars~773 tokensUpdated today
Auto-check passed
Create Component
Orange-OpenSource/Orange-Boosted-Bootstrap
Step-by-step workflow for creating a new SCSS and/or JavaScript component in OUDS Web.
222 GitHub stars~648 tokensUpdated today
Auto-check passed
Diagnose Errors
Orange-OpenSource/Orange-Boosted-Bootstrap
Diagnostic workflow for build, lint, CI, and test errors in OUDS Web.
222 GitHub stars~680 tokensUpdated today
Auto-check passed
Javascript Conventions
Orange-OpenSource/Orange-Boosted-Bootstrap
JavaScript coding conventions for OUDS Web. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
222 GitHub stars~751 tokensUpdated today
Auto-check passed

Questions about Token System

What does Token System do?

OUDS design token system rules and architecture. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Token System is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. OUDS design token system rules and architecture.

When should I use Token System?

Token System fits situations like: working with tokens; adding new component tokens; debugging undefined token errors; working on dark mode.

How do I install Token System in Claude Code?

Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a claude-code`. Or copy the skill folder (.github/skills/token-system in Orange-OpenSource/Orange-Boosted-Bootstrap) into .claude/skills/token-system in your project. Claude Code loads it when a task matches its description.

How do I install Token System in Codex?

Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a codex`. Or copy the skill folder (.github/skills/token-system in Orange-OpenSource/Orange-Boosted-Bootstrap) into .agents/skills/token-system in your project. Codex loads it when a task matches its description.

Can I use Token System in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill token-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/token-system, .gemini/skills/token-system, .github/skills/token-system and .opencode/skills/token-system in your project.

What does Token System need to run?

SKILL.md names no scripts, command-line tools or credentials: Token System is instructions for the agent only.

Does Token System access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Token System safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Token System use?

Token System is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Token System use?

About 780 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Token System?

Skills that share tags, products or a category with Token System: MCP Development (coollabsio/coolify, 63k stars), Liuguang Banlan UI (sickn33/agentic-awesome-skills, 47k stars), Preline Theme Generator (htmlstreamofficial/preline, 6.5k stars) and Tailwind Theme Builder (jezweb/claude-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Token System?

Orange-OpenSource (a GitHub organization) maintains it in Orange-OpenSource/Orange-Boosted-Bootstrap, which has 222 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

Source: Orange-OpenSource/Orange-Boosted-Bootstrap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Token System

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Token System

Why tokens matter

Token hierarchy

Rules

1. Component tokens first, then semantic

2. CSS custom properties for ALL colors

3. Never use raw tokens

4. Never edit auto-generated files

5. Import order is critical

6. New tokens → all 3 brands

7. Use color-mode() for theme declarations

Naming convention

Deep reference

Files

Compare with similar skills

Similar skills

More from Orange-OpenSource/Orange-Boosted-Bootstrap

Related

Questions about Token System

7. Use `color-mode()` for theme declarations