Agent skill

Domain Layer

Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters.

MITAuto-check passed

Install Domain Layer

skills CLI

$ npx skills add atopile/atopile --skill domain-layer -a claude-code

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

GitHub CLI

$ gh skill install atopile/atopile domain-layer --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/atopile/atopile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/domain-layer .claude/skills/domain-layer && 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 "domain-layer" agent skill from https://github.com/atopile/atopile/tree/main/.claude/skills/domain-layer into .claude/skills/domain-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-layer", 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/atopile/atopile/tree/main/.claude/skills/domain-layer

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 atopile/atopile --skill domain-layer -a codex

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

GitHub CLI

$ gh skill install atopile/atopile domain-layer --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/atopile/atopile.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/domain-layer .agents/skills/domain-layer && 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 "domain-layer" agent skill from https://github.com/atopile/atopile/tree/main/.claude/skills/domain-layer into .agents/skills/domain-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-layer", 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 atopile/atopile --skill domain-layer -a cursor

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

GitHub CLI

$ gh skill install atopile/atopile domain-layer --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/atopile/atopile.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/domain-layer .cursor/skills/domain-layer && 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 "domain-layer" agent skill from https://github.com/atopile/atopile/tree/main/.claude/skills/domain-layer into .cursor/skills/domain-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-layer", 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/atopile/atopile.git --path .claude/skills/domain-layer

--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 atopile/atopile --skill domain-layer -a gemini-cli

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

GitHub CLI

$ gh skill install atopile/atopile domain-layer --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/atopile/atopile.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/domain-layer .gemini/skills/domain-layer && 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 "domain-layer" agent skill from https://github.com/atopile/atopile/tree/main/.claude/skills/domain-layer into .gemini/skills/domain-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-layer", 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 atopile/atopile domain-layer

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 atopile/atopile --skill domain-layer -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/atopile/atopile.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/domain-layer .github/skills/domain-layer && 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 "domain-layer" agent skill from https://github.com/atopile/atopile/tree/main/.claude/skills/domain-layer into .github/skills/domain-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-layer", 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 atopile/atopile --skill domain-layer -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 atopile/atopile domain-layer --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/atopile/atopile.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/domain-layer .opencode/skills/domain-layer && 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 "domain-layer" agent skill from https://github.com/atopile/atopile/tree/main/.claude/skills/domain-layer into .opencode/skills/domain-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-layer", 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: domain-layer
GitHub stars: 4k
Token cost: ~791 tokens
SKILL.md length: 332 words
Files: 1
Skills in repo: 19
Repo updated: Jun 13, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters.

Works in 2 steps: Adding a Config Option: If a new build… → New Exporters: Create a new module in…
Modifying build steps
SKILL.md covers Quick Start, Relevant Files, Dependants (Call Sites) and How to Work With / Develop /…, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Domain Layer is an agent skill from atopile/atopile. Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters. Use when implementing or modifying build steps, exporters, PCB generation, or BOM/netlist output.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Design circuit boards with code! ✨ Get software-like design reuse 🚀, validation, version control and collaboration in hardware; starting with electronics ⚡️. The licence is MIT.

When your agent uses it

Modifying build steps
BOM/netlist output

Example prompts

“Use the domain-layer skill to instruction for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters”
“/domain-layer”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Adding a Config Option: If a new build step needs configuration, add it to atopile.config (not covered here, but relevant).
New Exporters: Create a new module in src/faebryk/exporters/ and register a wrapper function in build_steps.py using @muster.register.

What it can do on your machine

Read from SKILL.md and the folder at commit 619eda7. 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 bash).
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

Domain Layer loads about 791 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 332 words of instructions outside code blocks.

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

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 atopile/atopile at commit 619eda7, republished under its MIT licence (© atopile). 332 words, ~791 tokens.

