菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | init |
| description | 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". |
Bootstrap the project wiki and register a durable scheduled lint job.
This skill requires CronCreate and CronList to be available in the Claude Code harness. If those tools are not present, the wiki directory and Markdown index will still be created, but the scheduled lint job cannot be registered — inform the user that scheduling is unavailable.
1. Create the wiki directory.
Check whether .lore/reference/ exists. If not, create it. Then check whether .lore/reference/index.md or .lore/reference/index.html exists.
If neither index exists, write a minimal Markdown file at .lore/reference/index.md:
---
title: Field Guide Index
date: YYYY-MM-DD
status: current
tags: [index, field-guide]
---
# Field Guide Index
Never overwrite an existing index. If index.html already exists and index.md does not, leave it in place; the other field-guide skills can read either format.
2. Check for an existing lint job.
CronCreate jobs auto-delete when they expire, so any job present in CronList is by definition active. The check is simply: is the job ID present in the CronList results?
Proceed as follows:
.lore/reference/.field-guide.json. If it contains a lint_job_id, call CronList and check whether that ID appears in the results. If it does, skip to the summary step — do not create a second job..field-guide.json is absent, unreadable, or contains no lint_job_id, call CronList and scan for any job whose prompt is /field-guide:lint. If one is found, write its ID to .field-guide.json (preserving any existing schedule value, or omitting it if unknown), then skip to the summary step.3. Translate the schedule value.
Before calling CronCreate, convert the user's requested schedule to a 5-field cron expression:
daily → "3 8 * * *" (08:03 every day)weekly → "3 8 * * 1" (08:03 every Monday)"3 8 * * *"4. Register the lint job.
If no active job was found, call CronCreate with:
prompt: /field-guide:lintdurable: trueschedule: the translated cron expression from step 3Store the returned job ID in .lore/reference/.field-guide.json:
{ "lint_job_id": "<id>", "schedule": "<schedule>" }
5. Tell the user what happened.
Confirm whether the directory and index were created or already existed. If an existing HTML index was found, mention that it was preserved for compatibility. Confirm whether a new lint job was registered or an existing one was found. Report the job ID and schedule.
Include this notice: recurring CronCreate jobs expire after 7 days. Re-run /field-guide:init to refresh the scheduled lint job before it lapses.
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".
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 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.
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.