dashboard-platform-change
$
npx mdskill add vllm-project/semantic-router/dashboard-platform-change- Change dashboard frontend pages, components, or config editing flows - Change dashboard backend handlers, console persistence, auth, or session behavior - Change dashboard-only reveal, display, or topology presentation when the upstream router contract is already stable
SKILL.md
.github/skills/dashboard-platform-changeView on GitHub ↗
--- name: dashboard-platform-change category: primary description: 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. --- # Dashboard Platform Change ## Trigger - Change dashboard frontend pages, components, or config editing flows - Change dashboard backend handlers, console persistence, auth, or session behavior - Change dashboard-only reveal, display, or topology presentation when the upstream router contract is already stable ## Workflow 1. Read change surfaces and the nearest dashboard rules to understand the affected console flow 2. Modify the dashboard frontend or backend surface and identify whether the change is config UI, routing visibility, or console-platform behavior 3. Run `make agent-report ENV=cpu CHANGED_FILES="..."` to identify impacted surfaces 4. Run `make agent-ci-gate CHANGED_FILES="..."` to validate the affected constraints 5. Verify frontend callers, backend handlers, and user-visible routing metadata stay aligned ## Gotchas - Dashboard-only presentation work still encodes upstream contracts; verify the emitted data shape before treating the change as cosmetic. - Backend console work can still break frontend callers or local smoke, so validate both ends of the console path. - Keep router-runtime semantics upstream; if the change originates in signal or plugin behavior, let the router-side primary own it and treat dashboard updates as dependent surfaces. ## Must Read - [docs/agent/change-surfaces.md](../../../../docs/agent/change-surfaces.md) - [docs/agent/module-boundaries.md](../../../../docs/agent/module-boundaries.md) - [../../../../dashboard/backend/handlers/AGENTS.md](../../../../dashboard/backend/handlers/AGENTS.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 - Dashboard frontend and backend surfaces remain aligned with router and CLI contracts - User-visible routing metadata stays consistent across config, topology, playground, and console callers - Any new auth, storage, or session behavior is documented in the canonical harness or tracked through the matching indexed debt entry
More from vllm-project/semantic-router
- config-platform-changeSynchronizes 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.
- cross-stack-bugfixDiagnoses 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.
- fleet-sim-changeModifies 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-changeModifies 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-changeModifies 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-managementManages 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-opsMaintainer 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-bridgeInstall 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-endImplements 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-changeModifies 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.