科研 Skill
硬件项目实验记录管理
lab-notebook
Maintains a hardware project’s knowledge base: task cycle, facts with evidence, experiment verdicts, and per-stage reports. Use at the start and end of every project stage.
SKILL.md
Lab notebook
Hardware projects regress when nobody records what was tried. A fix undoes an earlier fix. A measurement gets repeated. A failed idea comes back a week later. An agent's findings are lost when the conversation ends. This skill makes every stage leave the project better documented than it found it.
Talk to the user in their language. Write the notebook in English, unless the user chose another language for project files.
Inputs and outputs
- Inputs:
hw/state.json,hw/knowledge/,hw/decisions.md. - Outputs: the files below. This skill owns them.
hw/knowledge/FACTS.md F-001… measured or verified facts
hw/knowledge/EXPERIMENTS.md E-001… what was tried, with a verdict
hw/knowledge/LESSONS.md L-001… rules learned, including user corrections
hw/retros/YYYY-MM-DD-<stage>.md one report per stage or large task
hw/agents/YYYY-MM-DD-<task>.md the report of each subagent, saved on arrival
Copy the headers from templates/ the first time.
1. Start of a stage
- Read
hw/state.json, thenhw/knowledge/LESSONS.md. Each lesson that applies to this stage is a rule. - Search
FACTS.mdandEXPERIMENTS.mdfor the subject (grep -n -i <word> hw/knowledge/*.md).- A fact with evidence is not measured again unless the design changed. Cite its ID.
- An experiment with the verdict
did not workis not repeated without a new hypothesis. Write the hypothesis down first.
- If other agents work in the same project, find their files first (
git status, file modification times). Do not edit, move or commit their files.
2. During the stage
-
Record facts at the moment you find them. One entry has:
- an ID;
- the date;
- the statement with its value and unit;
- an evidence tag (
CONVENTIONS.md§6); - the command or source that reproduces it.
A number lives only in its fact. Other files cite the ID.
-
Record each experiment with a verdict:
worked,did not workorinconclusive. Add the reason and what would change the verdict. Record failures too, because they keep the next session from repeating them. -
Take a new ID when you write the entry, not from memory. Run
scripts/notebook_check.py --next Fto get the next free ID. With parallel agents, give each agent its own range (F-2xx, F-3xx) and name the range in its brief. -
Write each user correction as a lesson when it happens. Record the user's words, what was wrong and the rule that prevents it. Examples of real corrections:
- "the shape makes no sense, it has to be straight" → L: pouch cells have straight edges;
- "something is poking through" → L: validate before any render.
-
Regression rule. If a change brings back a failure that an earlier change fixed:
- stop;
- write an experiment entry for both changes;
- find the shared cause, usually the order of operations or two owners of one value;
- change the order or the ownership.
Do not try a third variant of the same fix.
-
Parallel agents.
- Before you split the work, freeze a common base and run its checks.
- Agree the file formats.
- Give each agent its own files.
- Save each agent's report to
hw/agents/the moment it arrives. - Merge one file at a time.
3. End of a stage (checklist)
- Verify. Run the checks of the stage's skill, for example
bom_check.py, the assembly validator or DRC. Write what was not verified. - Knowledge. Add new F-, E- and L- entries. When a fact changes, write a new entry, and mark the old
one
SUPERSEDED on <date> by F-xxx: <what changed>. Do not delete it. - Decisions. Add decisions to
hw/decisions.md. - State. Update
hw/state.json: stage status, gate evidence, open questions. - Report. Write
hw/retros/YYYY-MM-DD-<stage>.mdfromtemplates/retro.md:- the request;
- what was done and verified;
- what was not verified;
- the user's interventions;
- mistakes and their causes;
- the lessons added;
- what is next.
- Check. Run
scripts/notebook_check.py hw/. It must report no duplicate IDs, no fact without evidence, and no experiment without a verdict. - Commit, only if the user wants commits. Never add attribution lines that the user did not ask for.
Writing rules for project files
These rules apply to every file in hw/. They are adapted from the concise skill (MIT) and from
ASD-STE100 controlled language. The full list is in references/writing-rules.md.
- Use only these normative words: must, must not, should (a deviation needs a written reason), can. Do not use "shall", "may", "ideally" or "try to".
- Write each fact once, in its owner file. Elsewhere, refer to it by ID (
F-012,REQ-004,D-007). - Replace vague words with values: "small" → "≤ 30 × 30 × 9 mm", "low power" → "≤ 1.5 mA average", "about 2 weeks" → "10–15 working days [estimate]".
- Use digits and units with a space:
3.3 V,68 mAh,0.35 mm. Repeat the unit in ranges:2 mA to 4 mA. - Keep sentences short: 20 words or fewer for instructions, 25 or fewer for descriptions. Use active voice.
- Use one term for one thing. Put part numbers, file names, nets and commands in code format.
- Do not announce, summarize or restate. Each sentence adds a fact, an instruction or a decision.
Gate
The stage closes when notebook_check.py passes, the retro exists and hw/state.json is updated.
Taste and pitfalls
- An agent report that stays only in the conversation is lost. Save it to a file on arrival.
- Two agents that take "the next ID" at the start of their tasks collide. Take the ID when you write. This includes open-question IDs in
hw/state.json: give each parallel agent its own prefix or range (Q-RF-,Q-PW-). In one real run, two research agents both created Q-07 to Q-09. - A number copied into three documents goes stale in two of them. Keep it in one fact and cite the ID.
- A failed experiment that is not written down gets tried again. Record failures with the same care as successes.
- A lesson written only in the chat is forgotten in the next session. Write it in
LESSONS.mdat the moment of the correction.
示例提示词
帮我把这个阶段的实验结论和经验教训整理进项目笔记里。
所属插件
安装该插件会一并获得同领域的 63 个 Skill / MCP。
同插件的其他科研 Skill
- ANDES电力系统动态仿真Runs ANDES power-system dynamic studies via PowerMCP: power flow, eigenvalue analysis, and time-domain simulation. Use for damping, stability, or oscillation-mode questions.
- 电池选型与电源预算Builds an evidence-tagged power budget and sizes a manufacturable battery with pouch outline, seals, and derating. Use when sizing runtime, mAh, charging, or supply rails.
- FPGA比特流生成与烧录Generates a Xilinx FPGA bitstream and programs it over JTAG, or burns an MCS image into flash for power-on boot. Use when flashing a board or diagnosing boot failures.
- 硬件项目发布包组装Assembles a hardware release package (fab files, BOM/CPL, carts, assembly guide, hashed manifest) and runs a ready-to-build gate. Use before ordering prototypes.
- 时钟域交叉风险审查Audits clock-domain-crossing risk on an FPGA design and applies the smallest safe synchronizer or constraint fix. Use to resolve CDC violations before sign-off.
- 硬件产品认证合规规划Plans certifications a hardware product needs per target market (FCC, CE/RED, UKCA, battery/radio rules), with cost and lead-time estimates. Use before PCB or enclosure tooling.
- Vivado XDC时序约束编写Authors a Vivado XDC timing constraint set from scratch: clocks, I/O delays, and timing exceptions. Use first, before timing closure, on a design with no or incomplete constraints.
- N-1/N-2应急违规处置Playbook for N-1/N-2 contingency violations: ranks contingencies and proposes preventive and corrective actions. Use after a study shows voltage or thermal problems.
- 潮流计算不收敛诊断Playbook for power-flow convergence failures in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Use when a case diverges or fails to solve.
- 硬件成本核算与采购Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.
- RTL仿真覆盖率收敛Measures RTL simulation code coverage and iteratively closes it toward a target by adding testbench stimulus. Use for a sign-off-grade coverage report.
- 配电网DER接纳能力治理Playbook for distribution DER hosting-capacity limits: voltage rise, reverse flow, and thermal limits from PV and storage. Use to estimate how much DER a feeder can host.
- 电子电路设计与审查Designs, audits, or corrects an electronic circuit from a brief, schematic, or netlist, checking power domains, reset sequencing, and ratings. Use for circuit review.
- 硬件可制造性红队审查Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design.
- 电力系统动态稳定处置Playbook for dynamic stability problems: poor damping, angle instability, or sustained oscillations from eigenvalue or time-domain studies. Use after an unstable study result.
- Egret电力市场调度优化Runs Egret market/operations optimization (DC-OPF, AC-OPF, unit commitment) via PowerMCP. Use for cheapest dispatch, unit commitment, or congestion checks.
- 电子元器件选型核查Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM.
- EMC电磁兼容预测试Plans grounding, shielding, and filtering for EMC/EMI, and runs an emissions pre-scan with a root-cause fix sequence. Use before a lab test or after a failed EMI scan.
- 产品外壳参数化建模Designs a hardware enclosure as parametric CAD with STEP/STL/GLB output, a DFM check, and Blender assembly validation. Use when designing a case or checking fit.
- 电网频率响应问题处置Playbook for frequency problems: low inertia, high RoCoF, weak primary response, or UFLS risk after loss of the largest unit. Use when a study flags frequency issues.
- FPGA RTL到比特流全流程Drives a Xilinx FPGA design end to end through RTL, simulation, synthesis, implementation, and bitstream, gated at every stage. Use to run the complete build flow in one pass.
- 硬件产品全流程总协调Leads a physical electronic product from idea to a doable design, coordinating specs, parts, battery, PCB, enclosure, render, and cost sub-skills. Use starting a hardware product.
- 硬件原理图与BOM审查Reviews hardware projects: checks schematics against datasheets, pin connections, and firmware-to-hardware alignment across KiCad/Altium files. Use for a design alignment check.
- FPGA ILA在线逻辑调试Inserts an Integrated Logic Analyzer, programs the board, arms a trigger, and reads captured waveforms on real FPGA hardware. Use when sim passes but the board fails.
常见问题
硬件项目实验记录管理能做什么?
Maintains a hardware project’s knowledge base: task cycle, facts with evidence, experiment verdicts, and per-stage reports. Use at the start and end of every project stage。
如何安装硬件项目实验记录管理?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件项目实验记录管理」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
硬件项目实验记录管理需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
硬件项目实验记录管理经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。