Updated 1d ago
by jmix-framework
jmix-agent-toolkit
A collection of skills, guidelines and tools designed to help AI coding agents develop applications using the Jmix framework effectively
21 GitHub stars (21)
+2 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | +2 |
- 22 skills (22 skills found in its SKILL.md files)
- 7 forks (7 forks)
- 1d ago last update (Last updated 1d ago)
Install
Skills CLI
npx skills add jmix-framework/jmix-agent-toolkit
Asks which skills and agents to install. Just one: npx skills add jmix-framework/jmix-agent-toolkit --skill jmix-add-dialog-detail-flow — add -g for every project.
Claude Code
git clone https://github.com/jmix-framework/jmix-agent-toolkitcp -r "jmix-agent-toolkit/content/skills/jmix-add-dialog-detail-flow" ~/.claude/skills/
Copies the jmix-add-dialog-detail-flow skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add jmix-framework/jmix-agent-toolkit
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
jmix-add-dialog-detail-flow
Open a Jmix entity detail view from a button/action and refresh related data after save.
content/skills/jmix-add-dialog-detail-flow/SKILL.md on GitHub (opens in a new tab) -
jmix-add-entity-event-listener
Add Jmix entity lifecycle event listeners to perform additional actions with saved or loaded entities.
content/skills/jmix-add-entity-event-listener/SKILL.md on GitHub (opens in a new tab) -
jmix-add-i18n-keys
Add complete Jmix message keys for entities, enums, views, actions, and validation text, and configure official Jmix framework translations for non-English applications.
content/skills/jmix-add-i18n-keys/SKILL.md on GitHub (opens in a new tab) -
jmix-configure-fetch-plan
Configure or audit Jmix fetch plans in XML views, fragments, DataManager loads, repositories, and entity events when loading references, avoiding N+1 queries, fixing unfetched attribute errors, or tuning data loading.
content/skills/jmix-configure-fetch-plan/SKILL.md on GitHub (opens in a new tab) -
jmix-create-composition-detail-view
Add inline editable parent-child composition UI to a Jmix detail view, when a parent entity owns child records edited via a property-bound collection container (no query loader).
content/skills/jmix-create-composition-detail-view/SKILL.md on GitHub (opens in a new tab) -
jmix-create-detail-view
Create a Jmix Flow UI detail view with XML descriptor, save-close action, messages, and policies.
content/skills/jmix-create-detail-view/SKILL.md on GitHub (opens in a new tab) -
jmix-create-dto-entity
Create or change Jmix DTO entities and other non-persistent transfer models for UI data containers, REST/API payloads, custom data stores, external data, or calculated read models.
content/skills/jmix-create-dto-entity/SKILL.md on GitHub (opens in a new tab) -
jmix-create-entity
Create or change a persistent Jmix JPA entity and its required surrounding artifacts.
content/skills/jmix-create-entity/SKILL.md on GitHub (opens in a new tab) -
jmix-create-enum
Create a Jmix enum for entity attributes with stable database ids and localization.
content/skills/jmix-create-enum/SKILL.md on GitHub (opens in a new tab) -
jmix-create-fragment
Create or change reusable Jmix Flow UI fragments, embedded fragment instances, provided data components, fragment facets, host event subscriptions, or fragment renderers.
content/skills/jmix-create-fragment/SKILL.md on GitHub (opens in a new tab) -
jmix-create-liquibase-changelog
Create Liquibase changelogs that exactly match Jmix entity model changes, and register database changelogs supplied by Jmix add-ons that own persistent entities.
content/skills/jmix-create-liquibase-changelog/SKILL.md on GitHub (opens in a new tab) -
jmix-create-list-view
Create a Jmix Flow UI list view with XML descriptor, data loading, menu, messages, and policies.
content/skills/jmix-create-list-view/SKILL.md on GitHub (opens in a new tab) -
jmix-create-resource-role
Create or update Jmix resource roles with entity, attribute, view, and menu policies, including the CREATE-implies-MODIFY rule.
content/skills/jmix-create-resource-role/SKILL.md on GitHub (opens in a new tab) -
jmix-create-service
Create Jmix service-layer business logic with DataManager, transactions, and no UI coupling.
content/skills/jmix-create-service/SKILL.md on GitHub (opens in a new tab) -
jmix-create-test
Create or update Jmix unit, integration, UI integration, or end-to-end tests for services, entity listeners, security behavior, views, fragments, and persistence workflows.
content/skills/jmix-create-test/SKILL.md on GitHub (opens in a new tab) -
jmix-ide-static-analysis
Gate-1 static checks. PRIMARY when connected: run a Jmix-aware IDE/semantic inspection (e.g. JetBrains get_file_problems) on every file you created/edited — it catches the *-view.xml defects a compiler cannot (unresolved msg://, invalid property paths, missing data containers). Fall back to compileJava plus mechanical descriptor checks when no inspection is available. Read before relying on any s…
content/skills/jmix-ide-static-analysis/SKILL.md on GitHub (opens in a new tab) -
jmix-migrate-theme-to-aura
Switch a project that came from Jmix 2.x over to the Aura theme, including porting Lumo utility classes. Studio's 2.x→3.x migration deliberately keeps Lumo and there is no automated conversion, so every step here is manual. Each step has a SILENT failure mode — the app boots, compiles, and passes a green clean test while still rendering Lumo, or renders Aura tokens on top of Lumo components.
content/skills/jmix-migrate-theme-to-aura/SKILL.md on GitHub (opens in a new tab) -
jmix-run-background-code
Use when writing code that runs outside a user request — a Quartz/scheduled job, an @Async method, an application-startup runner, or an integration event listener. Such threads have no authenticated user, so DataManager fails with "Authentication is not set" the first time the code actually runs. Compile, static analysis, and a green clean test all pass; only the real firing fails.
content/skills/jmix-run-background-code/SKILL.md on GitHub (opens in a new tab) -
jmix-style-ui
Style Jmix Flow UI components — views, fragments, grid renderers, or components built in a controller. Read this before writing any getStyle().set(...), classNames, addThemeVariants, or CSS custom property (--aura-* / --lumo-* / --vaadin-*). A custom property the active theme does not define fails SILENTLY: no error, every gate green, wrong rendering.
content/skills/jmix-style-ui/SKILL.md on GitHub (opens in a new tab) -
jmix-verify-api-symbol
Before typing a class, enum constant, inner-class event, method, or icon name you have not personally verified in this project, confirm it exists. Costs seconds and prevents the most expensive class of failures (hallucinated icon constants, fake event inner classes, wrong package paths). Primary check when connected = the Context7 docs MCP (/jmix-framework/jmix-context7); falls back to grepping t…
content/skills/jmix-verify-api-symbol/SKILL.md on GitHub (opens in a new tab) -
jmix-verify-bootrun
Gate 2 (mandatory) — verify the Spring/Jmix context loads via a TERMINATING `gradle clean test`, never a long-running bootRun. Gate 3 (optional) — if you have a browser/UI-automation tool, walk the views/buttons/fields you created to catch render-time defects that compile and clean test miss. A green compile/clean test is NOT proof a view renders.
content/skills/jmix-verify-bootrun/SKILL.md on GitHub (opens in a new tab) -
jmix
Read FIRST before writing or changing any file in a Jmix application. Lists the project stack, maps the task to Jmix artifacts, routes each artifact to the skill that governs it, and names the checks that close a task. Your Jmix/Vaadin priors are the main source of wrong API names and broken descriptors — start here, not from memory.
content/skills/jmix/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.