Download SKILL.mdSave it as .claude/skills/domain-layer/SKILL.md (or your agent's skills folder).

name: domain-layer
description: Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters. Use when implementing or modifying build steps, exporters, PCB generation, or BOM/netlist output.

Domain Layer Module

The domain layer (primarily src/atopile/build_steps.py and src/faebryk/exporters/) encompasses the logic and processes specific to electronic hardware engineering. This includes the build pipeline that transforms a compiled graph into manufacturing artifacts (Gerbers, BOMs, Pick & Place).

Quick Start

Run the standard build pipeline from a project directory (where ato.yaml lives):

bash

ato build

Relevant Files

Build Orchestration: src/atopile/build_steps.py
- Defines the Muster class (a DAG-based task runner).
- Registers standard build targets: generate_bom, generate_manufacturing_data, update_pcb, etc.
Build entry / app init: src/atopile/build.py (constructs app graph from .ato or .py, runs unit inference)
Exporters: src/faebryk/exporters/
- pcb/: KiCad PCB generation and layout sync (layout_sync.py).
- bom/: Bill of Materials generation (jlcpcb.py, etc.).
- netlist/: Netlist formatting.
- documentation/: Datasheets, diagrams.
Layout sync inputs:
- src/atopile/layout.py (generates .layouts.json module→layout mapping)
- src/atopile/kicad_plugin/README.md (plugin workflow overview)

Dependants (Call Sites)

CLI (src/atopile/cli/build.py): The ato build command directly invokes build_steps.muster to execute the pipeline.
IDE/Extension: May invoke specific build steps for previews (e.g., generate_3d_render).

How to Work With / Develop / Test

Core Concepts

Muster: The task runner. Targets declare dependencies (e.g. generate_bom depends on build_design).
Layout Sync: The process of preserving manual PCB layout changes while updating the netlist/components from the code (update_pcb).
Artifacts: Files produced by the build process, stored in the build directory.

Development Workflow

Adding a Config Option: If a new build step needs configuration, add it to atopile.config (not covered here, but relevant).
New Exporters: Create a new module in src/faebryk/exporters/ and register a wrapper function in build_steps.py using @muster.register.

Testing

Integration Tests: Since this layer orchestrates the whole flow, it is best tested via end-to-end tests or integration tests in test/end_to_end/ or test/integration/.
Manual Verification: Run ato build on a sample project and inspect the generated artifacts (Gerbers, BOM csv).
Muster unit tests: ato dev test --llm test/test_muster.py -q

Best Practices

Idempotency: Build steps should generally be idempotent.
Virtual Targets: Use virtual=True for targets that just group other targets (e.g. all or default).
Layout Preservation: Be extremely careful when modifying update_pcb or layout_sync logic to avoid dataloss of user's manual PCB routing.

Files

Just SKILL.md in .claude/skills/domain-layer of atopile/atopile.

Open the folder on GitHubat commit 619eda7

Compare with similar skills

Domain Layer 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.

Domain Layer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Domain Layer this skillatopile/atopile	4k	—	~791	Automated safety check: Pass	MIT	3 mo ago
Desktop ElectronOpenHands/OpenHands	90k	—	~302	Automated safety check: Pass	MIT	today
Electron Developmentdavila7/claude-code-templates	32k	3 repos	~7k	Automated safety check: Pass	MIT	today
Electron App Automationvercel-labs/agent-browser	44k	5 repos	~1.7k	Automated safety check: Pass	Apache-2.0	today
Codebase Domain Flow ExtractorEgonex-AI/Understand-Anything	86k	1 repos	~2.4k	Automated safety check: Pass	MIT	2 days ago
Electron Multi-Process ArchitectureiOfficeAI/AionUi	33k	1 repos	~1.8k	Automated safety check: Pass	Apache-2.0	29 days ago

Similar skills

Desktop Electron
OpenHands/OpenHands
This skill should be used when the user asks to "change the desktop app", "package Electron", "build a universal macOS app", "bundle Node or uv", "fix Electron startup", or changes electron/…
90k GitHub stars~302 tokensUpdated today
Auto-check passed
Electron Development
davila7/claude-code-templates
Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.
32k GitHub starsUsed in 3 repos~7k tokens
MobileAuto-check passed
Electron App Automation
vercel-labs/agent-browser
Official
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
44k GitHub starsUsed in 5 repos~1.7k tokens
Productivity & AutomationAuto-check passed
Codebase Domain Flow Extractor
Egonex-AI/Understand-Anything
Extracts business domains, flows and process steps from a codebase and produces an interactive horizontal flow graph, reusing an existing knowledge graph when one exists.
86k GitHub starsUsed in 1 repo~2.4k tokens
Knowledge ManagementAuto-check passed
Electron Multi-Process Architecture
iOfficeAI/AionUi
Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.
33k GitHub starsUsed in 1 repo~1.8k tokens
DevelopmentAuto-check passed
Nutrient Document Processing
affaan-m/ECC
Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API.
275k GitHub starsUsed in 4 repos~1.5k tokens
Documents & OfficeAuto-check passed

Questions about Domain Layer

What does Domain Layer do?

Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters. Domain Layer is an agent skill from atopile/atopile. Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters.

When should I use Domain Layer?

Domain Layer fits situations like: modifying build steps; BOM/netlist output.

How do I install Domain Layer in Claude Code?

Run `npx skills add atopile/atopile --skill domain-layer -a claude-code`. Or copy the skill folder (.claude/skills/domain-layer in atopile/atopile) into .claude/skills/domain-layer in your project. Claude Code loads it when a task matches its description.

How do I install Domain Layer in Codex?

Run `npx skills add atopile/atopile --skill domain-layer -a codex`. Or copy the skill folder (.claude/skills/domain-layer in atopile/atopile) into .agents/skills/domain-layer in your project. Codex loads it when a task matches its description.

Can I use Domain Layer 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 atopile/atopile --skill domain-layer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/domain-layer, .gemini/skills/domain-layer, .github/skills/domain-layer and .opencode/skills/domain-layer in your project.

What does Domain Layer need to run?

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

Does Domain Layer 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 Domain Layer 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 Domain Layer use?

Domain Layer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Domain Layer use?

About 791 tokens (SKILL.md is roughly 3.2k 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 Domain Layer?

Skills that share tags, products or a category with Domain Layer: Desktop Electron (OpenHands/OpenHands, 90k stars), Electron Development (davila7/claude-code-templates, 32k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars) and Codebase Domain Flow Extractor (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Domain Layer?

atopile (a GitHub organization) maintains it in atopile/atopile, which has 3,976 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on June 13, 2026.

Source: atopile/atopile on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Domain Layer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Domain Layer Module

Quick Start

Relevant Files

Dependants (Call Sites)

How to Work With / Develop / Test

Core Concepts

Development Workflow

Testing

Best Practices

Files

Compare with similar skills

Similar skills

More from atopile/atopile

Questions about Domain Layer