You configure crickets primitives and plugins with YAML manifests. You use two layers. The per-primitive frontmatter describes the primitive. You place this atop each SKILL.md / hook.md / agent .md / …. The per-group group.yaml describes the plugin. The scripts/lint_src.py script validates both layers. You run this script in CI + check-all.sh. You can find the source of truth at src/SCHEMA.md.

You use these fields in the primitive frontmatter atop a manifest file:

The primitive's group is the folder it lives in. You do not use a group: field.

crickets primitives are operator-scoped rather than project-scoped: a plugin installs once for the machine and travels with you. There is no per-primitive placement field — an install_scope key survived here as inert metadata from the v2 manifest schema until it was retired, and nothing ever read it.

You place one group.yaml in each src/<group>/. This file describes the plugin. The group slug is the folder name. You never write it as a field.

Invariant (lint-enforced): standalone: true ⟺ requires: []. You create an integrated plugin when it requires another. You create a standalone plugin when it requires nothing. The enhances field is orthogonal. It acts as a soft augmentation. A standalone plugin may still enhance a target.

# src/code-review/group.yaml
name: Code Review
requires: []
standalone: true
enhances:
  - group: development-lifecycle
    capability: review
    effect: "/review dispatches the adversarial reviewers"

You can read Plugin anatomy to learn how you compose these into a plugin.

You place a skill at skills/<name>/SKILL.md. You use <kind>/<name>.<ext> for other kinds. You can read Per-host paths for details.

---
name: pii-scrubber
description: Scan the current git diff for personal information before commit or push.
kind: skill
supported_hosts: [claude-code, antigravity]
version: 0.1.0
---

<skill body — operational instructions for the agent>

The generator finds a primitive by walking a group's <kind>/ subdir. It looks for a manifest file:

The other enum values (mcp-server, status-line, workflow, settings-fragment) are valid kinds. They have no discovery path or instance yet. A group's scripts/ dir is a group asset. It is not a kind. The generator copies it verbatim to <plugin>/scripts/. You reference it as ${CLAUDE_PLUGIN_ROOT}/scripts/<name> on Claude Code. You reference it as the relative scripts/<name> on Antigravity. Antigravity runs from inside the plugin dir.

The scripts/lint_src.py script asserts these rules:

• group.yaml — You must provide name / description / standalone. The standalone field must be a bool. The requires field must be a list of existing group slugs. You must maintain the invariant standalone ⟺ requires:[]. The capabilities field must be a list. Each enhances target must exist. The target cannot be the group itself. The target cannot be in requires. You must declare any named capability on the target.
• Primitive frontmatter — You must provide name / description / kind / supported_hosts. The supported_hosts field must be a non-empty subset of [claude-code, antigravity].

python3 scripts/lint_src.py

• Plugin anatomy — You learn what a plugin is + its overall structure.
• Customization types — You learn what each kind means.
• Per-host paths — You learn where each kind lands, per host.
• Host adapters — You learn how the renames map this field feeds differs, host by host.
• Modify a plugin — You learn how to edit src/, regenerate, and dogfood.
• src/SCHEMA.md — You can read the source schema this mirrors.