Geti UI Dev
Developmentgeti-ui-devGeti UI Dev is an Agent Skill for development published in the open-edge-platform/geti repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Develop and validate changes in `application/ui/` for the React and TypeScript frontend. Use when touching `application/ui/src/**`, frontend tests, RSBuild or Vitest config, Playwright setup, package scripts, or generated API typings under `src/api`. Helps with Node and npm requirements, install and build commands, lint, typecheck, test workflows, and coordination with backend OpenAPI changes.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/open-edge-platform/geti/blob/HEAD/skills/application/geti-ui-dev/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/geti-ui-dev, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Geti UI Development
For the full architecture reference (feature-folder layout, data fetching, generated API types, and vendored packages) read
application/ui/AGENTS.md.
Quick Start
- Work from
application/ui/. - Use Node
>=24.2.0and npm>=11.14.0. - Install or refresh dependencies with
npm ci. - Start with
npm run format:check,npm run lint,npm run cyclic-deps-check, andnpm run type-check.
Workflow
- Keep the change inside the existing UI structure under
src/unless the task explicitly calls for build or tooling updates. - Use existing component, routing, testing, and styling patterns instead of introducing a new structure.
- Regenerate API types instead of hand-editing them when the backend contract changes.
- Escalate to component (Playwright) or e2e tests only when the change affects rendered browser behavior, i.e. prefer unit over Playwright over e2e tests.
Verification
- Use
npm run format:checkfor Prettier verification. - Use
npm run lint,npm run cyclic-deps-check, andnpm run type-checkfor normal code changes. - Use
npm run test:unitornpm run test:unit:coveragefor logic and component behavior covered by Vitest. - Use
npm run test:componentornpm run test:e2eonly when the task reaches Playwright coverage. - Use
npm run buildbefore finishing broader UI changes.
API Type Notes
npm run build:apireadssrc/api/openapi-spec.jsonand regeneratessrc/api/openapi-spec.d.ts.npm run update-specdownloads the spec fromhttp://localhost:7860and then rebuilds the TypeScript types.- Use
$geti-openapi-syncwhen backend API changes are part of the task.
Coordination Notes
- The
preinstallscript clones pinned Geti UI workspace packages intopackages/; do not edit those generated packages. - Keep generated API artifacts and the consuming UI changes in the same change set when the contract changes.