gerrit-create
Use when creating or updating Gerrit changes — pushing code for review, amending patch sets, setting reviewers and topics.…
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
$ npx -y skills add ambient-code/platform --skill development --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/developmentContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: frontend-development description: > 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.
Before writing or changing any frontend code, load the project's frontend standards. These are non-negotiable constraints — not suggestions.
$ARGUMENTS
Read all files in `specs/standards/frontend/` before proceeding:
ls specs/standards/frontend/
At minimum, this includes:
1. `specs/standards/frontend/conventions.spec.md` — zero-tolerance rules (no `any`, Shadcn only, React Query for all data, `type` over `interface`, colocated components, feature flags) 2. `specs/standards/frontend/react-query.spec.md` — file structure (ports/adapters/queries), data fetching patterns, testing requirements, validation checklist
Also read the API adapter spec if working on the services layer:
3. `specs/frontend/api-adapter.spec.md` — port interface contract, canonical types, 30 API domains, testability requirements
These apply to every frontend change, no exceptions:
Confirm you have loaded the standards, then proceed with the task. If any of your changes would violate these constraints, stop and discuss with the user before writing code.
Kubernetes-native AI automation platform for intelligent agentic sessions
Use when creating or updating Gerrit changes — pushing code for review, amending patch sets, setting reviewers and topics.…
Use when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels.…
Use when submitting or preparing a Gerrit change for merge — checking submit requirements, rebasing, resolving comments, and…
Run a convention alignment check across the codebase to measure adherence to documented standards. Use when you want to check…
Perform a comprehensive code review using repository-specific standards. Use when reviewing code changes, checking PR quality,…
Perform any development work on the ambient-ui component. Full workflow instructions.