New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fpga Studio Control

by one-ware in 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…

Apache-2.0Auto-check passedDevelopment

Install Fpga Studio Control

skills CLI
$ npx skills add one-ware/OneWare --skill fpga-studio-control -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install one-ware/OneWare fpga-studio-control --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-studio-control .claude/skills/fpga-studio-control && rm -rf skills-src

Use ~/.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/

Facts

Skill name
fpga-studio-control
GitHub stars
147
Token cost
~1.7k tokens
SKILL.md length
838 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Development work in your project
  • SKILL.md covers Orientation, Creating a project, Configuring a project and Compiling, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fpga Studio Control is an agent skill from 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 test benches, and in what order.

Its SKILL.md is about 1.7k 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-studio-control”

What it can do on your machine

Read from SKILL.md and the folder at commit 1f44e1d. 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 Studio Control loads about 1.7k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 838 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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 1f44e1d, republished under its Apache-2.0 licence (© one-ware). 838 words, ~1,703 tokens.

Download SKILL.mdSave it as .claude/skills/fpga-studio-control/SKILL.md (or your agent's skills folder).
name
fpga-studio-control
description
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 test benches, and in what order.

Controlling the FPGA project system

Every fpga_* function acts on the active FPGA project. There is exactly one active project at a time, and it is not necessarily the project whose file the user has open in the editor.

Orientation

QuestionFunction
Is an FPGA project active, and how is it configured?fpga_get_project_overview
Which projects are loaded?fpga_list_projects
What is installed (toolchains, loaders, simulators, boards, templates, pre-compile steps)?fpga_list_toolchains
Which files belong to the project, and how are they flagged?fpga_list_files

Start every task with fpga_get_project_overview. If it reports that no project is active, either fpga_set_active_project an existing one, fpga_open_project a .fpgaproj from disk, or create a new one.

fpga_list_toolchains is the only authoritative source of ids. A toolchain, loader, simulator or board that it does not list is not installed, and no other function will accept it. Never guess an id from the user's wording — map "iCE40 board" or "Yosys" onto a listed entry, and if nothing matches, say what is available.

Creating a project

fpga_list_toolchains            -> pick a toolchain id and a loader id
fpga_create_project             -> name, optional directory, toolchain, loader, template
fpga_set_board                  -> a board name from fpga_list_toolchains

fpga_create_project creates a folder, writes the .fpgaproj, loads the project and makes it active. It asks the user to confirm because it writes to disk. It does not select a board — a board is required before compiling, so always follow up with fpga_set_board.

The optional template fills the project with starter sources. If the user wants to write the HDL themselves, omit it.

Configuring a project

TaskFunction
Change the toolchainfpga_set_toolchain
Change the loader (programmer)fpga_set_loader
Change the boardfpga_set_board
Set the top level entity/modulefpga_set_top_entity
Change a registered project settingfpga_set_project_setting
Change a board device settingfpga_set_device_setting
Exclude a file from compilationfpga_set_compile_excluded
Mark a file as a test benchfpga_set_testbench

All of these save the project file, so no separate save is needed. fpga_save_project exists only for the case where the project file was edited by other means.

Top entity

fpga_list_top_entities parses the HDL sources and returns every entity/module that could be the top level, together with the file it lives in. Test benches and files excluded from compilation are skipped, which is exactly what you want — a test bench is never the top entity of a synthesis run.

Only set a top entity that the list contains. If the list is empty, the language plugin for the sources is probably not installed; say so instead of setting a name that will fail at synthesis.

Project settings vs. device settings

Two different stores, two different functions:

  • Project settings (fpga_list_project_settings / fpga_set_project_setting) are what the project settings dialog shows. They live in the .fpgaproj file and are registered by plugins, so which ones exist depends on the selected toolchain. Keys of the form preCompileStep_<id> are booleans that enable or disable a pre-compile step.
  • Device settings (fpga_list_device_settings / fpga_set_device_setting) describe the selected board and live in device-settings/<board>.deviceconf. They only exist once a board is selected. Setting one to an empty value removes it, so the board default applies again.
Show full SKILL.md (354 more words)Show less
Compile exclusions

A file that is excluded from compilation stays in the project and stays visible, but is not passed to synthesis. Use it for alternative implementations of the same entity, for vendor sources that only the simulator needs, and for anything the user wants to keep but not build.

Excluding a file is the correct answer to "the synthesizer complains about a file I don't need" — deleting it is not.

Compiling

fpga_get_project_overview       -> toolchain, board and top entity present?
fpga_compile

fpga_compile saves the open files, runs the enabled pre-compile steps, and then the toolchain stages: synthesis, place & route, bitstream generation. The build stops at the first stage that fails, and a later stage never runs on a stale result from a previous build. That means the first error in the Output panel is the one to fix — later messages, if any, are consequences.

The function itself returns only success or failure; the tool output goes to the Output panel. When it fails, ask the user for the relevant Output lines (or read the source that the error names) rather than re-running the same build.

Compiling requires a confirmation because it runs external tools.

Simulating a test bench

fpga_set_testbench              -> path, true
fpga_set_testbench_simulator    -> path, a simulator name from fpga_list_toolchains
fpga_set_testbench_option       -> path, TopModule, <module name>      (usually needed)
fpga_run_simulation             -> path

The per-test-bench configuration lives in a .tbconf file next to the test bench, not in the project file — fpga_get_testbench_config reads it back.

Common options:

KeySimulatorMeaning
TopModuleallName of the module the simulator elaborates. Defaults to the file name.
VerilatorArgumentsVerilatorExtra compile-time arguments.
VerilatorRuntimeArgumentsVerilatorArguments passed to the built simulation binary.
IcarusVerilogArgumentsIcarus VerilogExtra arguments.
WaveOutputFormatIcarus VerilogVCD or FST.

Verilator treats warnings as fatal by default, so a design that only produces warnings still fails the run. -Wno-fatal in VerilatorArguments downgrades them; -Wno-<CODE> silences one specific warning. Prefer fixing the source — a missing `timescale causing TIMESCALEMOD is a real inconsistency, not noise.

Rules

  • Read the error a function returns. It names the concrete problem and usually the function to call next; retrying the identical call will fail identically.
  • Never invent ids, board names or entity names.
  • Ask before doing something the user did not ask for, especially before changing a board or a toolchain — that invalidates pin assignments.

© 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.UniversalFpgaProjectSystem/Skills/fpga-studio-control of one-ware/OneWare.

Open the folder on GitHubat commit 1f44e1d

Compare with similar skills

Fpga Studio Control 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.

Fpga Studio Control compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fpga Studio Control this skillone-ware/OneWare147—~1.7kAutomated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • 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.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • 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.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • 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.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • 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.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • 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.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from one-ware/OneWare

  • Oneware Module

    one-ware/OneWare

    Creates or wires up a OneWare feature module (built-in src/OneWare.

    147 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • 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…

    147 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Oneware Styling

    one-ware/OneWare

    Styles OneWare Avalonia UI with the shared design system (tokens, classes, icons, control themes).

    147 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Fpga Toolchain Yosys

    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…

    147 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Oneware Release

    one-ware/OneWare

    Prepares a OneWare Studio version bump (StudioVersion in Base.props, Flathub/AppStream metainfo release entry, changelog).

    147 GitHub stars~397 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Fpga Studio Control

What does Fpga Studio Control do?

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…. Fpga Studio Control is an agent skill from 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 test benches, and in what order.

When should I use Fpga Studio Control?

Fpga Studio Control fits situations like: development work in your project.

How do I install Fpga Studio Control in Claude Code?

Run `npx skills add one-ware/OneWare --skill fpga-studio-control -a claude-code`. Or copy the skill folder (src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-studio-control in one-ware/OneWare) into .claude/skills/fpga-studio-control in your project. Claude Code loads it when a task matches its description.

How do I install Fpga Studio Control in Codex?

Run `npx skills add one-ware/OneWare --skill fpga-studio-control -a codex`. Or copy the skill folder (src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-studio-control in one-ware/OneWare) into .agents/skills/fpga-studio-control in your project. Codex loads it when a task matches its description.

Can I use Fpga Studio Control 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-studio-control -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-studio-control, .gemini/skills/fpga-studio-control, .github/skills/fpga-studio-control and .opencode/skills/fpga-studio-control in your project.

What does Fpga Studio Control need to run?

SKILL.md names no scripts, command-line tools or credentials: Fpga Studio Control is instructions for the agent only.

Does Fpga Studio Control 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 Studio Control 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 Studio Control use?

Fpga Studio Control 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 Studio Control use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Studio Control?

Skills that share tags, products or a category with Fpga Studio Control: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k 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 Studio Control?

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 7, 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.