Use when writing or editing a SKILL.md, a skill's references/*.md, or an agent definition in this repo — required frontmatter, section ordering, the GDScript-then-C# example convention, and C# parity exemptions.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
File format templates for this repo. See the root CLAUDE.md for the conventions
and size budget that govern the content itself.
Every skill must start with YAML frontmatter:
---
name: skill-name
description: Use when [trigger] — [brief scope]
---
Followed by:
> **Related skills:** **skill-a** for X, **skill-b** for Y.gdscript and csharp language tags)The validator also checks C# parity inside references/*.md (csharp-parity-*-reference), so Pattern X moves stay enforced. Files that section by language (## C#, ## Dash (C#), ### … — C#) are checked file-level instead of per-section; a heading that merely mentions C# in prose is not a partition.
When a section genuinely cannot have a C# counterpart, mark that section — never the whole skill:
<!-- csharp-parity: n/a — C# is statically typed; there is no untyped alternative to contrast -->
It works in both SKILL.md and references/*.md. The reason is mandatory; omitting it is an error (checked on every marker, not only on sections missing C#), because an exemption that cannot say why is indistinguishable from an example nobody wrote. A reason may contain < and >, and a marker inside a fenced block is ignored, so a file can document the marker without exempting itself.
Do not reach for the two blunter tools instead: adding the skill to GDSCRIPT_ONLY_BY_DESIGN exempts every section in it, and renaming a heading to "… (GDScript)" trips the language-partition check and silently downgrades the entire file to a file-level check. Both hide real gaps in neighbouring sections.
A fenced ```gdscript block containing only comments is not a code example — it is prose in a fence, and it will be flagged as an unpaired GDScript block. Write it as prose or a bullet list.
Agent definitions in agents/<name>.md use YAML frontmatter:
---
name: agent-name
description: |
When to use, with <example> blocks.
model: inherit
---
Run node scripts/validate-skills.mjs — it enforces frontmatter, cross-references,
and the 16 KB size budget.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when working with 2D-specific systems — TileMaps, parallax scrolling, 2D lights and shadows, canvas layers, particles 2D, custom drawing, and 2D meshes in Godot 4.3+
The English summary is being prepared. Showing the original description.
Use when working with 3D-specific systems — materials, lighting, shadows, environment, global illumination, fog, LOD, occlusion culling, and decals in Godot 4.3+
The English summary is being prepared. Showing the original description.
Use when building character abilities — Resource-based abilities with cost/cooldown/cast, buffs/debuffs, stat modifiers, gameplay tags, and HUD binding
The English summary is being prepared. Showing the original description.
Use when creating Godot editor plugins — EditorPlugin, @tool scripts, custom inspectors, and dock panels
The English summary is being prepared. Showing the original description.
Use when implementing AI movement — NavigationAgent2D/3D, steering behaviors, behavior trees, and patrol patterns
The English summary is being prepared. Showing the original description.
Use when implementing animations — AnimationPlayer, AnimationTree, blend trees, state machines, sprite animation, and code-driven animation
The English summary is being prepared. Showing the original description.