Agent skill

Fpga Project File

Apache-2.0Auto-check passedDevelopment

Install Fpga Project File

skills CLI

$ npx skills add one-ware/OneWare --skill fpga-project-file -a claude-code

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

GitHub CLI

$ gh skill install one-ware/OneWare fpga-project-file --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-project-file .claude/skills/fpga-project-file && 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/

Paste into Claude Code

Install the "fpga-project-file" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file into .claude/skills/fpga-project-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-project-file", 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

$skill-installer install https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file

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

skills CLI

$ npx skills add one-ware/OneWare --skill fpga-project-file -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install one-ware/OneWare fpga-project-file --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file .agents/skills/fpga-project-file && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "fpga-project-file" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file into .agents/skills/fpga-project-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-project-file", 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.

skills CLI

$ npx skills add one-ware/OneWare --skill fpga-project-file -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install one-ware/OneWare fpga-project-file --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file .cursor/skills/fpga-project-file && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "fpga-project-file" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file into .cursor/skills/fpga-project-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-project-file", 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

$ gemini skills install https://github.com/one-ware/OneWare.git --path src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add one-ware/OneWare --skill fpga-project-file -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install one-ware/OneWare fpga-project-file --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file .gemini/skills/fpga-project-file && rm -rf skills-src

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

Paste into Gemini CLI

Install the "fpga-project-file" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file into .gemini/skills/fpga-project-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-project-file", 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.

GitHub CLI

$ gh skill install one-ware/OneWare fpga-project-file

Installs 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).

skills CLI

$ npx skills add one-ware/OneWare --skill fpga-project-file -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file .github/skills/fpga-project-file && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "fpga-project-file" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file into .github/skills/fpga-project-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-project-file", 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.

skills CLI

$ npx skills add one-ware/OneWare --skill fpga-project-file -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install one-ware/OneWare fpga-project-file --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/one-ware/OneWare.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file .opencode/skills/fpga-project-file && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "fpga-project-file" agent skill from https://github.com/one-ware/OneWare/tree/main/src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file into .opencode/skills/fpga-project-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fpga-project-file", 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-project-file
GitHub stars: 147
Token cost: ~1.1k tokens
SKILL.md length: 513 words
Files: 1
Skills in repo: 6
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Development work in your project
SKILL.md covers .fpgaproj, device-settings/<board>.d… and <testbench>.tbconf
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fpga Project File is an agent skill from 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 hand.

Its SKILL.md is about 1.1k 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-project-file”

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 (its code samples are json and jsonc).
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 Project File loads about 1.1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 513 words of instructions outside code blocks.

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

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). 513 words, ~1,107 tokens.

