UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
SCSS and JS structural patterns for OUDS Web components. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Install Component Patterns
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap component-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/component-patterns .claude/skills/component-patterns && rm -rf skills-srcUse ~/.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/
Install the "component-patterns" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patterns into .claude/skills/component-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-patterns", 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 install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patternsType 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.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap component-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/component-patterns .agents/skills/component-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "component-patterns" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patterns into .agents/skills/component-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-patterns", 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.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap component-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/component-patterns .cursor/skills/component-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "component-patterns" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patterns into .cursor/skills/component-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-patterns", 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 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git --path .github/skills/component-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap component-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/component-patterns .gemini/skills/component-patterns && rm -rf skills-srcUse ~/.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/
Install the "component-patterns" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patterns into .gemini/skills/component-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-patterns", 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.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap component-patternsInstalls 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).
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ 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/component-patterns .github/skills/component-patterns && rm -rf skills-srcUse ~/.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/
Install the "component-patterns" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patterns into .github/skills/component-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-patterns", 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.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap component-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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/component-patterns .opencode/skills/component-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "component-patterns" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/component-patterns into .opencode/skills/component-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-patterns", 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
component-patterns- GitHub stars
- 222
- Token cost
- ~773 tokens
- SKILL.md length
- 104 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
SCSS and JS structural patterns for OUDS Web components. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
- Reviewing component SCSS files (scss/.scss
- SKILL.md covers Core principle, SCSS structure template, Key patterns and OUDS mod markers
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Scss/forms/.scss)
What it does
Component Patterns is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. SCSS and JS structural patterns for OUDS Web components. Use this skill when creating, editing, or reviewing component SCSS files (scss/.scss, scss/forms/.scss) or JS component files (js/src/.js). Covers CSS custom property declarations at top of class, state overrides via variable overrides (not property overrides), scss-docs-start/end markers, border-width compensation with calc(), mask-image icon pattern, responsive breakpoint overrides, and the OUDS mod comment convention.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering CSS and styling and Responsive design. 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
- Reviewing component SCSS files (scss/.scss
- Scss/forms/.scss)
- JS component files (js/src/.js)
Example prompts
- “/component-patterns”
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
Component Patterns loads about 773 tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 104 words of instructions outside code blocks.
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). 104 words, ~773 tokens.
Download SKILL.mdSave it as
.claude/skills/component-patterns/SKILL.md (or your agent's skills folder).- name
- component-patterns
- description
- SCSS and JS structural patterns for OUDS Web components. Use this skill when creating, editing, or reviewing component SCSS files (scss/_*.scss, scss/forms/_*.scss) or JS component files (js/src/*.js). Covers CSS custom property declarations at top of class, state overrides via variable overrides (not property overrides), scss-docs-start/end markers, border-width compensation with calc(), mask-image icon pattern, responsive breakpoint overrides, and the OUDS mod comment convention.
Component Patterns
Core principle
Every component declares CSS custom properties at the top of its main selector, then consumes them via var(). State changes (hover, disabled, variants) override the variable, never the property. This creates one source of truth and enables runtime theming.
SCSS structure template
#{$ouds-root-selector} {
--#{$prefix}my-comp-border-radius: #{$ouds-border-radius-default};
}
.my-component {
// scss-docs-start my-component-css-vars
--#{$prefix}my-comp-padding: #{$ouds-my-comp-space-padding-block};
--#{$prefix}my-comp-color: #{$ouds-color-content-default};
--#{$prefix}my-comp-bg: #{$ouds-color-bg-primary};
// scss-docs-end my-component-css-vars
padding: var(--#{$prefix}my-comp-padding);
color: var(--#{$prefix}my-comp-color);
background-color: var(--#{$prefix}my-comp-bg);
@include border-radius(var(--#{$prefix}my-comp-border-radius));
@include transition($transition-base);
&:hover {
--#{$prefix}my-comp-bg: #{$ouds-color-bg-secondary}; // Override var, not property
}
&:focus-visible {
@include focus-visible();
}
&:disabled, &[aria-disabled="true"] {
--#{$prefix}my-comp-color: #{$ouds-color-content-disabled};
pointer-events: none;
}
}
.my-component-variant {
--#{$prefix}my-comp-bg: #{$ouds-color-surface-brand};
}Key patterns
Documentation markers
The Astro docs site extracts CSS variable tables from these markers. Every component needs them:
// scss-docs-start badge-css-vars
// scss-docs-end badge-css-varsBorder-width compensation
Prevent layout shift when borders change on interaction:
padding: calc(var(--#{$prefix}btn-padding-y) - var(--#{$prefix}btn-border-width))
calc(var(--#{$prefix}btn-padding-x) - var(--#{$prefix}btn-border-width));Icon pattern (mask-image)
Icons inherit color from currentcolor:
&::before {
content: "";
background-color: currentcolor;
mask-image: escape-svg(var(--#{$prefix}icon));
mask-size: 100%;
mask-repeat: no-repeat;
}Responsive overrides
Override the variable at breakpoints, don't duplicate rulesets:
.component {
--#{$prefix}comp-width: #{$mobile};
@include media-breakpoint-up(xl) {
--#{$prefix}comp-width: #{$desktop};
}
}OUDS mod markers
Every deviation from Bootstrap upstream must be marked:
display: flex; // OUDS mod: instead of `inline-block`
// OUDS mod: loading buttons
.btn.loading-indeterminate { ... }
// End mod© Orange-OpenSource, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/component-patterns of Orange-OpenSource/Orange-Boosted-Bootstrap.
Open the folder on GitHubat commit f25f7be
Compare with similar skills
Component Patterns 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Component Patterns this skillOrange-OpenSource/Orange-Boosted-Bootstrap | 222 | — | ~773 | Automated safety check: Pass | MIT | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Frontend Design Routercode-yeongyu/oh-my-openagent | 70k | — | ~5.3k | Automated safety check: Pass | Custom licence | |
| Refero Designreferodesign/refero_skill | 292 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Tailwind CSS Patternsever-works/ever-works | 158 | 3 repos | ~1.6k | Automated safety check: Notes | AGPL-3.0 | |
| Frontend Design Principlespretend1111/claude-desktop-app | 494 | 1 repos | ~824 | Automated safety check: Pass | Custom licence |
Similar skills
Frontend Design Router
code-yeongyu/oh-my-openagent
Routes frontend and UI work through design reference rulesets, with a design-system gate plus layout and print guidance, before any UI code is written.
Refero Design
referodesign/refero_skill
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive…
Tailwind CSS Patterns
ever-works/ever-works
Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices.
Frontend Design Principles
pretend1111/claude-desktop-app
Gives practical design rules for polished HTML, CSS and JavaScript interfaces and browser games, covering spacing, type, color, components, motion and responsive breakpoints.
Tailwindcss Development
cachethq/core
A skill your agent uses for Cachet Tailwind CSS and UI styling: Blade utility classes, public status-page components, Filament dashboard theme work, responsive layout, dark mode, spacing…
More from Orange-OpenSource/Orange-Boosted-Bootstrap
All 13 skills in this repoToken System
Orange-OpenSource/Orange-Boosted-Bootstrap
OUDS design token system rules and architecture. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
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.
Code Review
Orange-OpenSource/Orange-Boosted-Bootstrap
OUDS Web compliance code review. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Create Component
Orange-OpenSource/Orange-Boosted-Bootstrap
Step-by-step workflow for creating a new SCSS and/or JavaScript component in OUDS Web.
Diagnose Errors
Orange-OpenSource/Orange-Boosted-Bootstrap
Diagnostic workflow for build, lint, CI, and test errors in OUDS Web.
Javascript Conventions
Orange-OpenSource/Orange-Boosted-Bootstrap
JavaScript coding conventions for OUDS Web. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Related
Categories
Questions about Component Patterns
What does Component Patterns do?
SCSS and JS structural patterns for OUDS Web components. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Component Patterns is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. SCSS and JS structural patterns for OUDS Web components.
When should I use Component Patterns?
Component Patterns fits situations like: reviewing component SCSS files (scss/.scss; scss/forms/.scss); JS component files (js/src/.js).
How do I install Component Patterns in Claude Code?
Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a claude-code`. Or copy the skill folder (.github/skills/component-patterns in Orange-OpenSource/Orange-Boosted-Bootstrap) into .claude/skills/component-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Component Patterns in Codex?
Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill component-patterns -a codex`. Or copy the skill folder (.github/skills/component-patterns in Orange-OpenSource/Orange-Boosted-Bootstrap) into .agents/skills/component-patterns in your project. Codex loads it when a task matches its description.
Can I use Component Patterns 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 component-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/component-patterns, .gemini/skills/component-patterns, .github/skills/component-patterns and .opencode/skills/component-patterns in your project.
What does Component Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Component Patterns is instructions for the agent only.
Does Component Patterns 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 Component Patterns 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 Component Patterns use?
Component Patterns 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 Component Patterns use?
About 773 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.
What are the alternatives to Component Patterns?
Skills that share tags, products or a category with Component Patterns: UI Styling (Ohh-889/skyroc, 795 stars), Frontend Design Router (code-yeongyu/oh-my-openagent, 70k stars), Refero Design (referodesign/refero_skill, 292 stars) and Tailwind CSS Patterns (ever-works/ever-works, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Component Patterns?
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.