config-platform-change

Name: config-platform-change
Author: vllm-project/semantic-router

$npx mdskill add vllm-project/semantic-router/config-platform-change

Synchronizes config representations across router config, CLI schema, and dashboard UI

Identifies all affected config layers for a change in router config, CLI schema, or dashboard UI.
Modifies the config concept across all identified surfaces (router, CLI, dashboard).
Verifies consistency between modified surfaces using `make agent-report` command.
Validates constraints and delivers results to user via `make agent-ci-gate` command.

SKILL.md

.github/skills/config-platform-changeView on GitHub ↗

---
name: config-platform-change
category: primary
description: 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.
---

# 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

1. Read change surfaces and module boundaries to identify all config layers affected
2. Modify the config concept across all touched surfaces (router, CLI, dashboard)
3. Run `make agent-report ENV=cpu CHANGED_FILES="..."` to verify surface consistency
4. Run `make agent-ci-gate CHANGED_FILES="..."` to validate constraints
5. 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

- [docs/agent/change-surfaces.md](../../../../docs/agent/change-surfaces.md)
- [docs/agent/module-boundaries.md](../../../../docs/agent/module-boundaries.md)

## 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

More from vllm-project/semantic-router

Skill	Description
cross-stack-bugfix	Diagnoses and fixes bugs that span multiple layers (runtime, CLI, UI, platform, tests) requiring coordinated changes across surfaces. Use when a bug does not map cleanly to a narrower skill, the fix touches more than one surface, or changes need cross-cutting validation.
dashboard-platform-change	Modifies dashboard frontend or backend surfaces that present, configure, or manage router behavior through the console UI. Use when changing dashboard pages or components, backend handlers, console persistence, auth or session flows, or user-visible routing metadata in the dashboard.
fleet-sim-change	Modifies the fleet simulator package, API service, release wiring, or simulator-owned docs and assets as one maintained subsystem. Use when changing src/fleet-sim, simulator release workflow, or fleet-sim-owned docs and assets under website/.
harness-contract-change	Modifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.
k8s-platform-change	Modifies Kubernetes-facing operator, CRD, deployment-profile, or DSL translation behavior for semantic-router platform integration. Use when changing operator APIs or controllers, deployment stack manifests, profile-owned platform wiring, or router-to-Kubernetes translation layers.
maintainer-issue-pr-management	Manages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.
maintainer-release-ops	Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, create milestone issues, sync GitHub issue or PR state, generate a daily review brief, or manage stale PRs and backlog routing.
openclaw-vsr-bridge	Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.
plugin-end-to-end	Implements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.
router-service-platform-change	Modifies router-side API, authz, memory, provider, storage, or runtime service modules outside config, decision, selection, and extproc plugin chains. Use when changing apiserver endpoints, authz or rate-limit policy code, memory or response storage flows, provider adapters, or other router service-platform modules.