Scaffold a new NEML2 `Model` subclass under `neml2/models/<domain>/`. NEML2 models are pure Python classes deriving from `neml2.models.model.Model` (an `nn.Module`), declared via a `HitSchema`, decorated with `@register_neml2_object("TypeName")`, and tested with a `.i` driver under `tests/models/<domain>/`. Trigger on any "add a Foo model", "scaffold a new yield function", "create an SR2-to-SR2 mapping", etc.
Add a NEML2 regression test under `tests/regression/<submodule>/<scenario>/` that pins a model's current behavior against a checked-in `gold/result.pt` reference. Trigger on phrases like "add a regression test for X", "scaffold a regression scenario", "create a TransientRegression for this model", "the regression suite is missing coverage for Y". For tests that compare against a *known* truth (analytical solution, benchmark data), use `add-verification` instead.
Author a new NEML2 tutorial page under `doc/content/tutorials/`. Tutorials are self-contained, Colab-runnable Jupyter notebooks (`main.ipynb`, no jupytext pairing) with executable code cells; they create their own input files in-notebook via `%%writefile` (no sibling files, no `{literalinclude}`) and carry an auto-injected "Open in Colab" badge. Trigger on phrases like "add a tutorial for X", "write a tutorial about Y", "I need a notebook-style doc page demonstrating Z". For static reference pages without executable cells, see `add-doc` instead.
Add a NEML2 verification test under `tests/verification/<submodule>/<scenario>/` that compares model output against an external ground truth — analytical solution, established benchmark code (NEML1, WARP3D, etc.), or a closed-form physical-intuition result. Trigger on phrases like "add a verification test for X", "verify against the analytical solution", "set up a Verification driver", "compare to benchmark data". For tests that pin current behavior to a `gold/result.pt` of the model's own output, use `add-regression` instead.
Build the NEML2 Sphinx documentation locally. Use when the user asks to build, regenerate, preview, or serve the docs (e.g., "build the docs", "preview the documentation", "the doc build is failing", "run sphinx-build", "run sphinx-autobuild"). Walks through the `pip install` → `sphinx-build` (or `sphinx-autobuild` for live preview) pipeline using the shibuya theme + MyST-NB markdown/notebook backend, the syntax-catalog extension, and the front-matter recipe for tutorial pages that embed executable `{code-cell}` blocks.
Add or revise a static NEML2 documentation page under `doc/content/` — physics-module pages, top-level reference pages, migration guides, and the cross-references between them. Use this for narrative documentation that doesn't need executable code cells. For runnable, notebook-style tutorial pages use the `add-tutorial` skill. For per-type catalog pages (`doc/generated/syntax/`), nothing — those autogenerate from `neml2-syntax --json` via the `neml2_syntax` Sphinx extension.