Install and verify Ambient Code Platform on an OpenShift cluster using quay.io images. Use when deploying Ambient to any OpenShift namespace — production, ephemeral PR test instances, or developer clusters. Covers secrets, kustomize deploy, rollout verification, and troubleshooting.
Perform any development work on the ambient-ui component. Full workflow instructions.
Deploy, update manifests, and troubleshoot the ambient-ui component. Use when creating or modifying deployment manifests, adding ambient-ui to a new overlay, building images, or debugging cluster issues.
Discover domain-specific skills and context before starting any coding or spec work. This is the mandatory first step for every task — no matter how trivial. Triggers on: any code change, spec change, implementation task, bug fix, refactor, feature work, or documentation update that touches component code or specs.
Deploy a PR's images (api-server, control-plane, runner) to any OpenShift namespace for integration testing. Works on both standard OpenShift clusters and MPP managed clusters. Auto-detects the environment and chooses the right script.
End-to-end development workflow for the Ambient Code Platform. Covers ticket → branch → spec → code → commit → PR → review → deploy → verify. Self-improving: update this skill whenever a failure path is discovered or a shortcut is validated. Git history is the audit trail.
Required context for all frontend work. Loads frontend standards (conventions, React Query patterns, adapter testing requirements) before any code changes. Use when modifying anything under components/frontend/. Triggers on: any frontend code change, UI component work, React Query hooks, API adapter work, frontend bug fix, frontend refactor.
Run a convention alignment check across the codebase to measure adherence to documented standards. Use when you want to check health of the codebase, verify convention compliance, get a scored report, find violations, check alignment before a release, or run periodic quality scans. Triggers on: "check conventions", "alignment scan", "codebase health", "are we following our standards", "convention violations", "quality check", "how aligned are we".