KOKO\Mimi
46 lines
2.6 KiB
Markdown
46 lines
2.6 KiB
Markdown
---
|
|
name: fem-theory-query
|
|
description: Use when the user requests a finite-element structural-analysis answer grounded in a configured FEM wiki vault, or asks to identify a gap in that vault.
|
|
---
|
|
|
|
# FEM Theory Query
|
|
|
|
Answer from configured vault evidence and clearly separate vault knowledge from gaps. Do not activate for ordinary FEM questions that do not request or require vault grounding.
|
|
|
|
## Inputs
|
|
|
|
- User question and explicit need for configured-vault evidence
|
|
- Resolved vault root, index, relevant pages, and optional companion-skill instructions
|
|
|
|
## Vault Resolution
|
|
|
|
Resolve the first valid root containing `wiki/hot.md` or `wiki/index.md`:
|
|
|
|
1. `FEM_THEORY_WIKI_VAULT` environment variable
|
|
2. A `FEM Solver Theory Wiki` path in project instructions
|
|
3. Optional skill-local `vault-path.txt`
|
|
|
|
`vault-path.txt` is a machine-local, untracked override created from `vault-path.example.txt`; never commit a workstation path. If no root resolves, report the missing configuration and ask for a path rather than answering as though it came from the vault.
|
|
|
|
## Workflow
|
|
|
|
1. Read `<vault>/wiki/hot.md`; use the vault retrieval command when its own instructions provide one, otherwise read `wiki/index.md`.
|
|
2. Read the smallest sufficient set of relevant pages, normally three to seven.
|
|
3. For nontrivial derivation, solver design, ambiguity, or verification design, follow `<vault>/skills/think/SKILL.md` when present.
|
|
4. Follow `<vault>/skills/wiki-query/SKILL.md` when present. Resolve its relative links from that companion skill directory and keep them inside the vault.
|
|
5. Synthesize in the user's language with `[[Page Name]]` citations on core technical claims. Label inference and missing coverage explicitly.
|
|
|
|
Use `<vault>/skills/autoresearch/SKILL.md` only when the user explicitly requests external research or vault updates. That work may use the web or write to the vault only within the user's authorization and the companion skill's safety rules.
|
|
|
|
## Output
|
|
|
|
Lead with the conclusion, then include only relevant formulation, implementation implications, verification, evidence, and vault-gap sections. Short factual questions do not require every section.
|
|
|
|
## Evidence
|
|
|
|
Every core claim traces to a vault page. Cite conflicting pages and explain the conflict; do not silently replace vault evidence with model memory.
|
|
|
|
## Boundary
|
|
|
|
Do not modify the vault during ordinary queries, invent a configured path, force-load every companion skill, or present external research as existing vault knowledge. A missing companion skill limits that mode but does not block direct read-only vault synthesis when the index and relevant pages are available.
|