Download SKILL.mdSave it as .claude/skills/fpga-project-file/SKILL.md (or your agent's skills folder).

name: fpga-project-file
description: 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 hand.

The .fpgaproj file and its companions

An FPGA project is a folder containing one <name>.fpgaproj file. That file is plain JSON and is the single source of truth for the project; the folder layout carries no meaning beyond it.

Prefer the fpga_* functions over editing these files. They validate the value against what is actually installed, keep the in-memory project model in sync, and save. Hand-editing a project file that the IDE has open loses the edit on the next save.

.fpgaproj

jsonc

{
  "include": ["*.vhd", "*.vhdl", "*.v", "*.vcd", "vhdl_ls.toml"],
  "exclude": ["build"],
  "toolchain": "yosys",
  "loader": "openFpgaLoader",
  "board": "MyBoard",
  "topEntity": "top",
  "compileExcluded": ["src/old_top.v"],
  "testBenches": ["sim/top_tb.v"],
  "preCompileSteps": ["someStepId"]
}

Key	Meaning	Function
`include`	Glob patterns or relative paths that make up the project file set. It must list at least one pattern — an empty or missing array includes no file, so the project appears empty and nothing reaches the toolchain.	`fpga_set_project_setting` (`include`)
`exclude`	Patterns removed from the file set again. Excluded files are invisible to the IDE.	`fpga_set_project_setting` (`exclude`)
`toolchain`	Id of the compile toolchain.	`fpga_set_toolchain`
`loader`	Id of the programmer used to configure the FPGA or write its FLASH.	`fpga_set_loader`
`board`	Name of the selected board.	`fpga_set_board`
`topEntity`	Name of the top level entity/module for synthesis.	`fpga_set_top_entity`
`compileExcluded`	Relative paths kept in the project but not passed to synthesis.	`fpga_set_compile_excluded`
`testBenches`	Relative paths marked as test benches.	`fpga_set_testbench`
`preCompileSteps`	Ids of the pre-compile steps that run before synthesis.	`fpga_set_project_setting` (`preCompileStep_<id>`)

Everything else in the file was registered by a plugin — typically the toolchain — and appears in fpga_list_project_settings with its key, type and allowed values. vhdlStandard is one example; which keys exist depends on the selected toolchain, so list them instead of assuming.

Notes on the format:

Paths are relative to the project folder and use / as separator, on every platform. A pattern written with \ never matches.
include/exclude decide what the IDE sees at all. compileExcluded decides what the synthesizer sees. They are not interchangeable: a file removed via exclude disappears from the project explorer, a compileExcluded file stays visible and greyed out.
fpga was the old key for board. Old files are migrated automatically; write board.
Toolchain, Loader and VHDL_Standard (capitalised) are likewise legacy spellings that are migrated to toolchain, loader and vhdlStandard.

Show full SKILL.md (166 more words)Show less

device-settings/<board>.deviceconf

A flat JSON object of string properties describing the selected board, for example a device part number or a programming mode:

json

{
  "device": "iCE40UP5K",
  "package": "sg48"
}

The defaults come from the installed hardware package; the file only needs to carry the values that differ. An entry with an empty value is dropped on save, which is how "use the board default" is expressed — fpga_set_device_setting with an empty value does exactly that.

The file is only meaningful once a board is selected, and it is per board: switching the board switches to a different .deviceconf.

<testbench>.tbconf

Simulation configuration for one test bench, stored next to it with the same base name:

json

{
  "simulator": "Verilator",
  "TopModule": "top_tb",
  "VerilatorArguments": "-Wno-fatal"
}

simulator names the simulator; every other key is an option of that simulator. Read it with fpga_get_testbench_config, write it with fpga_set_testbench_simulator and fpga_set_testbench_option.

A .tbconf is independent of the testBenches array in the project file: the array controls the test bench marker and toolbar in the IDE, the .tbconf controls how the file is simulated. In practice you want both.

Files

Just SKILL.md in src/OneWare.UniversalFpgaProjectSystem/Skills/fpga-project-file of one-ware/OneWare.

Open the folder on GitHubat commit 1f44e1d

Compare with similar skills

Fpga Project File 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 Project File compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Fpga Project File this skillone-ware/OneWare	147	—	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday
Vercel Composition Patternssupabase/supabase	111k	59 repos	~726	Automated safety check: Pass	MIT	yesterday
Finishing a Development Branchobra/superpowers	296k	5 repos	~1.9k	Automated safety check: Pass	MIT	yesterday
Typescript Advanced Typesrolling-scopes/rsschool-app	10k	25 repos	~4.2k	Automated safety check: Pass	MPL-2.0	4 days ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	2 days ago
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	10 days ago

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 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…
147 GitHub stars~1.7k 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

Questions about Fpga Project File

What does Fpga Project File do?

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 Project File is an agent skill from one-ware/OneWare.tbconf files next to it — which key means what, which ones have a dedicated fpga function, and which ones may only be edited by hand.

When should I use Fpga Project File?

Fpga Project File fits situations like: development work in your project.

How do I install Fpga Project File in Claude Code?

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

How do I install Fpga Project File in Codex?

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

Can I use Fpga Project File 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-project-file -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-project-file, .gemini/skills/fpga-project-file, .github/skills/fpga-project-file and .opencode/skills/fpga-project-file in your project.

What does Fpga Project File need to run?

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

Does Fpga Project File 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 Project File 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 Project File use?

Fpga Project File 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 Project File use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Project File?

Skills that share tags, products or a category with Fpga Project File: 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 Project File?

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.

Install Fpga Project File

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

The .fpgaproj file and its companions

.fpgaproj

device-settings/<board>.deviceconf

<testbench>.tbconf

Files

Compare with similar skills

Similar skills

More from one-ware/OneWare

Related

Questions about Fpga Project File