dashboard-platform-change

Name: dashboard-platform-change
Availability: InStock
Author: vLLM

Orchestrate dashboard frontend and backend changes to align with router contracts.

5.1k|806|Updated Aug 26, 2025

Search Tags:#frontend #backend #dashboard #router #session #auth #change-management

Ready to run

npx skills add https://github.com/vllm-project/semantic-router --skill dashboard-platform-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dashboard-platform-change
Source: https://github.com/vllm-project/semantic-router/tree/main/tools/agent/skills/dashboard-platform-change
Command: npx skills add https://github.com/vllm-project/semantic-router --skill dashboard-platform-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Orchestrates dashboard surface changes in sync with upstream router contracts to maintain UX consistency.
Validates that frontend and backend changes align with routing and config semantics, ensuring a safe rollout.
Use Case: When updating a dashboard page or component, or updating auth/session flows, this skill coordinates changes end-to-end to avoid breaking the console UX.

Quick Start

Update the dashboard platform surface to reflect the new routing for the current contract.

Frequently Asked Questions about dashboard-platform-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate dashboard frontend and backend updates when routing contracts change?▼

Coordinate dashboard updates by orchestrating changes across frontend pages, backend handlers, and session flows to align with router contract updates. This ensures console UI consistency and validates that surface changes match routing semantics before a safe rollout.

When do I need to update auth and session flows for dashboard console changes?▼

Update auth and session flows when modifying dashboard pages, components, or user-visible routing metadata to reflect router contract updates. Coordinating these end-to-end changes prevents breaking console UX during console persistence or configuration updates.

How does validating dashboard surface changes against router schemas work?▼

Validating dashboard surface changes involves running agent commands to enforce constraints and verify that frontend and backend modifications align with upstream router contracts. This validation ensures routing and config semantics remain consistent across the console UI.

Can I use this approach to manage console persistence and config modifications across the stack?▼

Yes, you can manage console persistence and config modifications by orchestrating changes to backend handlers and frontend pages simultaneously. This coordinates updates to dashboard surfaces that present or manage router behavior through the console UI.

What's the best way to avoid breaking console UX when updating dashboard routing metadata?▼

The best way to avoid breaking console UX is coordinating dashboard surface changes in sync with upstream router contracts. This orchestrates frontend, backend, and session flow updates end-to-end, validating that all changes align with routing and config semantics.

Why does my dashboard page break after updating backend handlers without syncing router contracts?▼

Dashboard pages break when backend handler updates are not coordinated with upstream router contracts. Frontend and backend surface changes must be validated against routing and config semantics to ensure console UX consistency and prevent misaligned router behavior.