一键导入
axon-ivy-repository
Create repository classes for persisting entities. Dispatches between Ivy.repo() (default) and JPA/SQL (advanced) approaches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create repository classes for persisting entities. Dispatches between Ivy.repo() (default) and JPA/SQL (advanced) approaches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | axon-ivy-repository |
| description | Create repository classes for persisting entities. Dispatches between Ivy.repo() (default) and JPA/SQL (advanced) approaches. |
When user needs data persistence, choose the approach:
Does the user explicitly request SQL/JPA/database/persistence-utils?
├── NO → Load `ivy-repo.md` — DEFAULT (simple, no DB config needed)
└── YES → Load `jpa-persistence.md` (requires databases.yaml, persistence.xml, DAOs)
DEFAULT: Always load ivy-repo.md unless the user explicitly asks for:
ivy-repo.mdjpa-persistence.mdMANDATORY: After creating or modifying any entity or repository using Ivy.repo(), run the checklist in ivy-repo-verify.md to catch common errors (duplicate key violations, manual ID issues).
Both approaches use axon-ivy-java-data skill for creating model classes and enums.