Menu
Rules and best practices for Axon Ivy HTML Dialog implementations including PrimeFaces, PrimeFlex, CSS, JS, and Ivy components.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Rules and patterns for the `com.axonivy.utils.persistence` library — the Axon Ivy community helper around JPA. Covers `AuditableIdEntity`, `AuditableIdDAO`, `CriteriaQueryContext`, and `UpdateQueryContext`. Use whenever Java code in `src/` reads or writes data through a DAO that extends `AuditableIdDAO` or an entity that extends `AuditableIdEntity`.
Rules and patterns for creating, editing, reviewing, and fixing Axon Ivy workflow processes (.p.json files). Use this when working with any .p.json file — including checking existing processes for errors, reviewing script code, or fixing IvyScript issues.
Verification checklist for Axon Ivy process files (.p.json). Use this whenever a .p.json file is created, modified, or reviewed — either after axon-ivy-process skill, or when a user asks to check, verify, or fix a process file for errors.
Master router skill for all requirement clarification, create story, development, review, and testing tasks. Detects user intent and orchestrates the correct path using specialized skills and parallel subagents.
Rules and patterns for sending email from an Axon Ivy project. Covers sender / recipient resolution, subject and body templating, attachments, and the recommended builder pattern for one mail type per class. Use whenever Java code or a process step composes or sends an email.
Cut a new release version of an Axon Ivy project. Creates a release branch off `develop`, bumps Maven versions, optionally adds a Liquibase folder for schema changes, builds, generates the site report, and tags the release commit. Use whenever the user asks to "release", "cut a release", or "bump the version" of an Ivy project.
| name | axon-ivy-html |
| description | Rules and best practices for Axon Ivy HTML Dialog implementations including PrimeFaces, PrimeFlex, CSS, JS, and Ivy components. |
Every HTML dialog consists of 3 files, all inside one named subfolder under src_hd/. Never put XHTML in webContent/ and never put the dialog data class in dataclasses/.
src_hd/<namespace-path>/<DialogName>/
├── <DialogName>.xhtml ← the UI template
├── <DialogName>Data.d.json ← dialog data class
└── <DialogName>Process.p.json ← HTML_DIALOG logic process
namespace = <package>.<DialogName> (e.g. invoice.parser.upload.UploadInvoice)config.data = <namespace>.<DialogName>Data (e.g. invoice.parser.upload.UploadInvoice.UploadInvoiceData)Load the appropriate file when creating a new dialog:
dialog-template.mddialog-component.mdThese references are needed for every HTML dialog:
primefaces.md — JSF & PrimeFaces component rulescss-js.md — Styling, layout, icons, CSS & JS rulesform-design.mdp:datePicker) → Load date-picker.mdp:fileUpload) → Load file-upload.md
logic-process-example.md#{logic.*}, #{data.*}) → Load logic-process.md and ../axon-ivy-process/code.mdmanaged-bean.md<ic:*>) → Load ivy.mdicons.txtaxon-ivy-cms skill to create CMS entries