Run any Skill in Manus with one click

dashboard-platform-change

Stars4,986

Forks758

UpdatedMarch 26, 2026 at 12:24

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

vllm-project

vllm-project/semantic-router

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

SKILL.md

readonly

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

Read change surfaces and the nearest dashboard rules to understand the affected console flow
Modify the dashboard frontend or backend surface and identify whether the change is config UI, routing visibility, or console-platform behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces
Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
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

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 this repository

same repository

openclaw-vsr-bridge

vllm-project/semantic-router

Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.

2026-07-135.0k

vllm-semantic-router-harness

vllm-project/semantic-router

Bridges native skill discovery into the vLLM Semantic Router repository harness, routing tasks through the canonical agent-report flow, repo-local skill registry, and validation commands. Use when starting any task inside the vLLM Semantic Router repository to resolve the correct primary skill, read canonical docs, and run harness validation.

2026-05-305.0k

config-platform-change

vllm-project/semantic-router

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.

2026-05-305.0k

k8s-platform-change

vllm-project/semantic-router

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.

2026-05-305.0k

maintainer-issue-pr-management

vllm-project/semantic-router

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.

2026-05-305.0k

maintainer-release-ops

vllm-project/semantic-router

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.

2026-05-305.0k

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

Read change surfaces and the nearest dashboard rules to understand the affected console flow
Modify the dashboard frontend or backend surface and identify whether the change is config UI, routing visibility, or console-platform behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces
Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
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

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