Connect Component To Figma
dequelabs/cauldron
Add a Figma Code Connect (.figma.tsx) file for a Cauldron React component.
Apply the formal standard for React component engineering focusing on accessibility, composition, and styling.
Install Component Engineering
$ npx skills add IgorWarzocha/Opencode-Workflows --skill component-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows component-engineering --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/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/component-engineer/.opencode/skill/component-engineering .claude/skills/component-engineering && 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-engineering" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineering into .claude/skills/component-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-engineering", 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/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineeringType 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 IgorWarzocha/Opencode-Workflows --skill component-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows component-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/component-engineer/.opencode/skill/component-engineering .agents/skills/component-engineering && 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-engineering" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineering into .agents/skills/component-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-engineering", 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 IgorWarzocha/Opencode-Workflows --skill component-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows component-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/component-engineer/.opencode/skill/component-engineering .cursor/skills/component-engineering && 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-engineering" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineering into .cursor/skills/component-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-engineering", 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/IgorWarzocha/Opencode-Workflows.git --path agents/component-engineer/.opencode/skill/component-engineering--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 IgorWarzocha/Opencode-Workflows --skill component-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows component-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/component-engineer/.opencode/skill/component-engineering .gemini/skills/component-engineering && 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-engineering" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineering into .gemini/skills/component-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-engineering", 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 IgorWarzocha/Opencode-Workflows component-engineeringInstalls 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 IgorWarzocha/Opencode-Workflows --skill component-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/component-engineer/.opencode/skill/component-engineering .github/skills/component-engineering && 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-engineering" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineering into .github/skills/component-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-engineering", 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 IgorWarzocha/Opencode-Workflows --skill component-engineering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows component-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/component-engineer/.opencode/skill/component-engineering .opencode/skills/component-engineering && 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-engineering" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/component-engineer/.opencode/skill/component-engineering into .opencode/skills/component-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-engineering", 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-engineering- GitHub stars
- 122
- Token cost
- ~588 tokens
- SKILL.md length
- 203 words
- Files
- 7 (incl. references)
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- None found
At a glance
Apply the formal standard for React component engineering focusing on accessibility, composition, and styling.
- Works in 5 steps: You MUST read all reference files in the… → Classify the artifact using taxonomy.md. → Evaluate Accessibility: You MUST check… → …
- Building professional
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Composable React artifacts
What it does
Component Engineering is an agent skill from IgorWarzocha/Opencode-Workflows. Apply the formal standard for React component engineering focusing on accessibility, composition, and styling. Use for building professional, composable React artifacts. Use proactively when creating or reviewing React components. Examples: - user: "/component-create Button trigger" → build accessible button with asChild and keyboard map - user: "/component-review src/components/Input.tsx" → audit for accessibility and composition compliance - user: "Build a responsive slider" → select taxonomy type and implement…
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/accessibility.md`, `references/composition.md` and `references/distribution.md`).
It sits in Frontend & Design, covering React components and Accessibility. It works with React. The repository describes itself as: An ever evolving repository of Opencode workflow examples that might enhance your experience with it. I only left the stuff that actually works. YMMV.
When your agent uses it
- Building professional
- Composable React artifacts
Example prompts
- “/component-create Button trigger”
- “/component-review src/components/Input.tsx”
- “Build a responsive slider”
- “/component-engineering”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- You MUST read all reference files in the references/ directory before proceeding.
- Classify the artifact using taxonomy.md.
- Evaluate Accessibility: You MUST check keyboard support and semantic HTML against accessibility.md.
- Evaluate Architecture: You MUST check for monolithic patterns vs composition against composition.md.
- Evaluate Styling: Look for data-slot usage and prop spreading against styling.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6444ec4. 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.
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 Engineering loads about 588 tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 161 tokens; SKILL.md has 203 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 203 words (~588 tokens).
“This skill embodies the formal standard for building professional, accessible, and composable React artifacts.”
- name
- component-engineering
Files
SKILL.md and 6 other files (references) in agents/component-engineer/.opencode/skill/component-engineering of IgorWarzocha/Opencode-Workflows.
- SKILL.md
- references/accessibility.md
- references/composition.md
- references/distribution.md
- references/patterns.md
- references/styling.md
- references/taxonomy.md
Open the folder on GitHubat commit 6444ec4
Compare with similar skills
Component Engineering 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 Engineering this skillIgorWarzocha/Opencode-Workflows | 122 | — | ~588 | Automated safety check: Pass | None | |
| Connect Component To Figmadequelabs/cauldron | 129 | — | ~2k | Automated safety check: Pass | MPL-2.0 | |
| A11y Auditscaleway/ultraviolet | 127 | — | ~979 | Automated safety check: Pass | Apache-2.0 | |
| Framer Component Best Practicesframer/plugins | 138 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Base UI Reactsecondsky/claude-skills | 227 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Stitch to React and Vite Dashboardgoogle-labs-code/stitch-skills | 8.4k | — | ~914 | Automated safety check: Notes | Apache-2.0 |
Similar skills
A11y Audit
scaleway/ultraviolet
Audit components for accessibility. An agent skill from scaleway/ultraviolet.
Framer Component Best Practices
framer/plugins
Best practices for building and improving React code components in Framer, a no-code website builder.
Base UI React
secondsky/claude-skills
MUI Base UI unstyled React components with Floating UI. An agent skill from secondsky/claude-skills.
- Official
Stitch to React and Vite Dashboard
google-labs-code/stitch-skills
Turns Stitch screens into a React, Vite and TypeScript dashboard with TanStack Query data fetching, DESIGN.md tokens as CSS variables and optional read-only Web3 data.
Design Code for Any Framework
plugin87/ux-ui-agent-skills
Generates complete, accessible, token-driven UI component code for a chosen framework such as React with Tailwind, SwiftUI, Vue, Flutter or Jetpack Compose.
More from IgorWarzocha/Opencode-Workflows
All 37 skills in this repoCreate Opencode Plugin
IgorWarzocha/Opencode-Workflows
Create OpenCode plugins using the @opencode-ai/plugin SDK. An agent skill from IgorWarzocha/Opencode-Workflows.
Plugin Installer
IgorWarzocha/Opencode-Workflows
Find, install, and configure OpenCode plugins from the catalog or community.
Skill Creator
IgorWarzocha/Opencode-Workflows
Guide for creating effective opencode skills. An agent skill from IgorWarzocha/Opencode-Workflows.
Security AI Keys
IgorWarzocha/Opencode-Workflows
Review AI API key leakage patterns and redaction strategies.
Security Convex
IgorWarzocha/Opencode-Workflows
Review Convex security audit patterns for authentication and authorization.
Security Django
IgorWarzocha/Opencode-Workflows
Review Django security audit patterns for settings and middleware.
Related
Works with
Categories
Questions about Component Engineering
What does Component Engineering do?
Apply the formal standard for React component engineering focusing on accessibility, composition, and styling. Component Engineering is an agent skill from IgorWarzocha/Opencode-Workflows. Apply the formal standard for React component engineering focusing on accessibility, composition, and styling.
When should I use Component Engineering?
Component Engineering fits situations like: building professional; composable React artifacts.
How do I install Component Engineering in Claude Code?
Run `npx skills add IgorWarzocha/Opencode-Workflows --skill component-engineering -a claude-code`. Or copy the skill folder (agents/component-engineer/.opencode/skill/component-engineering in IgorWarzocha/Opencode-Workflows) into .claude/skills/component-engineering in your project. Claude Code loads it when a task matches its description.
How do I install Component Engineering in Codex?
Run `npx skills add IgorWarzocha/Opencode-Workflows --skill component-engineering -a codex`. Or copy the skill folder (agents/component-engineer/.opencode/skill/component-engineering in IgorWarzocha/Opencode-Workflows) into .agents/skills/component-engineering in your project. Codex loads it when a task matches its description.
Can I use Component Engineering 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 IgorWarzocha/Opencode-Workflows --skill component-engineering -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-engineering, .gemini/skills/component-engineering, .github/skills/component-engineering and .opencode/skills/component-engineering in your project.
What does Component Engineering need to run?
SKILL.md names no scripts, command-line tools or credentials: Component Engineering is instructions for the agent only.
Does Component Engineering 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 Engineering 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 Engineering use?
No licence was found for Component Engineering or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Component Engineering use?
About 588 tokens (SKILL.md is roughly 2.4k 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 2.2k tokens, read only when the agent opens those files.
What are the alternatives to Component Engineering?
Skills that share tags, products or a category with Component Engineering: Connect Component To Figma (dequelabs/cauldron, 129 stars), A11y Audit (scaleway/ultraviolet, 127 stars), Framer Component Best Practices (framer/plugins, 138 stars) and Base UI React (secondsky/claude-skills, 227 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Component Engineering?
IgorWarzocha (a GitHub user) maintains it in IgorWarzocha/Opencode-Workflows, which has 122 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on February 4, 2026.
Source: IgorWarzocha/Opencode-Workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.