Stream Builder
adrianhajdin/react-native-lingua
Build a new app or add Stream products (Chat, Video, Feeds, Moderation) to an existing app.
Guides migration of a web project to OUDS Web (Orange Unified Design System).
Install Migrate To Ouds Web
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill migrate-to-ouds-web -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap migrate-to-ouds-web --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/skills/migrate-to-ouds-web .claude/skills/migrate-to-ouds-web && 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 "migrate-to-ouds-web" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/skills/migrate-to-ouds-web into .claude/skills/migrate-to-ouds-web/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-to-ouds-web", 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/skills/migrate-to-ouds-webType 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 migrate-to-ouds-web -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap migrate-to-ouds-web --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/skills/migrate-to-ouds-web .agents/skills/migrate-to-ouds-web && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migrate-to-ouds-web" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/skills/migrate-to-ouds-web into .agents/skills/migrate-to-ouds-web/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-to-ouds-web", 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 migrate-to-ouds-web -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap migrate-to-ouds-web --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/skills/migrate-to-ouds-web .cursor/skills/migrate-to-ouds-web && 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 "migrate-to-ouds-web" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/skills/migrate-to-ouds-web into .cursor/skills/migrate-to-ouds-web/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-to-ouds-web", 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 skills/migrate-to-ouds-web--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 migrate-to-ouds-web -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap migrate-to-ouds-web --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/skills/migrate-to-ouds-web .gemini/skills/migrate-to-ouds-web && 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 "migrate-to-ouds-web" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/skills/migrate-to-ouds-web into .gemini/skills/migrate-to-ouds-web/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-to-ouds-web", 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 migrate-to-ouds-webInstalls 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 migrate-to-ouds-web -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/skills/migrate-to-ouds-web .github/skills/migrate-to-ouds-web && 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 "migrate-to-ouds-web" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/skills/migrate-to-ouds-web into .github/skills/migrate-to-ouds-web/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-to-ouds-web", 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 migrate-to-ouds-web -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 migrate-to-ouds-web --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/skills/migrate-to-ouds-web .opencode/skills/migrate-to-ouds-web && 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 "migrate-to-ouds-web" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/skills/migrate-to-ouds-web into .opencode/skills/migrate-to-ouds-web/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-to-ouds-web", 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
migrate-to-ouds-web- GitHub stars
- 222
- Token cost
- ~1.2k tokens
- SKILL.md length
- 456 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides migration of a web project to OUDS Web (Orange Unified Design System).
- Works in 5 steps: Detect source library → Choose file glob → Run the migration tool → …
- The user wants to migrate from OB1 (@ob1/web)
- SKILL.md covers Step 1 — Detect source library, Step 2 — Choose file glob, Step 3 — Run the migration tool and Step 4 — Resolve warnings…, plus 4 more sections
- Calls npx and git
What it does
Migrate To Ouds Web is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Guides migration of a web project to OUDS Web (Orange Unified Design System). Use when the user wants to migrate from OB1 (@ob1/web), Boosted, or an older OUDS Web version to the latest OUDS Web. Covers: detecting source library from package.json, running npx @ouds/web-migrate with correct --from flag and glob pattern, and resolving manual migration warnings by finding correct OUDS Web component markup using the using-ouds-web skill. Triggers on: migrate to OUDS Web, migration from Boosted, migration from OB1…
Its SKILL.md is about 1.2k 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 Source-grounded notebooks, Design systems and CSS and styling. It works with npm. 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
- The user wants to migrate from OB1 (@ob1/web)
- An older OUDS Web version to the latest OUDS Web
- : migrate to OUDS Web
- Migration from Boosted
Example prompts
- “Use the migrate-to-ouds-web skill to guide migration of a web project to OUDS Web (Orange Unified Design System)”
- “/migrate-to-ouds-web”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 49c53aa. 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
Shell commands in SKILL.md call:
npxgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and git, which can reach the network depending on how they are called.
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
Migrate To Ouds Web loads about 1.2k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 456 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 49c53aa, republished under its MIT licence (© Orange-OpenSource). 456 words, ~1,243 tokens.
Download SKILL.mdSave it as
.claude/skills/migrate-to-ouds-web/SKILL.md (or your agent's skills folder).- name
- migrate-to-ouds-web
- description
- Guides migration of a web project to OUDS Web (Orange Unified Design System). Use when the user wants to migrate from OB1 (@ob1/web), Boosted, or an older OUDS Web version to the latest OUDS Web. Covers: detecting source library from package.json, running npx @ouds/web-migrate with correct --from flag and glob pattern, and resolving manual migration warnings by finding correct OUDS Web component markup using the using-ouds-web skill. Triggers on: migrate to OUDS Web, migration from Boosted, migration from OB1, @ouds/web-migrate, update OUDS Web version.
Migrate to OUDS Web
Step-by-step workflow for migrating a project to OUDS Web using the @ouds/web-migrate CLI tool.
Step 1 — Detect source library
Read the project's package.json (dependencies and devDependencies) and map to the correct --from flag:
| Dependency found | --from flag | Migration source |
|---|---|---|
@ob1/web | --from=ob1 | OB1 |
boosted | --from=boosted | Boosted |
@ouds/web-common | (omit flag, default) | Older OUDS Web |
| None found | Ask the user | Unknown |
If ouds-web or @ouds/web-orange is already present, the project is either fully migrated or partially migrated — confirm with the user before proceeding. If the user confirms, update the dependencies to the latest OUDS Web version. Detect the installed OUDS Web version from the project's lockfile (package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lock/bun.lockb) or package.json, then use the matching using-ouds-web-version-<major>-<minor> skill afterward.
Step 2 — Choose file glob
Inspect the project file types and pick a safe glob. Never use "**/*.*" — it modifies binary and unrelated files.
| Project type | Recommended glob |
|---|---|
| HTML/CSS only | "**/*.{css,scss,html}" |
| React (JSX/TSX) | "**/*.{css,scss,html,jsx,tsx}" |
| Vue | "**/*.{css,scss,html,vue}" |
| Angular | "**/*.{css,scss,html,ts}" |
| Default (safe) | "**/*.{css,scss,html}" |
Advise running in a version-controlled folder so changes can be reviewed with git diff.
Step 3 — Run the migration tool
# Migrate from Boosted
npx @ouds/web-migrate --from=boosted "**/*.{css,scss,html}"
# Migrate from OB1 (Vue project)
npx @ouds/web-migrate --from=ob1 "**/*.{css,scss,html,vue}"
# Update to latest OUDS Web version (from older OUDS)
npx @ouds/web-migrate "**/*.{css,scss,html}"The tool:
- Automatically replaces known class names using regex
- Emits warnings for deprecated/removed classes that require manual follow-up (one line per change needed)
Step 4 — Resolve warnings (manual steps)
For each warning line in the output:
- Identify the component or class name mentioned in the warning
- Invoke the
using-ouds-web-version-<major>-<minor>skill to find the correct OUDS Web HTML structure for that component - Apply the replacement manually in the affected files
Example: if the warning mentions .alert-success, look up alerts in using-ouds-web-version-<major>-<minor> references to find the correct .alert-positive / .alert-neutral structure.
Show full SKILL.md (184 more words)Show less
Step 5 — Post-migration checklist
- Review
git diffto verify all automated replacements are correct - Update
package.json: replaceboosted/@ob1/webwith@ouds/web-commonplus exactly one theme package (for example,@ouds/web-orange) - Update Sass/CSS imports (e.g.
@import "boosted"→@import "ouds-web") - Update CDN links in HTML files (
boosted.min.css→ouds-web.min.css) - Search for leftover
class=" "artifacts — the tool does not remove empty class attributes - Verify responsive breakpoints: OUDS Web uses 8 breakpoints with prefix syntax
{bp}:{utility}-{value}(e.g.lg:col-6), not Bootstrap infix format (col-lg-6)
Known tool limitations
- Empty
class=" "attributes are left in place after class removal — clean up manually - Custom responsive classes with infixes (e.g.
something-2xl-left) get renamed to2xl:something-left— review these carefully - Always inspect the diff before committing
Anti-patterns
- ❌ Don't guess source library from class names — always check
package.jsonfirst - ❌ Don't use
"**/*.*"glob — modifies binary and irrelevant files - ❌ Don't stop after automated replacements — warnings require manual action
- ❌ Don't skip the
git diffreview — automated replacements may need adjustment
References
- Use the
using-ouds-web-version-<major>-<minor>skill for target component markup and class lookup during manual warning resolution packages/migrate/README.md— full@ouds/web-migrateoptions and examplesusing-ouds-web-version-<major>-<minor>/references/getting-started/migration-from-boosted.md— component-by-component Boosted→OUDS Web changesusing-ouds-web-version-<major>-<minor>/references/getting-started/migration.md— OUDS Web version-to-version changes
© 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 skills/migrate-to-ouds-web of Orange-OpenSource/Orange-Boosted-Bootstrap.
Open the folder on GitHubat commit 49c53aa
Compare with similar skills
Migrate To Ouds Web 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 |
|---|---|---|---|---|---|---|
| Migrate To Ouds Web this skillOrange-OpenSource/Orange-Boosted-Bootstrap | 222 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Stream Builderadrianhajdin/react-native-lingua | 152 | — | ~5.4k | Automated safety check: Notes | None | |
| Light Frontend DesignLight0305/Light-skills | 640 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Aceternity UIsecondsky/claude-skills | 227 | — | ~4.7k | Automated safety check: Pass | MIT | |
| daisyUI 5 Installationsaadeghi/daisyui | 43k | — | ~967 | Automated safety check: Pass | MIT | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Light Frontend Design
Light0305/Light-skills
Light 按需工程技能·前端设计：把模糊的「做个好看的界面」落成能跑的 React/Tailwind/shadcn 代码 + 设计决策说明—— 有视觉记忆点(signature element)、风格自洽(design tokens 一致)、适配场景(学术海报/数据大屏/管理后台/移动端/营销 landing 信息密度各不同)、反「一眼 AI」(紫蓝渐变/Inter/16px 圆角/巨型…
Aceternity UI
secondsky/claude-skills
100+ animated React components (Aceternity UI) for Next.js with Tailwind.
daisyUI 5 Installation
saadeghi/daisyui
Installation instructions for daisyUI 5 with Tailwind CSS 4: the npm setup, CSS plugin lines, CDN usage and pointers to framework-specific guides.
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.
Coss
crafter-station/petdex
Helps implement coss UI components correctly. An agent skill from crafter-station/petdex.
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.
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.
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.
Related
Works with
Categories
Questions about Migrate To Ouds Web
What does Migrate To Ouds Web do?
Guides migration of a web project to OUDS Web (Orange Unified Design System). Migrate To Ouds Web is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Guides migration of a web project to OUDS Web (Orange Unified Design System).
When should I use Migrate To Ouds Web?
Migrate To Ouds Web fits situations like: the user wants to migrate from OB1 (@ob1/web); an older OUDS Web version to the latest OUDS Web; : migrate to OUDS Web; migration from Boosted.
How do I install Migrate To Ouds Web in Claude Code?
Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill migrate-to-ouds-web -a claude-code`. Or copy the skill folder (skills/migrate-to-ouds-web in Orange-OpenSource/Orange-Boosted-Bootstrap) into .claude/skills/migrate-to-ouds-web in your project. Claude Code loads it when a task matches its description.
How do I install Migrate To Ouds Web in Codex?
Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill migrate-to-ouds-web -a codex`. Or copy the skill folder (skills/migrate-to-ouds-web in Orange-OpenSource/Orange-Boosted-Bootstrap) into .agents/skills/migrate-to-ouds-web in your project. Codex loads it when a task matches its description.
Can I use Migrate To Ouds Web 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 migrate-to-ouds-web -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-to-ouds-web, .gemini/skills/migrate-to-ouds-web, .github/skills/migrate-to-ouds-web and .opencode/skills/migrate-to-ouds-web in your project.
What does Migrate To Ouds Web need to run?
Going by SKILL.md and its folder, Migrate To Ouds Web needs the command-line tools its instructions call (npx and git). Our summary lists: Node.js.
Does Migrate To Ouds Web access the network?
SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Migrate To Ouds Web 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 Migrate To Ouds Web use?
Migrate To Ouds Web 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 Migrate To Ouds Web use?
About 1.2k tokens (SKILL.md is roughly 5k 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 Migrate To Ouds Web?
Skills that share tags, products or a category with Migrate To Ouds Web: Stream Builder (adrianhajdin/react-native-lingua, 152 stars), Light Frontend Design (Light0305/Light-skills, 640 stars), Aceternity UI (secondsky/claude-skills, 227 stars) and daisyUI 5 Installation (saadeghi/daisyui, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migrate To Ouds Web?
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 9, 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.