菜单
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.
用 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.
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.
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.
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-builder |
| description | 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. |
See tools/fecim-skills/_shared/fecim-context.md (Build target matrix) for the canonical CGO/entry-point mapping.
Identify the target — ask the user if unclear:
cmd/fecim-lattice-toolsSet the build environment:
export CGO_ENABLED=0.Run the build:
CGO_ENABLED=0 go build -o fecim-lattice-tools ./cmd/fecim-lattice-tools./launch.shgo build ./...go, git, and rg/fallback using _shared/fecim-context.md.On failure, triage:
| Symptom | Cause | Fix |
|---|---|---|
fatal error: GL/gl.h: No such file | Missing OpenGL headers | Report blocker with command output; operator/admin installs packages. |
cannot find -lvulkan | Vulkan loader missing | Report blocker for legacy/Vulkan path; optional dep may be omitted when not required. |
gcc not found | CGO toolchain missing | Report blocker with command -v gcc evidence; operator/admin installs packages. |
package github.com/Fyne: cannot find module | Fyne import in non-shell pkg | UI-boundary violation; move logic to shared/viewmodel/ per AGENTS.md |
Verify:
CGO_ENABLED=0 was respected (go env CGO_ENABLED should print 0 in the same shell).Build invocations are observation, not behavior change — TDD: N/A. Any code change discovered during triage triggers the project's TDD hard-rule. See tools/fecim-skills/_shared/tdd-evidence-template.md.