菜单
Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when checking whether field-guide reference pages still match current code and tests. Reads pages plus fg-evidence anchors, reports or fixes semantic drift, and can use sub-agents for parallel audit batches. Triggers include "resolve drift", "semantic drift", "check accuracy", "verify the reference against code", and "audit the wiki".
Use after ingesting or editing field-guide pages to attach living code/test anchors. Adds or refreshes fg-evidence metadata without trying to prove prose accuracy. Triggers include "update evidence", "wire evidence", "add evidence anchors", and "connect the wiki to code".
Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".
Use when setting up field-guide on a project for the first time, or to refresh the scheduled lint job after it expires. Triggers include "init field-guide", "set up field-guide", "refresh field-guide lint schedule", and "bootstrap the wiki".
This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.
Use when exploring before committing, thinking through trade-offs, or digesting sketches and diagrams. Triggers include "let's brainstorm", "what if we...", and "explore options". Bad ideas welcome, questions over answers, mistakes on purpose.
| name | query |
| description | Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki. |
Answer a question using the project wiki and work artifacts. Cite every source. Offer to persist the answer as a synthesis page.
Read the field-guide index first. Prefer .lore/reference/index.md; if it does not exist, read .lore/reference/index.html. Scan all listed pages to identify which are relevant to the question. Relevance is broad — include any page whose subject could bear on the answer, even indirectly.
Read every candidate page in full. Candidate pages may be Markdown or HTML. For HTML pages, use meta tags as metadata and visible body content as the page body. Then scan .lore/work/ for supported source documents (.md and .html specs, designs, retros, plans, research) that may contain context not yet extracted into the wiki. Use judgment: if the question is about a decision, check plans and specs. If it's about what broke, check retros. If it's about how something works, check architecture and research documents.
If no relevant material exists, say so. Don't synthesize an answer from general knowledge when the question is asking what this project specifically decided or learned.
Give a direct answer, then the supporting evidence. If sources conflict, name the conflict and both positions — don't arbitrate silently.
After the answer, list every file cited. Use the file path as the identifier. Example:
Sources:
.lore/reference/auth-flow-decision.md,.lore/work/specs/auth-spec.md
After delivering the answer, ask whether to save it as a synthesis wiki page. If the user accepts:
Write a Markdown page at .lore/reference/[descriptive-kebab-name].md with YAML frontmatter:
---
title: Precise noun-first description of what the synthesis answers
date: YYYY-MM-DD
status: current
tags: [kebab-case, terms, subject, domain, question-type]
fg-type: synthesis
fg-sources: [relative/path/to/source1.md, relative/path/to/source2.md]
fg-status: current
---
# Precise noun-first description of what the synthesis answers
<!-- body in Markdown -->
fg-sources lists every source cited in the answer as a YAML list. Sources may be Markdown or HTML files.
The body must be self-contained in Markdown. A reader with no access to the original question or sources should understand what the page is saying and why it exists. Reach for embedded inline HTML only when a visual carries meaning Markdown cannot — color-coded status, inline <svg> diagram, side-by-side comparison. When you do, write it raw and inline; never in a fenced code block.
After writing the page, update the field-guide index. Prefer .lore/reference/index.md; if only .lore/reference/index.html exists, update it in place. Add the new page to the synthesis group. If the group doesn't exist yet, create it. The entry must use the page's title as link text, matching the existing index format. Preserve all other groups and entries.