Found while following the skills on a Jmix 2.8.2 project.
Problem: silent — the instructions say nothing about this case.
Task
Over a single project the work needed a change log of entity edits, application settings editable from a screen, and a translated UI.
Where
content/AGENTS.md and the skill routing list skills per ARTIFACT — entity, view, role, changelog, test. Nothing anywhere lists the Jmix ADD-ONS and which need each one covers.
What happened
Every add-on was found from the project owner's hint rather than from the instructions: audit, application settings, translations. Until the hint, the default was to write it by hand — a custom settings entity instead of AppSettingsEntity, custom translation bundles instead of the ready-made package. No gate catches this, because it is not a defect: it is extra code that then has to be maintained, and a framework capability left unused.
Caught by the project owner, three times in a row.
Suggested fix
A short reference skill, e.g. jmix-choose-addon: a table of "need → add-on → Gradle coordinates → what not to forget when wiring it" for the main add-ons (audit, appsettings, translations, datatools, localfs, dynattr, quartz, reports, webdav, kanban, notifications, message templates). Include the line that an add-on shipping its own tables needs its changelog explicitly included in the master changelog when the project uses explicit includes (see #39).
Found while following the skills on a Jmix 2.8.2 project.
Problem: silent — the instructions say nothing about this case.
Task
Over a single project the work needed a change log of entity edits, application settings editable from a screen, and a translated UI.
Where
content/AGENTS.mdand the skill routing list skills per ARTIFACT — entity, view, role, changelog, test. Nothing anywhere lists the Jmix ADD-ONS and which need each one covers.What happened
Every add-on was found from the project owner's hint rather than from the instructions: audit, application settings, translations. Until the hint, the default was to write it by hand — a custom settings entity instead of
AppSettingsEntity, custom translation bundles instead of the ready-made package. No gate catches this, because it is not a defect: it is extra code that then has to be maintained, and a framework capability left unused.Caught by the project owner, three times in a row.
Suggested fix
A short reference skill, e.g.
jmix-choose-addon: a table of "need → add-on → Gradle coordinates → what not to forget when wiring it" for the main add-ons (audit, appsettings, translations, datatools, localfs, dynattr, quartz, reports, webdav, kanban, notifications, message templates). Include the line that an add-on shipping its own tables needs its changelog explicitly included in the master changelog when the project uses explicit includes (see #39).