菜单
Runs the FeCIM test matrix (full, race, module-scoped, coverage, golden regen) and interprets physics regression failures using the 5 known bug patterns. Use when running tests, debugging test failures, or regenerating physics golden files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audits Go code for goroutine-to-widget access without fyne.Do(...) wrapping, the project's most common GUI freeze cause. Use when reviewing a PR that adds goroutines, async I/O, or simulation tickers in any pkg/gui/ or shell package.
Runs build flows for the canonical Fyne shell and module commands on this Go 1.25 monorepo. Use when building, packaging, or debugging build failures in cmd/fecim-lattice-tools or module GUI commands.
Relentlessly interviews the user about a proposed FeCIM physics, simulation, or GUI change before any code is written — covering source citation, educational-vs-validated framing, TDD-RED test, thread-safety, and honesty-audit alignment. Use when starting a non-trivial change to physics, ISPP, crossbar, or GUI logic.
Verifies and formats FeCIM physics/measurement claims against the project's published-source list and docs/4-research/honesty-audit.md. Use when adding a numeric claim, accuracy figure, or device-parameter assertion to code, docs, PR descriptions, or commit messages.
Enforces docs/4-research/honesty-audit.md policy by scanning PR diffs, READMEs, and presentation material for removed/unverified claims (87% MNIST, 30-states-as-fact, energy multipliers vs NAND/GPUs). Use before committing docs, PRs, or release notes that include accuracy or efficiency numbers.
Surveys FeCIM domain knowledge by searching references/, citations/, docs/4-research/, and the local Cognee KG, then synthesizes a cited research note. Use when investigating a physics topic, evaluating a paper, or grounding a design decision in literature.
| name | fecim-labtester |
| description | Runs the FeCIM test matrix (full, race, module-scoped, coverage, golden regen) and interprets physics regression failures using the 5 known bug patterns. Use when running tests, debugging test failures, or regenerating physics golden files. |
Pick the right test invocation, run it, and triage failures against the 5 known bug patterns. See tools/fecim-skills/_shared/fecim-context.md for the test matrix and bug list.
Pick scope by the change being verified:
go test ./...go test -json ./... followed by a pass/fail/skip/package summarygo test -race ./...go test ./module1-hysteresis/... (or make test-hys, test-xbar, test-mnist, test-circuits, test-shared)make test-Fyne-uigo test -cover ./...git diff --checkFor physics-regression failures, classify against the 5 known patterns:
[VMin, VMax]Golden regeneration is allowed only when divergence is intentional and the user has confirmed:
FECIM_UPDATE_PHYSICS_GOLDEN=1 go test ./...
Diff validation/testdata/physics_regression/ before committing — unintended changes are bugs.
Output the TDD evidence block per tools/fecim-skills/_shared/tdd-evidence-template.md:
RED: go test ./module1-hysteresis/... -run TestX
FAIL TestX (Preisach Everett zero-clamp pattern)
GREEN: go test ./module1-hysteresis/... -run TestX
ok
VERIFY: go test ./... && go test -race ./... && git diff --check
This skill is the TDD verifier itself — every change made under it must produce the RED/GREEN block above before commit.