Config Platform Change
Developmentconfig-platform-changeConfig Platform Change is an Agent Skill for development published in the vllm-project/semantic-router repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Synchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vllm-project/semantic-router/blob/HEAD/tools/agent/skills/config-platform-change/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/config-platform-change, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Config Platform Change
Trigger
- Change a config concept that exists in router config and Python CLI schema
- Change config translation between router config and dashboard config UI
- Work on config complexity or representation debt before Kubernetes-facing translation
Workflow
- Read change surfaces and module boundaries to identify all config layers affected
- Modify the config concept across all touched surfaces (router, CLI, dashboard)
- Run
make agent-report ENV=cpu CHANGED_FILES="..."to verify surface consistency - Run
make agent-ci-gate CHANGED_FILES="..."to validate constraints - Record any intentional remaining mismatches as indexed debt entries
Gotchas
- Do not update the router config contract without also checking CLI and dashboard config serialization in the same change.
- If defaults, field names, or migration policy change, make the migration posture explicit or record the intentional gap as indexed debt.
Must Read
Standard Commands
make agent-report ENV=cpu CHANGED_FILES="..."make agent-ci-gate CHANGED_FILES="..."make agent-feature-gate ENV=cpu CHANGED_FILES="..."
Acceptance
- The same config concept is represented consistently across router config, CLI schema, and dashboard config UI
- Any intentional remaining mismatch is recorded in the matching indexed debt entry in the same change
- Platform-facing translation tests or validations are updated when behavior changes