field-guide

Plugin field-guide from marketplace vibe-garden in rjroy/vibe-garden. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• ingest

  Use when distilling useful project understanding from eligible .lore/ artifacts into the reference wiki. Historical artifacts suggest candidates; current claims are checked against implementation and tests. Triggers include "ingest this", "distill reference knowledge", "update the reference", and "p

• init

  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".

• lint

  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'.

• query

  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.

• resolve-drift

  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 refere

• stratify

  Use when the wiki has outgrown its flat layout and pages need grouping into category directories. Reorganizes .lore/reference/ into category and subcategory trees, rewrites the index, and repairs every referrer. Triggers include "stratify the wiki", "organize the reference directory", "group the wik

• update-evidence

  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".