axon-ivy-dev-skills

Rules and best practices for Axon Ivy HTML Dialog implementations including PrimeFaces, PrimeFlex, CSS, JS, and Ivy components.

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.

Rules and patterns for error handling in Axon Ivy projects — `BpmError` construction, error code naming, error start events in processes, exception walking, and the boundary between Java exceptions and Ivy errors. Use whenever Java code needs to surface a recoverable failure into a process, or when a process needs to react to a Java-thrown error.

Rules and patterns for JAX-RS REST endpoints in Axon Ivy projects. Covers `@Path` / HTTP method annotations, parameter binding, building `Response` objects, mapping exceptions to HTTP status codes, and `@RolesAllowed` auth. Use whenever Java code in `src/` defines, modifies, or consumes a REST resource (`@Path`-annotated class).

Verification checklist for Liquibase changelogs in Axon Ivy projects. MUST be used after the `axon-ivy-liquibase` skill, or whenever a `.sql` / `.xml` file under `<project>/liquibase/` is created or modified.

Conventions and patterns for Liquibase changelogs in an Axon Ivy project. Use whenever you create, edit, or order schema migrations under `<project>/liquibase/`. Pairs with `axon-ivy-liquibase-verify` (post-edit checklist).

Rules and patterns for plain JPA (`@Entity`, `EntityManager`, `persistence.xml`) inside an Axon Ivy project, with the Hibernate provider. Use whenever Java code in `src/` defines `@Entity` classes, configures persistence units, or chooses fetch / cascade strategies. Pairs with `axon-ivy-persistence-utils` when the project uses the helper library on top.

Read holidays, free days, and working-day information from the Axon Ivy Business Calendar. Use whenever Java code needs to determine working days, public holidays, vacation calendars, or capacity planning based on a configured business calendar.

Verification checklist for PrimeFaces components — column widths, table layout, AJAX updates, and common rendering pitfalls.

Create repository classes for persisting entities. Dispatches between Ivy.repo() (default) and JPA/SQL (advanced) approaches.

Step-by-step guide for creating complete Axon Ivy workflow processes. Use this skill FIRST when building new workflows.

Create and manage CMS (Content Management System) content — multi-language YAML files, binary content (files), and Portal CMS overrides.

Verification checklist for Axon Ivy CMS files (cms_*.yaml). MUST be used after axon-ivy-cms skill to catch common errors.

Generate detailed requirements and implementation stories from simple user input. Use when a user provides vague requirements, needs a structured requirements document, or wants to create implementation stories.

Provide format for Axon Ivy users/roles configurations. Use when working with Axon Ivy users/roles.

Reviews generic, framework-agnostic Java source code for Clean Architecture, Ports and Adapters, and SOLID principles. Use this when asked to "review Java code," "check architecture," "refactor for decoupling," or evaluate domain isolation.

Entry point for creating and updating tests. Use this skill when user asks to write/update/delete tests.

Rules and patterns for Axon Ivy data classes (.d.json files).

Implement a story generated by axon-ivy-requirements-creation. Maps story types to skills, handles dependencies, and tracks progress.

Scaffold a new Axon Ivy project. Asks for project name, group ID, and artifact ID, then generates the project from the bundled template in this skill folder.

Create AI-powered data extraction and processing in Axon Ivy workflows using the Smart Workflow AgenticProcessCall element.

Import an Axon Ivy Marketplace item into the codebase. Optionally adds it as a dependency to one or more projects. Asks for the item name, version, and target projects.

Define custom fields in custom-fields.yaml for tasks, cases, and process starts. Use when working with custom metadata on workflow elements.

Rules and patterns for Java model classes, enums, DTOs, and persistence (Ivy.repo() or JPA/SQL) in Axon Ivy projects.

Provide information and rules for Axon Ivy variables configurations. Use when working with Axon Ivy variable.

Reviews JavaScript code for clean architecture, audit compliance (no client-side cookie/storage manipulation), DRY principles, and file organization. Use this when asked to "review JavaScript code," "review JS," "check JS quality," or evaluate frontend code.

Verify story implementation by checking acceptance criteria, loading verify parts from other skills, and validating UI behavior (field interactions, disable/enable, show/hide, validations).