Run any Skill in Manus with one click

k8s-platform-change

Stars2

Forks0

UpdatedMarch 26, 2026 at 12:24

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.

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

BruceLoveDecimal

BruceLoveDecimal/semantic-router

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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

Kubernetes Platform Change

Trigger

Change operator APIs, CRDs, or controller-facing config translation
Change deployment-profile manifests or profile-owned platform wiring under deploy/kubernetes/**
Change router-to-Kubernetes DSL translation or config bridging layers

Workflow

Read change surfaces, module boundaries, and the E2E selection playbook for the affected Kubernetes-facing surface
Modify the operator, deployment profile, or DSL translation behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces and affected profile coverage
Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
Verify control-plane behavior, stack-manifest behavior, and DSL translation still describe the same platform contract

Gotchas

Do not hide control-plane and stack-resource differences; they can change in the same loop, but they should remain explicit in the final report.
Manifest-only edits still need profile-aware validation when they change response-api, authz, observability, or routing stack behavior.
Router config representation debt belongs to config-platform-change; Kubernetes-facing translation and deployment ownership belong here.

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

Operator APIs, DSL translation, deployment manifests, and affected Kubernetes validation paths stay aligned
Profile-owned resources and control-plane behavior remain explicit even when they change in the same loop

More from this repository

same repository

claude-code-install

BruceLoveDecimal/semantic-router

Guides coding agents through a session-isolated install of the vllm-sr CLI. The install is scoped to a temporary directory so it does not modify the user's global PATH or system packages. Use when an agent or user wants to try vllm-sr without a permanent install.

2026-04-212

routing-calibration-loop

BruceLoveDecimal/semantic-router

Calibrates routing changes against a live router endpoint with executable probes, local DSL validation, versioned deploys, and structured failure review. Use when tuning signals, projections, decisions, or maintained route examples against a real apiserver.

2026-04-022

maintainer-issue-pr-management

BruceLoveDecimal/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-04-022

architecture-guardrails

BruceLoveDecimal/semantic-router

Runs an explicit structural review for boundary-sensitive edits that need dependency, module, and structure-rule scrutiny without forcing that material into every default context pack. Use when a task crosses hotspot boundaries, adds new seams, or needs a deliberate architecture pass.

2026-03-262

config-platform-change

BruceLoveDecimal/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-03-262

dashboard-platform-runtime

BruceLoveDecimal/semantic-router

Maintains dashboard frontend and backend implementation slices that present, configure, or expose router behavior through the console. Use when the task changes dashboard config flows, console backend handlers, topology rendering, playground reveal flows, or other user-visible routing metadata in the dashboard.

2026-03-262

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

Kubernetes Platform Change

Trigger

Change operator APIs, CRDs, or controller-facing config translation
Change deployment-profile manifests or profile-owned platform wiring under deploy/kubernetes/**
Change router-to-Kubernetes DSL translation or config bridging layers

Workflow

Read change surfaces, module boundaries, and the E2E selection playbook for the affected Kubernetes-facing surface
Modify the operator, deployment profile, or DSL translation behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces and affected profile coverage
Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
Verify control-plane behavior, stack-manifest behavior, and DSL translation still describe the same platform contract

Gotchas

Do not hide control-plane and stack-resource differences; they can change in the same loop, but they should remain explicit in the final report.
Manifest-only edits still need profile-aware validation when they change response-api, authz, observability, or routing stack behavior.
Router config representation debt belongs to config-platform-change; Kubernetes-facing translation and deployment ownership belong here.

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

Operator APIs, DSL translation, deployment manifests, and affected Kubernetes validation paths stay aligned
Profile-owned resources and control-plane behavior remain explicit even when they change in the same loop