Architecture Design Review
bbartling/open-fdd
A skill your agent uses to evaluate architecture, design proposals, refactors, module boundaries, dependency direction, data flow, concurrency model, and maintainability tradeoffs across any codebase.
A skill your agent uses when the user needs embedded hardware architecture, MCU/SoC selection, power tree design, interface planning, sensor/actuator selection, RF/connectivity, BOM risk assessment…
Install Hardware Solution
$ npx skills add LeoKemp223/NextBoard --skill hardware-solution -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoKemp223/NextBoard hardware-solution --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/LeoKemp223/NextBoard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hardware-solution .claude/skills/hardware-solution && 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 "hardware-solution" agent skill from https://github.com/LeoKemp223/NextBoard/tree/main/skills/hardware-solution into .claude/skills/hardware-solution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-solution", 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/LeoKemp223/NextBoard/tree/main/skills/hardware-solutionType 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 LeoKemp223/NextBoard --skill hardware-solution -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoKemp223/NextBoard hardware-solution --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoKemp223/NextBoard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hardware-solution .agents/skills/hardware-solution && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hardware-solution" agent skill from https://github.com/LeoKemp223/NextBoard/tree/main/skills/hardware-solution into .agents/skills/hardware-solution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-solution", 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 LeoKemp223/NextBoard --skill hardware-solution -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoKemp223/NextBoard hardware-solution --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoKemp223/NextBoard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hardware-solution .cursor/skills/hardware-solution && 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 "hardware-solution" agent skill from https://github.com/LeoKemp223/NextBoard/tree/main/skills/hardware-solution into .cursor/skills/hardware-solution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-solution", 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/LeoKemp223/NextBoard.git --path skills/hardware-solution--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 LeoKemp223/NextBoard --skill hardware-solution -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoKemp223/NextBoard hardware-solution --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoKemp223/NextBoard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hardware-solution .gemini/skills/hardware-solution && 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 "hardware-solution" agent skill from https://github.com/LeoKemp223/NextBoard/tree/main/skills/hardware-solution into .gemini/skills/hardware-solution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-solution", 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 LeoKemp223/NextBoard hardware-solutionInstalls 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 LeoKemp223/NextBoard --skill hardware-solution -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoKemp223/NextBoard.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hardware-solution .github/skills/hardware-solution && 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 "hardware-solution" agent skill from https://github.com/LeoKemp223/NextBoard/tree/main/skills/hardware-solution into .github/skills/hardware-solution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-solution", 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 LeoKemp223/NextBoard --skill hardware-solution -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoKemp223/NextBoard hardware-solution --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoKemp223/NextBoard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hardware-solution .opencode/skills/hardware-solution && 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 "hardware-solution" agent skill from https://github.com/LeoKemp223/NextBoard/tree/main/skills/hardware-solution into .opencode/skills/hardware-solution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-solution", 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
hardware-solution- GitHub stars
- 381
- Token cost
- ~1.5k tokens
- SKILL.md length
- 329 words
- Files
- 10 (incl. scripts, references)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when the user needs embedded hardware architecture, MCU/SoC selection, power tree design, interface planning, sensor/actuator selection, RF/connectivity, BOM risk assessment…
- Works in 12 steps: 模式选择（首先执行）： 进入流程前先询问用户选择工作模式 → 读取… → 先给用户一个"需求澄清选择题"：用 2-4… → …
- The user needs embedded hardware architecture
- SKILL.md covers 工作方式, 必要输入, 流程 and 文件输出规则, plus 6 more sections
- Runs Python scripts from its folder; calls python3
What it does
Hardware Solution is an agent skill from LeoKemp223/NextBoard. Use when the user needs embedded hardware architecture, MCU/SoC selection, power tree design, interface planning, sensor/actuator selection, RF/connectivity, BOM risk assessment, PCB/layout constraints, schematic-ready proposals, validation plans, or hardware design review.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/design-workflow.md` and `references/domestic-sources.md`).
It sits in Sales & Support, covering Proposals and quotes and Design review and critique. The repository describes itself as: 面向硬件产品PCB方案设计的AI Agent，Agent会自动帮你进行需求确认，实时分析国内外各类芯片技术方案，进行器件选型，下载datasheet，输出BOM表，计算价格，输出模块原理图，最终整合成可落地技术方案。
When your agent uses it
- The user needs embedded hardware architecture
- MCU/SoC selection
- Power tree design
- Interface planning
Example prompts
- “/hardware-solution”
Requirements
- Python 3
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- 模式选择（首先执行）： 进入流程前先询问用户选择工作模式
- 读取 references/design-workflow.md，按阶段推进，不要跳过需求冻结和风险澄清。
- 先给用户一个"需求澄清选择题"：用 2-4 个具体选项确认优先级、成本/功耗/周期取向、国内/海外/混合供应链偏好。专业模式下：所有标记为"待确认"的约束项必须逐一向用户确认，不能默认跳过或自行假设。每次只问 1…
- 如果是从零设计，先输出 3 类候选架构并比较取舍：国产芯片/国产供应链优先、海外主流生态优先、混合折中方案。若某类不适用，必须说明原因；如果是评审已有方案，直接进入风险审查和改进建议。
- 关键器件和功能模块器件必须附带：采购链接（国内电商平台或分销商页面 URL，优先淘宝/立创商城/嘉立创 > 授权分销商 > 原厂官网）、datasheet 下载链接（优先 AllDatasheet > 立创商城 > 半导小芯 > 原厂官网）、封装文件下载链接（优先立创 EDA…
- Gate 3 通过后，询问用户使用的 EDA 工具，然后批量下载已选的关键 IC 和功能模块器件的 datasheet（PDF）和对应格式的封装文件，保存至 docs/hardware/datasheets/ 和 docs/hardware/footprints/…
- 需要交付正式方案时，使用 references/output-template.md 的结构输出。
- 需要评审原理图、PCB、BOM 或量产风险时，读取 references/review-checklists.md。
- 涉及关键芯片选型、供应链、认证或替代料时，读取 references/sourcing-and-risk.md；涉及国产芯片、国内元器件渠道或国产替代时，同时读取 references/domestic-sources.md。
- 每个阶段结束前，读取 references/verification-gates.md 确认门控通过。
- 评审通过后询问用户是否需要输出模块原理图。如果用户确认需要，先提供展示方式选项供用户选择（结构化连接表 / ASCII 框图 / D2 图表 / KiCad 原理图文件 .kicad_sch / 立创 EDA JSON），然后按用户选择的方式和指定的模块范围输出。KiCad…
- 所有阶段完成后，将 docs/hardware/ 目录下的全部 markdown 文件合并输出为 PDF 报告。运行 python3 /scripts/md_to_pdf.py --merge docs/hardware/…
What it can do on your machine
Read from SKILL.md and the folder at commit 69810c1. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
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
Hardware Solution loads about 1.5k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 329 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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 329 words (~1,452 tokens).
- name
- hardware-solution
Files
SKILL.md and 9 other files (scripts, references) in skills/hardware-solution of LeoKemp223/NextBoard.
- SKILL.md
- agents/openai.yaml
- references/design-workflow.md
- references/domestic-sources.md
- references/download-sources.md
- references/output-template.md
- references/review-checklists.md
- references/sourcing-and-risk.md
- references/verification-gates.md
- scripts/md_to_pdf.py
Open the folder on GitHubat commit 69810c1
Compare with similar skills
Hardware Solution 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 |
|---|---|---|---|---|---|---|
| Hardware Solution this skillLeoKemp223/NextBoard | 381 | — | ~1.5k | Automated safety check: Pass | None | |
| Architecture Design Reviewbbartling/open-fdd | 172 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Design Reviewopenclaw/openclaw-enterprise | 367 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore | 195 | 40 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Audit Onboarding Proposalhoangnb24/repository-harness | 1.2k | — | ~4k | Automated safety check: Pass | MIT | |
| No Negative EchoLB623/no-negative-echo | 897 | — | ~965 | Automated safety check: Pass | MIT |
Similar skills
Design Review
openclaw/openclaw-enterprise
Assess designs, public interfaces, state ownership, readability, and refactor proposals when the task calls for design review or structural simplification; not for unrelated routine edits.
- Official
Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
Audit Onboarding Proposal
hoangnb24/repository-harness
Use only when the user explicitly invokes $audit-onboarding-proposal.
No Negative Echo
LB623/no-negative-echo
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.
GEO Service Proposal Generator
zubair-trabzada/geo-seo-claude
Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.
Related
Categories
Questions about Hardware Solution
What does Hardware Solution do?
A skill your agent uses when the user needs embedded hardware architecture, MCU/SoC selection, power tree design, interface planning, sensor/actuator selection, RF/connectivity, BOM risk assessment…. Hardware Solution is an agent skill from LeoKemp223/NextBoard. Use when the user needs embedded hardware architecture, MCU/SoC selection, power tree design, interface planning, sensor/actuator selection, RF/connectivity, BOM risk assessment, PCB/layout constraints, schematic-ready proposals, validation plans, or hardware design review.
When should I use Hardware Solution?
Hardware Solution fits situations like: the user needs embedded hardware architecture; MCU/SoC selection; power tree design; interface planning.
How do I install Hardware Solution in Claude Code?
Run `npx skills add LeoKemp223/NextBoard --skill hardware-solution -a claude-code`. Or copy the skill folder (skills/hardware-solution in LeoKemp223/NextBoard) into .claude/skills/hardware-solution in your project. Claude Code loads it when a task matches its description.
How do I install Hardware Solution in Codex?
Run `npx skills add LeoKemp223/NextBoard --skill hardware-solution -a codex`. Or copy the skill folder (skills/hardware-solution in LeoKemp223/NextBoard) into .agents/skills/hardware-solution in your project. Codex loads it when a task matches its description.
Can I use Hardware Solution 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 LeoKemp223/NextBoard --skill hardware-solution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hardware-solution, .gemini/skills/hardware-solution, .github/skills/hardware-solution and .opencode/skills/hardware-solution in your project.
What does Hardware Solution need to run?
Going by SKILL.md and its folder, Hardware Solution needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Hardware Solution 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 Hardware Solution 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Hardware Solution use?
No licence was found for Hardware Solution or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Hardware Solution use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 8.8k tokens, read only when the agent opens those files.
What are the alternatives to Hardware Solution?
Skills that share tags, products or a category with Hardware Solution: Architecture Design Review (bbartling/open-fdd, 172 stars), Design Review (openclaw/openclaw-enterprise, 367 stars), Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars) and Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hardware Solution?
LeoKemp223 (a GitHub user) maintains it in LeoKemp223/NextBoard, which has 381 GitHub stars. The repository was last updated on May 5, 2026.
Source: LeoKemp223/NextBoard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.