---
name: Maintain Adaptive Surfaces
slug: maintain-adaptive-surfaces
category: AI Engineering
description: Maintain Adaptive Surfaces keeps NeMo Relay’s adaptive config, plugin lifecycle, bindings, and docs aligned. Use it when changing the canonical adaptive model or when users still say optimizer.
github: "https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-optimizer"
language: Rust
stars: 165
forks: 67
install: "npx degit https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-optimizer ~/.claude/skills/maintain-optimizer"
installs_to: ~/.claude/skills/maintain-optimizer
source_path: .agents/skills/maintain-optimizer/SKILL.md
collection_size: 25
category_size: 3670
collection_url: "https://dirskills.com/collections/NVIDIA/NeMo-Relay"
added: 2026-09-08T05:35:20.263Z
last_synced: 2026-09-08T05:35:20.263Z
canonical_url: "https://dirskills.com/skills/maintain-adaptive-surfaces"
---

# Maintain Adaptive Surfaces

Maintain Adaptive Surfaces keeps NeMo Relay’s adaptive config, plugin lifecycle, bindings, and docs aligned. Use it when changing the canonical adaptive model or when users still say optimizer.

**Install:**

```bash
npx degit https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-optimizer ~/.claude/skills/maintain-optimizer
```

## README

# Maintain Adaptive Surfaces

## Companion Guidance

Use `karpathy-guidelines` alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.

Use this skill when changing adaptive config schema, built-in sections, shared
plugin lifecycle, plugin registration, or binding-native helper
APIs.

## Public Boundary

The stable adaptive boundary is the config document plus the shared plugin
lifecycle:

- Config types and policies
- Built-in adaptive section helpers
- Plugin registration and composition
- Plugin lifecycle
- Reports and diagnostics

There is no separate public adaptive runtime handle.

See `docs/plugins/adaptive/configuration.md` and
`docs/about/concepts/plugins.md`.

## Keep In Sync

- `crates/adaptive`
- Shared plugin behavior in core and bindings
- Python adaptive/plugin wrappers in `python/nemo_relay/adaptive.py` and
  `python/nemo_relay/plugin.py`
- Go adaptive helpers under `go/nemo_relay/adaptive` plus shared plugin
  helpers in `go/nemo_relay`
- Node.js adaptive helpers and plugin wrappers
- Docs and examples that show canonical config shapes

## Checklist

- [ ] Dynamic config shape still matches the documented canonical model
- [ ] Typed helper constructors still map cleanly to the same config document
- [ ] Plugin lifecycle is consistent across languages
- [ ] Plugin context surfaces remain aligned
- [ ] Validation/report behavior remains documented and tested
- [ ] Any new component kind has docs, examples, and binding coverage

## Validation

- Run adaptive-focused Rust tests
- Run binding tests for every changed adaptive or plugin surface
- Update adaptive docs and any examples in the same branch

## References

- `docs/plugins/adaptive/configuration.md`
- `docs/plugins/adaptive/about.md`
- `docs/plugins/adaptive/acg.md`
- `docs/plugins/adaptive/adaptive-hints.md`
- `docs/build-plugins/basic-guide.md`
- `docs/build-plugins/validate-configuration.md`
- `docs/about/concepts/plugins.md`
- `validate-change`