Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
The Yosys/nextpnr toolchain in ONE WARE Studio — which device setting key controls which stage of the compile, what the build produces, and how to read a failed synthesis, place & route or bitstream…
Install Fpga Toolchain Yosys
$ npx skills add one-ware/OneWare --skill fpga-toolchain-yosys -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install one-ware/OneWare fpga-toolchain-yosys --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/one-ware/OneWare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys .claude/skills/fpga-toolchain-yosys && 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 "fpga-toolchain-yosys" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys into .claude/skills/fpga-toolchain-yosys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-toolchain-yosys", 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/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosysType 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 one-ware/OneWare --skill fpga-toolchain-yosys -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install one-ware/OneWare fpga-toolchain-yosys --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys .agents/skills/fpga-toolchain-yosys && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fpga-toolchain-yosys" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys into .agents/skills/fpga-toolchain-yosys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-toolchain-yosys", 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 one-ware/OneWare --skill fpga-toolchain-yosys -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install one-ware/OneWare fpga-toolchain-yosys --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys .cursor/skills/fpga-toolchain-yosys && 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 "fpga-toolchain-yosys" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys into .cursor/skills/fpga-toolchain-yosys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-toolchain-yosys", 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/one-ware/OneWare.git --path src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys--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 one-ware/OneWare --skill fpga-toolchain-yosys -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install one-ware/OneWare fpga-toolchain-yosys --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys .gemini/skills/fpga-toolchain-yosys && 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 "fpga-toolchain-yosys" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys into .gemini/skills/fpga-toolchain-yosys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-toolchain-yosys", 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 one-ware/OneWare fpga-toolchain-yosysInstalls 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 one-ware/OneWare --skill fpga-toolchain-yosys -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys .github/skills/fpga-toolchain-yosys && 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 "fpga-toolchain-yosys" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys into .github/skills/fpga-toolchain-yosys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-toolchain-yosys", 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 one-ware/OneWare --skill fpga-toolchain-yosys -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install one-ware/OneWare fpga-toolchain-yosys --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys .opencode/skills/fpga-toolchain-yosys && 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 "fpga-toolchain-yosys" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys into .opencode/skills/fpga-toolchain-yosys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-toolchain-yosys", 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
fpga-toolchain-yosys- GitHub stars
- 147
- Token cost
- ~1.2k tokens
- SKILL.md length
- 634 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
The Yosys/nextpnr toolchain in ONE WARE Studio — which device setting key controls which stage of the compile, what the build produces, and how to read a failed synthesis, place & route or bitstream…
- Works in 3 steps: Synthesis — yosys reads the HDL sources… → Place & Route — a nextpnr-* binary reads… → Bitstream — a pack tool (icepack,…
- Development work in your project
- SKILL.md covers Configuring the stages, Reading a failed compile and Programming
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Fpga Toolchain Yosys is an agent skill from one-ware/OneWare. The Yosys/nextpnr toolchain in ONE WARE Studio — which device setting key controls which stage of the compile, what the build produces, and how to read a failed synthesis, place & route or bitstream run.
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 Development. The repository describes itself as: Next Generation IDE for Electronics Development. The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “/fpga-toolchain-yosys”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Synthesis — yosys reads the HDL sources and writes build/synth.json.
- Place & Route — a nextpnr-* binary reads build/synth.json and the constraint file and
- Bitstream — a pack tool (icepack, ecppack, gowin_pack, gmpack) turns that into the
What it can do on your machine
Read from SKILL.md and the folder at commit bbc4d99. 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
Fpga Toolchain Yosys loads about 1.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 634 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 one-ware/OneWare at commit bbc4d99, republished under its Apache-2.0 licence (© one-ware). 634 words, ~1,218 tokens.
Download SKILL.mdSave it as
.claude/skills/fpga-toolchain-yosys/SKILL.md (or your agent's skills folder).- name
- fpga-toolchain-yosys
- description
- The Yosys/nextpnr toolchain in ONE WARE Studio — which device setting key controls which stage of the compile, what the build produces, and how to read a failed synthesis, place & route or bitstream run.
The Yosys toolchain
The yosys toolchain compiles an FPGA project in three stages that run in this order:
- Synthesis —
yosysreads the HDL sources and writesbuild/synth.json. - Place & Route — a
nextpnr-*binary readsbuild/synth.jsonand the constraint file and writes the placed and routed design intobuild/. - Bitstream — a pack tool (
icepack,ecppack,gowin_pack,gmpack) turns that into the bitstream inbuild/.
Everything is written below build/ in the project folder. That folder is in the project's
exclude list, so it does not show up as project content.
A stage only runs when the previous one succeeded. Each stage deletes its own stale output before it starts and verifies that the expected artifact exists afterwards, so a build can never silently reuse a result from an earlier run. This matters when reading a failed compile: the first reported error is the real one, and there is no risk that a "successful" place & route was in fact routing yesterday's netlist.
Configuring the stages
These are device settings of the selected board, stored in
device-settings/<board>.deviceconf. Read them with fpga_list_device_settings and change them
with fpga_set_device_setting. The same values are what the Toolchain Settings dialog under
Compile shows, grouped into Synthesis, Place & Route and Bitstream.
Synthesis (Yosys)
| Key | Meaning |
|---|---|
yosysToolchainYosysSynthTool | The synth_* command for the target family, e.g. synth_ice40, synth_ecp5, synth_gowin. Must match the board. |
yosysToolchainYosysFlags | Extra flags passed to yosys. |
yosysToolchainCommand | Overrides the generated yosys script command entirely. Leave empty unless the default pipeline does not fit. |
yosysQuietFlag | true suppresses the yosys output. The dialog exposes the inverse as Yosys Verbose. |
Place & Route (nextpnr)
| Key | Meaning |
|---|---|
yosysToolchainNextPnrTool | The nextpnr-* binary, e.g. nextpnr-ice40, nextpnr-ecp5, nextpnr-himbaechel. Must match the synth tool's family. |
yosysToolchainNextPnrFlags | Extra flags, typically the device and package selection. |
yosysToolchainConstraintFileType | pcf or ccf — the constraint format the board uses. |
yosysToolchainOutputType | asc or txt — the place & route output format the pack tool expects. |
yosysToolchainNextPnrVerbose | true adds --verbose and shows the full nextpnr output in the Output panel. Turn this on when diagnosing timing or placement problems. |
Bitstream (pack)
| Key | Meaning |
|---|---|
yosysToolchainPackTool | icepack, ecppack, gowin_pack or gmpack, matching the family. |
yosysToolchainPackFlags | Extra flags for the pack tool. |
packToolOutputFormat | bin or bit. |
The three tool selections must agree on the FPGA family: synth_ice40 + nextpnr-ice40 +
icepack is consistent, mixing families is not. The hardware package of a board ships correct
defaults, so only change them when the user targets a device the package does not cover.
Show full SKILL.md (232 more words)Show less
Reading a failed compile
The compile output goes to the Output panel, prefixed with the project name. A tool that exits with
a non-zero status, or that prints a line starting with Error: / ERROR:, fails the stage and
stops the build.
| Symptom | Cause |
|---|---|
ERROR: Module ... not found from yosys | A source file is missing from the project or is in compileExcluded. |
ERROR: Can't open input file from yosys | The top entity name does not match any module. Check fpga_list_top_entities. |
Cannot run place & route: build/synth.json is missing | Synthesis did not produce a netlist — fix the synthesis error above it. |
| nextpnr reports unconstrained or unknown pins | The constraint file does not match the design. Assign the pins in the constraint editor. |
... exited with code N with no other error | The tool failed without a parseable message; the verbose option for that stage usually reveals why. |
Do not re-run an identical build to "see if it works this time". The stages are deterministic and a stale artifact can no longer mask a failure.
Programming
After a successful build the loader writes the bitstream to the hardware:
- Config FPGA loads the bitstream into the FPGA's volatile configuration. It is gone after a power cycle.
- Write FLASH Memory writes it into the board's FLASH, so the FPGA loads it on every power-up.
Both need a bitstream from a completed build; the loader refuses to start without one.
© one-ware, 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
Files
Just SKILL.md in src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys of one-ware/OneWare.
Open the folder on GitHubat commit bbc4d99
Compare with similar skills
Fpga Toolchain Yosys 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 |
|---|---|---|---|---|---|---|
| Fpga Toolchain Yosys this skillone-ware/OneWare | 147 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from one-ware/OneWare
Oneware Module
one-ware/OneWare
Creates or wires up a OneWare feature module (built-in src/OneWare.
Fpga Project File
one-ware/OneWare
Format of a ONE WARE Studio .fpgaproj file and of the .deviceconf and .tbconf files next to it — which key means what, which ones have a dedicated fpga function, and which ones may only be edited by…
Fpga Studio Control
one-ware/OneWare
How to drive ONE WARE Studio's FPGA project system from chat — which fpga function to call for creating a project, selecting board/toolchain/loader, setting the top entity, compiling, and running…
Oneware Styling
one-ware/OneWare
Styles OneWare Avalonia UI with the shared design system (tokens, classes, icons, control themes).
Oneware Release
one-ware/OneWare
Prepares a OneWare Studio version bump (StudioVersion in Base.props, Flathub/AppStream metainfo release entry, changelog).
Related
Categories
Questions about Fpga Toolchain Yosys
What does Fpga Toolchain Yosys do?
The Yosys/nextpnr toolchain in ONE WARE Studio — which device setting key controls which stage of the compile, what the build produces, and how to read a failed synthesis, place & route or bitstream…. Fpga Toolchain Yosys is an agent skill from one-ware/OneWare. The Yosys/nextpnr toolchain in ONE WARE Studio — which device setting key controls which stage of the compile, what the build produces, and how to read a failed synthesis, place & route or bitstream run.
When should I use Fpga Toolchain Yosys?
Fpga Toolchain Yosys fits situations like: development work in your project.
How do I install Fpga Toolchain Yosys in Claude Code?
Run `npx skills add one-ware/OneWare --skill fpga-toolchain-yosys -a claude-code`. Or copy the skill folder (src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys in one-ware/OneWare) into .claude/skills/fpga-toolchain-yosys in your project. Claude Code loads it when a task matches its description.
How do I install Fpga Toolchain Yosys in Codex?
Run `npx skills add one-ware/OneWare --skill fpga-toolchain-yosys -a codex`. Or copy the skill folder (src/OneWare.OssCadSuiteIntegration/Skills/fpga-toolchain-yosys in one-ware/OneWare) into .agents/skills/fpga-toolchain-yosys in your project. Codex loads it when a task matches its description.
Can I use Fpga Toolchain Yosys 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 one-ware/OneWare --skill fpga-toolchain-yosys -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fpga-toolchain-yosys, .gemini/skills/fpga-toolchain-yosys, .github/skills/fpga-toolchain-yosys and .opencode/skills/fpga-toolchain-yosys in your project.
What does Fpga Toolchain Yosys need to run?
SKILL.md names no scripts, command-line tools or credentials: Fpga Toolchain Yosys is instructions for the agent only.
Does Fpga Toolchain Yosys 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 Fpga Toolchain Yosys 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 Fpga Toolchain Yosys use?
Fpga Toolchain Yosys 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.
How many tokens does Fpga Toolchain Yosys use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Fpga Toolchain Yosys?
Skills that share tags, products or a category with Fpga Toolchain Yosys: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fpga Toolchain Yosys?
one-ware (a GitHub organization) maintains it in one-ware/OneWare, which has 147 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: one-ware/OneWare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.