Skip to main content

AI-native Development 2026-06-01 Update Details

The 2026-06-01 update includes two major changes.

  1. Release of a container-based development environment
  2. Additions and improvements to coding agent assets

Container-Based Development Environment Assets​

We have released assets for building an Accel Platform development environment with Docker Compose. You can set up the web server, application server, and database required to run Accel Platform as containers. It also includes Apache Cassandra and Apache Solr containers for the IMBox and IM-Copilot features. In addition, it includes Accel Studio Testing Agent as an E2E testing environment and Mailpit as a fake SMTP server. With these assets, you can quickly set up an Accel Platform development environment.

We provide two types of assets: one for running Accel Platform standalone, and one for running it in a cluster configuration. For the actual setup steps, see the README.md included in each published repository, or the bundled documentation.

Coding Agent Assets​

Added a Skill for REST APIs​

skill: jssp-im-oauth-generator You can now create REST APIs that use the OAuth provider feature (im_oauth).

Added a Skill for Creating Tenant Environment Setup Assets​

skill: jssp-tenant-setup-generator Tenant environment setup lets you create the assets needed to set up DDL, roles, authorization, menus, and the tenant environment. This skill makes it easy to create the assets your application needs to run.

You can create the following assets:

  • Role definition XML (base + per-language)
  • Authorization policy XML (subject format and effect)
  • Authorization resource and resource group XML (parent-group, uri)
  • Authorization subject group XML (sort-key, expression)
  • Minimal structure for menu group XML
  • Job and job net definition XML
  • The IM-Workflow import mechanism (workflowImport.files, the structure of the generated JS, and dependency ordering)
  • The IM-LogicDesigner import mechanism (logicImport.files, direct Java access via LogicFlowImporter)
  • DDL/DML

Note: The skill generates menus only for the "Site Map (PC)"; the global navigation is out of scope. To register an item in the global navigation, you must copy and place it from the menu management screen.

Improvements to the IMDS Design System Skill​

skill: jssp-imds-theme

We significantly expanded the skill content for the IMDS design system. We fixed an issue where the output varied too easily (added lint checks for tag and class structure). We added usage examples for components such as dialog (detail / form / select).

Expanded the Page Generation Skill​

skill: jssp-page-generator

We expanded the patterns used when creating pages.

  • Added templates for file upload and download.
  • Added a template for POSTing data in JSON format.
  • Added the relevant convention sections to reference.

skill: jssp-presentation-page.md

We expanded the rules for page generation.

  • A detailed table of id attribute naming conventions
  • Field naming for input elements
  • Error display, required elements, error display, buttons/dialogs/forms
  • Added anti-patterns for width adjustment

Improvements to the Workflow Skill​

skill: jssp-im-workflow-generator

  • Added validate-xsd.js, a script that validates XML encoding (BOM validation for UTF-16 LE/BE) when generating flow definition information.
  • Made pageType validation stricter.

Improvements to the IM-Common Master Skill​

skill: jssp-im-master-usage

  • Added "Application Policy" and "Conventions to Reference" sections.
  • Added an explanation of ARIA support for imACMSearch.

Improvements to Error Handling Conventions​

skill: jssp-error-handling.md

We improved the error handling conventions for REST API support.

  • Error code naming rules
  • HTTP status mapping table
  • Error response structure definition

Expanded the E2E Testing Skill​

skill: jssp-testing.md We added perspectives for verifying page transitions in E2E tests. Validating specific elements—such as a regular expression that includes the imart context path in the URL, toHaveTitle, and h1#page-title—prevents missed 404 errors. We also added a troubleshooting chapter that covers how to handle the implicit 127.0.0.1 proxy bypass caused by ERR_ABORTED and <base href>, missing Chromium native deps such as libglib-2.0.so.0, and Squid 503 errors. In addition, we added proxy configuration patterns for playwright.config.ts.

Added File Placement Rules​

skill: jssp-file-structure.md We added file placement rules.

  • Exception rules for pages that are not called through the routing table (pages invoked through the IM-Workflow engine use {feature}/workflow/{page-type}/index.js, handled by jssp-im-workflow-usage)
  • Added guidelines for the mapper attribute
  • With support for generating tenant environment setup assets, the storage location for DDL/DML has changed.
    • May 1: src/main/schema/
    • June 1: src/main/storage/system/products/import/basic/{feature}/{version}/

Updated Code Generation Conventions​

skill jssp-code-style.md

  • Added an applicability line and style conventions

README.md: We defined the priority of convention application (specifications first → conventions as a fallback) and applicability tags (🟢 always / 🟡 context-dependent / 🟠 business-requirement-dependent).

Added a Script​

bun run format

We added a script for formatting Java code and similar files. (It is used when Java implementation skills are added; it has no effect on code generation in the script development model.)

Added Node.js Compatibility​

We now support builds that use Node.js. We support the following package managers.

  • npm
  • yarn classic
  • pnpm

Added devDependencies: @playwright/test ^1.52.0, @types/node ^24.0.0

Minor Changes​

  • Renamed the jssp-job-generator skill to jssp-im-job-generator.