Available Skills
Overall Architecture and Infrastructure Layer Implementation Rules cover the "shape" of a user module implemented in the JavaEE development model. intra-mart also provides a large number of platform-specific APIs — accounts, roles, authorization, caching, IM-Workflow, IM-Copilot, and more — for filling in that shape.
When you implement code that follows the shape, or use one of these platform-specific APIs from Java, the agent loads the corresponding skill to implement it. This page lists the available skills by functional category.
Convention Files (rules)
With AI-native development, the nature of agents means implementation sometimes follows generic Java conventions. But the JavaEE development model has intra-mart-specific implementation rules, so following generic conventions alone will not always conform to them.
By having the agent reference convention files that describe these platform-specific implementation rules, the resulting code is more likely to follow the conventions.
| File | Key Contents |
|---|---|
java-architecture.md | Layer structure, dependency rules, exception hierarchy, and factory pattern definitions |
java-service-layer.md | Service layer implementation rules, transaction boundaries, and exception translation definitions |
java-entity.md | Entity class (Mirage ORM) design conventions and audit trail field definitions |
java-code-style.md | Coding conventions such as final, string literals, equals(), and the ban on raw types |
java-naming.md | Naming rules for packages, classes, methods, and variables |
java-javadoc.md | JavaDoc conventions for classes and methods |
java-logging.md | Log levels, masking secrets, and log-level decisions by exception type |
database-ddl.md | Table/column naming conventions, type mapping, and audit trail column definitions (shared between JSSP and Java) |
Architecture, Service Layer, and Database Access Implementation
The three files java-architecture.md, java-service-layer.md, and java-entity.md each have a corresponding skill that provides a more detailed version — not just the convention's key points, but full implementation templates and an anti-pattern catalog.
| Skill | Purpose | Corresponding Convention File |
|---|---|---|
java-im-architecture | Providing implementation templates and an anti-pattern catalog for the layer structure, dependency rules, exception hierarchy, and factory pattern | java-architecture.md |
java-im-service-layer | Implementing the service layer (single-repository / multi-repository transaction patterns, etc.) | java-service-layer.md |
java-im-mirage-usage | Implementing entity classes, DAO classes, 2WaySQL, and transaction management using im_mirage, the database access foundation | java-entity.md |
What these three skills generate is the same as what is explained on the pages of this guide from Overall Architecture through Infrastructure Layer Implementation Rules. If you want to understand the implementation approach as reading material, see the body of the guide; if you want the agent to implement it, use the skills above.
IM-Workflow / IM-Propagation / IM-LogicDesigner Integration
Skills for implementing programs that integrate with intra-mart's business platform features (workflow, cross-module data propagation, and logic flows).
| Skill | Purpose |
|---|---|
java-im-workflow-usage | Implementing IM-Workflow integration programs (action processes, arrival processes, case start/end processes, branch/join condition processes, assignee plugins, case deletion/archival listeners) |
java-im-propagation-generator | Implementing cross-module data propagation with IM-Propagation (sending via PropagationManager, receiving listeners via Decoder/Procedure, and the full set of send/receive configuration files) |
java-im-logic-generator | Implementing custom IM-LogicDesigner flow elements (tasks) |
intra-mart-Specific API Set
Skills for using the various management APIs provided by intra-mart from Java.
| Skill | Purpose |
|---|---|
java-im-storage-usage | File operations using PublicStorage / SessionScopeStorage / SystemStorage |
java-im-identifier-usage | Unique ID issuance with the Identifier API (choosing between get(), unique across a distributed environment, and make(), unique within a single server) |
java-im-lock-usage | DB-based exclusive control with the NewLock API |
java-im-cache-usage | Tenant-scoped caching with the CacheManager / Cache API |
java-im-account-usage | Login settings, account locking, account attributes, password verification, and assigning roles to users via AccountInfoManager |
java-im-profile-usage | Fetching, registering, and deleting IM Common Master profile images via UserProfileImageManager |
java-im-role-usage | Registering role definitions, sub-role hierarchies, and category management via RoleInfoManager |
java-im-authz-usage | CRUD on authorization resources, subjects, and policies, and permission checks via AuthorizationClient |
java-im-web-api-maker-usage | Implementing REST APIs with Web API Maker annotations (@WebAPIMaker / @Path / @GET, etc.) |
java-im-secure-token-usage | Issuing and verifying CSRF protection tokens with SecureTokenManager |
java-im-master-usage | CRUD and search for IM Common Master data (users, companies, departments, positions, public/private/company/corporation groups, corporations, customers, item categories, items, currencies) |
java-im-contexts-usage | Retrieving logged-in user information (account, organization, client, job execution parameters) via Contexts.get() |
java-im-configuration-generator | Creating custom XML configuration files (JAXB configuration classes, XSD schemas, XML instances) with ConfigurationLoader |
java-im-message-usage | Retrieving and localizing message properties with MessageManager |
IM-Copilot Extensions
Skills for implementing the IM-Copilot Agent framework, MCP servers, RAG, and Tool Calling.
| Skill | Purpose |
|---|---|
java-im-mcp-generator | Implementing a Streamable HTTP MCP server with the @MCPServer / @Tool annotations |
java-im-copilot-agent-generator | Building an AI agent with Agent / AgentBuilder, and implementing custom tools with UserDefinedTool |
java-im-copilot-rag-generator | Implementing RAG (retrieval-augmented generation) using VectorStore / ActionFactory directly |
java-im-copilot-toolcalling-generator | Implementing provider-agnostic Tool Calling using ChatAction + ToolConfig directly |
All three skills implement AI-related features, but at different levels of abstraction.
- To expose external tools to an AI agent:
java-im-mcp-generator - To wire high-level RAG or Tool Calling into your app through the Agent framework:
java-im-copilot-agent-generator - For low-level implementations that work directly with
VectorStoreorChatAction:java-im-copilot-rag-generator/java-im-copilot-toolcalling-generator