Snippets

Reusable text blocks expanded via #hashtag in messages. Use the plugin's README as the source of truth for installation, configuration, and supported syntax.

Locations and configuration

Check only the documented global and project snippet directories. Snippet configuration is always snippet/config.jsonc; plural snippets/ supports Markdown snippets only.

When modifying configuration:

1. Check both documented configuration locations.
2. Modify the existing location when only one exists.
3. Ask the user which location to modify when both exist.
4. Create the global configuration when neither exists.

Snippet format

The filename (without .md) is the primary hashtag. Frontmatter is optional:

---
aliases:
  - short
description: Optional
---
Content here

Authoring rules

• Read Creating snippets before creating or restructuring a snippet.
• When users ask for inputs, choices, defaults, or conditional wording, read Fields and forms. Translate their ordinary language into typed fields and add only requested constraints.
• Define fields in a YAML frontmatter fields mapping. Use ordinary Handlebars variables and conditions in the body. Keep familiar names as nested preset snippets when consolidating variants.
• Use !> rather than !`cmd` when the command itself helps the model interpret its output.
• Use <inject> only for context that must persist for the whole turn.
• Treat #skill(...) as hidden context injection, not inline expansion.
• Interpret #_name as an escaped reference to #name; do not expand it.

Library

/snippets opens the library for browsing, creating, editing, deleting, and reloading snippets. Edit aliases, descriptions, and fields in the source editor. Ctrl+G or Edit snippet fields in the command palette edits an invocation under the composer cursor. Agents can manage the Markdown files directly.

Sharing snippets

Share to GitHub Discussions.

1. Check that gh --version succeeds.
2. If it is available, use the question tool to get approval to post and ask when the user uses the snippet. Use a body file with gh rather than an inline body.
3. If it is unavailable, open the new-discussion URL and ask the user for the same usage context.