القائمة
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.
التثبيت باستخدام 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.
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.
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-citation |
| description | 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. |
Validate any quantitative or device-physics claim before it lands in code, docs, or commit messages. See tools/fecim-skills/_shared/fecim-context.md (Honesty-audit policy) for the rule list.
Parse the claim. Extract: subject (e.g., HZO coercive field), value (e.g., 1.0 MV/cm), context (educational vs validated).
Match to canonical sources (tools/fecim-skills/_shared/fecim-context.md table) and the current source/audit files (docs/4-research/honesty-audit.md, references/, and citations/ if present). If the claim corresponds to a published source, format as:
<claim text> (Materlik 2015)
Check honesty-audit removed/unverified list:
For uncited claims, suggest one of:
Output:
Claim: <as written>
Status: verified | educational-default | removed-unverified | needs-source
Suggested wording: <if change needed>
Citation: <short form, DOI or source path if applicable>
Evidence boundary: <what the source verifies and what it does not verify>
removed-unverified; suggested wording reframes as the simulation pipeline's accuracy with explicit educational label, OR points to HZO FTJ 2025's 98.24% with "not a FeCIM device claim" caveat.Citation review is observation — TDD: N/A. Code/doc edits triggered by review follow the project's TDD hard-rule per tools/fecim-skills/_shared/tdd-evidence-template.md.