القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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-fyne-thread-check |
| description | 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. |
Find places where a goroutine touches a Fyne widget without fyne.Do(...) wrapping. See tools/fecim-skills/_shared/fecim-context.md (UI thread-safety rule).
Run the automated guardrail first. It scans default Fyne GUI scopes and exits non-zero on direct mutation-like widget calls inside goroutine literals without fyne.Do/fyne.DoAndWait:
make fyne-thread-check
# or scoped:
go run ./tools/fyne-thread-check module6-eda/pkg/gui/tabs/builder_validation_tab.go
Define audit scope. Default: module*/pkg/gui/, cmd/fecim-lattice-tools/. Narrow to changed files for PR review:
git diff --name-only main...HEAD | grep '\.go$' | grep -E 'pkg/gui|cmd/fecim'
Use rg if available; on this host it may be missing, so grep is the default-safe fallback.
Find goroutine launches:
rg -nU 'go func\(' <scope> 2>/dev/null || grep -RIn 'go func(' <scope>
For each match, examine the body for direct mutation of:
*widget.* (e.g., Label.SetText, Button.SetText, Entry.SetText, ProgressBar.SetValue)*canvas.* (e.g., canvas.Refresh, *canvas.Image.Image = ...)*container.* (Add, Remove, Refresh)fyne.CanvasObjectVerify the call is wrapped:
fyne.Do(func() { label.SetText("done") })label.SetText(...) inside go func()Output a violation list:
<file>:<line>: <symbol>.<method>(...) inside goroutine — needs fyne.Do
Suggested:
fyne.Do(func() { <symbol>.<method>(...) })
Cross-reference docs/3-develop/gui/FYNE_NOTES.md#threading-critical for nuanced cases (animation tickers, blocking dialogs).
go func() { mylabel.SetText("done") }() in module1-hysteresis/pkg/gui/simulation.go.
Expected: skill flags simulation.go:<line>: mylabel.SetText and suggests the wrap.Audit is observation — TDD: N/A. Any code change made to fix a violation triggers the project's TDD hard-rule.