agentleFS
Sign inStart free
open-edge-platformopen-edge-platform/training_extensions/skills/application/geti-ui-dev/SKILL.md

geti-ui-dev

Skill1.4k starsChanged 17 days agoApache-2.0View on GitHub

Develop and validate changes in `application/ui/` for the React and TypeScript frontend. Use when touching `application/ui/src/**`, frontend tests, RSBuild or Rstest 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.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 2 mentionsMar 2026: 2 mentionsApr 2026: 7 mentionsMay 2026: 2 mentionsJun 2026: 3 mentionsJul 2026: 2 mentionsAug 2026: 3 mentionsSep 2026: 4 mentionsOct 2026: 9 mentionsNov 2026: 5 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the open-edge-platform/training_extensions repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about open-edge-platform/training_extensions

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Node >=24.2.0 and npm >=11.14.0.

    line 14
  2. Very specific:

    Start with npm run format:check, npm run lint, npm run cyclic-deps-check, and npm run type-check.

    line 16
  3. Very specific:

    Keep the change inside the existing UI structure under src/ unless the task explicitly calls for build or tooling updates.

    line 20
  4. Distinctive:

    Use existing component, routing, testing, and styling patterns instead of introducing a new structure.

    line 21
  5. Very specific:

    Use npm run format:check for Prettier verification.

    line 27
  6. Very specific:

    Use npm run lint, npm run cyclic-deps-check, and npm run type-check for normal code changes.

    line 28
  7. Very specific:

    Use npm run test:unit or npm run test:unit:coverage for logic and component behavior covered by Rstest.

    line 29
  8. Very specific:

    Use npm run test:component or npm run test:e2e only when the task reaches Playwright coverage.

    line 30
  9. Very specific:

    Use npm run build before finishing broader UI changes.

    line 31
  10. Very specific:

    Use $geti-openapi-sync when backend API changes are part of the task.

    line 37
  11. Distinctive:

    Keep generated API artifacts and the consuming UI changes in the same change set when the contract changes.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Geti UI Development

For the full architecture reference (feature-folder layout, data fetching, and generated API types) read the application/ui/AGENTS.md file.

Quick Start

  • Work from application/ui/.
  • Use Node >=24.2.0 and 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, and npm run type-check.

Workflow

  1. Keep the change inside the existing UI structure under src/ unless the task explicitly calls for build or tooling updates.
  2. Use existing component, routing, testing, and styling patterns instead of introducing a new structure.
  3. Regenerate API types instead of hand-editing them when the backend contract changes.
  4. 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:check for Prettier verification.
  • Use npm run lint, npm run cyclic-deps-check, and npm run type-check for normal code changes.
  • Use npm run test:unit or npm run test:unit:coverage for logic and component behavior covered by Rstest.
  • Use npm run test:component or npm run test:e2e only when the task reaches Playwright coverage.
  • Use npm run build before finishing broader UI changes.

API Type Notes

  • npm run build:api reads src/api/openapi-spec.json and regenerates src/api/openapi-spec.d.ts.
  • npm run update-spec downloads the spec from https://localhost:7860 (self-signed TLS, fetched with --insecure) and then rebuilds the TypeScript types.
  • Use $geti-openapi-sync when backend API changes are part of the task.

Coordination Notes

  • @geti-ui/ui and @geti-ui/smart-tools are consumed as regular published npm dependencies (npm install/npm ci) — no clone/preinstall step, do not vendor them locally.
  • Keep generated API artifacts and the consuming UI changes in the same change set when the contract changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free