Web Style Extractor
Lucent-Snow/style-extractor
Extracts evidence-backed style guides and motion appendices from websites, keeping reusable visual language and stripping product-specific content.
Create new web components in the Helvetia Design System. An agent skill from baloise/design-system.
$ npx skills add baloise/design-system --skill ds-create-component -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install baloise/design-system ds-create-component --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/baloise/design-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ds-create-component .claude/skills/ds-create-component && 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 "ds-create-component" agent skill from https://github.com/baloise/design-system/tree/next/.claude/skills/ds-create-component into .claude/skills/ds-create-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ds-create-component", 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/baloise/design-system/tree/next/.claude/skills/ds-create-componentType 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 baloise/design-system --skill ds-create-component -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install baloise/design-system ds-create-component --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baloise/design-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ds-create-component .agents/skills/ds-create-component && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ds-create-component" agent skill from https://github.com/baloise/design-system/tree/next/.claude/skills/ds-create-component into .agents/skills/ds-create-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ds-create-component", 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 baloise/design-system --skill ds-create-component -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install baloise/design-system ds-create-component --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baloise/design-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ds-create-component .cursor/skills/ds-create-component && 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 "ds-create-component" agent skill from https://github.com/baloise/design-system/tree/next/.claude/skills/ds-create-component into .cursor/skills/ds-create-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ds-create-component", 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/baloise/design-system.git --path .claude/skills/ds-create-component--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 baloise/design-system --skill ds-create-component -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install baloise/design-system ds-create-component --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baloise/design-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ds-create-component .gemini/skills/ds-create-component && 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 "ds-create-component" agent skill from https://github.com/baloise/design-system/tree/next/.claude/skills/ds-create-component into .gemini/skills/ds-create-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ds-create-component", 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 baloise/design-system ds-create-componentInstalls 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 baloise/design-system --skill ds-create-component -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/baloise/design-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ds-create-component .github/skills/ds-create-component && 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 "ds-create-component" agent skill from https://github.com/baloise/design-system/tree/next/.claude/skills/ds-create-component into .github/skills/ds-create-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ds-create-component", 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 baloise/design-system --skill ds-create-component -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install baloise/design-system ds-create-component --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baloise/design-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ds-create-component .opencode/skills/ds-create-component && 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 "ds-create-component" agent skill from https://github.com/baloise/design-system/tree/next/.claude/skills/ds-create-component into .opencode/skills/ds-create-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ds-create-component", 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.
ds-create-componentCreate new web components in the Helvetia Design System. An agent skill from baloise/design-system.
Ds Create Component is an agent skill from baloise/design-system. Create new web components in the Helvetia Design System. Generates Stencil component files with shadow DOM, interfaces, SCSS with design tokens, and visual HTML. Use when building a new component, migrating from the old design system, or creating subcomponents.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `README.md`, `REFERENCE.md` and `implementation.js`).
It sits in Frontend & Design, covering Design systems, CSS and styling and Design tokens. The repository describes itself as: The Baloise Design System consists of reusable components and a clearly defined visual style, that can be assembled together to build any number of applications. The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 19063c5. It shows what the files ask for, not the result of running them.
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.
Ships script files (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
pnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ds Create Component loads about 2.1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 694 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.
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.
The full file from baloise/design-system at commit 19063c5, republished under its Apache-2.0 licence (© baloise). 694 words, ~2,088 tokens.
.claude/skills/ds-create-component/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Create new web components in the Helvetia Design System with a guided questionnaire. Generates all necessary files in one pass: .tsx, .interfaces.ts, .host.scss, and .visual.html.
/ds-create-componentThe skill will ask you a series of questions to understand your component, then generate all files at once.
The skill asks:
button, card, modalactions, forms, indicators, media, navigation, overlays, structure (see the taxonomy in packages/core/CONTEXT.md). Determines where the component is scaffolded: components/<category>/<name>/.propName: PropType = defaultValue (e.g., label: string = '', disabled: boolean = false)dsEventName (e.g., dsClick, dsChange)tab inside tabs)tab, tab-content)primary, secondary, danger)Once you answer all questions, the skill creates:
<component>.tsx — Stencil component with all props/events, basic render with <slot><component>.interfaces.ts — TypeScript types and enums for props<component>.host.scss — Shadow DOM styles with design token structure and variants<component>.visual.html — Visual test file with sections for each variant<component>/<subcomponent>/The skill:
--ds-alias-*) — all good--ds-<component>-*) — all good--ds-* without alias prefix) — warning with recommendation to create an alias tokenpackages/core/src/index.tsapps/storybook/src/components/<category>/<name>/; stories/MDX content is generated separately by /ds-document-componentAfter generation, the skill prints:
✅ Component created: packages/core/src/components/actions/button/
Storybook folder scaffolded: apps/storybook/src/components/actions/button/
Add stories/MDX with /ds-document-component.
Next steps:
1. Review the generated component files
2. Refine render() logic and add your component-specific code
3. Update SCSS variants if needed
4. Run: pnpm play
5. Create tests with /ds-sync-component-testsThe skill enforces these design system rules:
.host.scss only)shadow: true<slot> for light DOM contenttabs/tab.tsx, not tabs and tab at same level)components/<category>/<name>/, matching the folder's category taxonomypackages/core/src/index.tsds- prefix, ComponentInterface + Loggable implementation (see STYLE_GUIDE.md)Q: Component name?
A: badge
Q: Category?
A: indicators
Q: Component purpose?
A: Displays a small label with customizable color and size
Q: Migration from old design system?
A: no
Q: Props?
A: label: string = '', color: 'primary'|'secondary'|'danger' = '', size: 'sm'|'md'|'lg' = 'md'
Q: Events?
A: (none)
Q: Subcomponents?
A: no
Q: Variants?
A: primary, secondary, danger, small, medium, largeResult: Generated badge.tsx, badge.interfaces.ts, badge.host.scss, badge.visual.html
Q: Component name?
A: tabs
Q: Category?
A: navigation
Q: Component purpose?
A: Container for tab content with keyboard navigation and ARIA support
Q: Migration from old design system?
A: yes, old-tabs
(skill auto-extracts props/events from old-tabs)
Q: Props? (pre-filled from old-tabs, you review)
A: (accept defaults)
Q: Events? (pre-filled from old-tabs)
A: (accept defaults)
Q: Subcomponents?
A: yes
- tab
- tab-panel
Q: Variants?
A: horizontal, verticalResult: Generated:
tabs.tsx, tabs.interfaces.ts, tabs.host.scss, tabs.visual.htmltabs/tab/tab.tsx, tabs/tab/tab.interfaces.ts, tabs/tab/tab.host.scsstabs/tab-panel/tab-panel.tsx, tabs/tab-panel/tab-panel.interfaces.ts, tabs/tab-panel/tab-panel.host.scssPlus warnings if old component used global tokens (e.g., "⚠️ Using global token --ds-color-primary. Consider using alias token --ds-alias-color-primary or creating component token --ds-tabs-color-primary")
This skill only generates components. The following are handled by other skills:
/ds-sync-component-tests to create unit, interaction, visual, and a11y tests.stories.ts and .mdx files separatelypnpm buildWhen the skill validates tokens, it prints warnings like:
⚠️ Token Issue: Global token used
File: button.host.scss, line 25
Found: var(--ds-color-primary)
Recommendation:
1. Use alias token instead: var(--ds-alias-color-primary)
2. Or create a component token: --ds-button-color-primary
3. Add to Base.tokens.json and re-run: pnpm tokens
This is a warning only. You can proceed.
See: docs/agents/domain.md (Design tokens section)Q: "Component already exists" warning
A: The skill found an existing component. Review whether you should:
/ds-find-component)Q: "No alias token available" warning
A: A design token (e.g., --ds-alias-color-status) doesn't exist yet. Either:
packages/tokens/tokens/Base.tokens.jsonQ: How do I refine the generated component?
A: The generated .tsx file has a basic render() with <slot>. Add:
See REFERENCE.md for template structure and patterns.
© baloise, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in .claude/skills/ds-create-component of baloise/design-system.
Open the folder on GitHubat commit 19063c5
Ds Create Component 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 |
|---|---|---|---|---|---|---|
| Ds Create Component this skillbaloise/design-system | 114 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Web Style ExtractorLucent-Snow/style-extractor | 453 | — | ~3.8k | Automated safety check: Pass | None | |
| Tailwind Design SystemSuFxGIT/scoutarr | 114 | 5 repos | ~5.6k | Automated safety check: Pass | None | |
| Extract DesignManavarya09/design-extract | 4.2k | — | ~786 | Automated safety check: Notes | MIT | |
| Tailwind Design Systemjh941213/my-cc-harness | 126 | 10 repos | ~4.7k | Automated safety check: Pass | None | |
| Design System AnalyzerNakanoSanku/OhMySkills | 163 | — | ~1.2k | Automated safety check: Pass | None |
Lucent-Snow/style-extractor
Extracts evidence-backed style guides and motion appendices from websites, keeping reusable visual language and stripping product-specific content.
SuFxGIT/scoutarr
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns.
Manavarya09/design-extract
Extract the full design language from any website URL. An agent skill from Manavarya09/design-extract.
jh941213/my-cc-harness
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns.
NakanoSanku/OhMySkills
Inspects a live website through Chrome DevTools and turns its CSS tokens, animations and hover states into a design system prompt.
ever-works/ever-works
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React.
baloise/design-system
Migrate a consuming app from the Baloise Design System (bal-) to the Helvetia Design System (ds-).
baloise/design-system
Create a changeset entry for pending changes using the repo's create-changeset.mjs CLI.
baloise/design-system
Lint and fix Helvetia Design System components for style guide compliance.
baloise/design-system
Auto-generate all test files for DS components including visual, a11y, component, page object, and unit tests.
baloise/design-system
Check a component's design tokens in Base.tokens.json against the canonical naming convention (packages/tokens/CONTEXT.md "Token Naming Anatomy"), report violations as a markdown table, and apply…
baloise/design-system
Post the /update-screenshots bot command as a PR comment to re-baseline visual regression snapshots for one or more components.
Categories
Create new web components in the Helvetia Design System. An agent skill from baloise/design-system. Ds Create Component is an agent skill from baloise/design-system. Create new web components in the Helvetia Design System.
Ds Create Component fits situations like: building a new component; migrating from the old design system; creating subcomponents.
Run `npx skills add baloise/design-system --skill ds-create-component -a claude-code`. Or copy the skill folder (.claude/skills/ds-create-component in baloise/design-system) into .claude/skills/ds-create-component in your project. Claude Code loads it when a task matches its description.
Run `npx skills add baloise/design-system --skill ds-create-component -a codex`. Or copy the skill folder (.claude/skills/ds-create-component in baloise/design-system) into .agents/skills/ds-create-component in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add baloise/design-system --skill ds-create-component -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ds-create-component, .gemini/skills/ds-create-component, .github/skills/ds-create-component and .opencode/skills/ds-create-component in your project.
Going by SKILL.md and its folder, Ds Create Component needs JavaScript for the scripts in its folder and the command-line tools its instructions call (pnpm). Our summary lists: Node.js.
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.
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.
Ds Create Component is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ds Create Component: Web Style Extractor (Lucent-Snow/style-extractor, 453 stars), Tailwind Design System (SuFxGIT/scoutarr, 114 stars), Extract Design (Manavarya09/design-extract, 4.2k stars) and Tailwind Design System (jh941213/my-cc-harness, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
baloise (a GitHub organization) maintains it in baloise/design-system, which has 114 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: baloise/design-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.