WHEN: before answering any Udon/VRChat docs question. HOW: keyword/fuzzy search the indexed agent-skills repo. Prefer this over inventing APIs from general C# knowledge.

WHEN: user needs a cited explanation of a Udon/VRChat topic. HOW: returns sections with path and line numbers — use citations, do not paraphrase away constraints.

WHEN: starting an Udon session or discovering available skills. HOW: list skills from the repo before reading one with read_skill.

WHEN: you need the full skill contract (rules, refs, templates). HOW: call after list_skills; follow linked rules before writing code.

WHEN: you need the set of UdonSharp rules before coding. HOW: list then read_rule for any rule that applies to the feature.

WHEN: implementing something covered by a named rule (constraints, networking, etc.). HOW: apply purpose/constraints/examples from the rule; do not skip constraints.

WHEN: looking up API/reference docs in references/. HOW: search before inventing method names or event signatures.

WHEN: about to write UdonSharp — first step of template→validate→fix. HOW: list .cs templates, then get_template for the closest match and adapt it.

WHEN: before writing UdonSharp. HOW: use the returned source as the BASE — adapt fields/logic; do NOT invent networking (ownership, Manual sync, RequestSerialization). After adapting, call validate_code.

WHEN: after writing or editing any UdonSharp script (mandatory). HOW: pass full code. If issues: call explain_validation for each unique ruleId, fix, then re-run validate_code until valid. Never ship code that failed validation.

WHEN: validate_code returned issues. HOW: call once per unique ruleId from the result, read the cited rule/docs, apply the fix, then re-run validate_code. Part of the fix loop — do not guess fixes.

WHEN: checking which APIs exist for a target SDK version. HOW: read the matrix before using version-specific features.

WHEN: unsure if a feature (NetworkCallable, PlayerData, PhysBones, etc.) exists or how it works. HOW: search before coding against that feature.

WHEN: BEFORE using any C# feature in UdonSharp (List, Dictionary, Coroutine, LINQ, async, generics, etc.). HOW: check constraints and use documented alternatives. Skipping this causes invalid Udon.

WHEN: any ownership, sync mode, late joiners, serialization, or RPC work. HOW: search before writing synced fields; prefer Manual + RequestSerialization patterns from docs/templates.

WHEN: before writing UdonSharp (prefer with get_template). HOW: use matching examples as the code BASE — adapt, do not invent APIs or networking patterns. Then validate_code.

WHEN: refining structure, performance, or idiomatic UdonSharp. HOW: apply recommended patterns from the repo after drafting from a template.

WHEN: BEFORE using unfamiliar C# patterns or when validate_code fails with a common mistake. HOW: check anti-patterns to avoid; prefer documented alternatives.