Java Technical Solution Generator

Problem

Java backend design docs often lack a consistent structure: table relationships lack complete ER diagrams, API definitions contain only method signatures, and business flows or permission rules remain scattered. This skill constrains the output into an inspectable technical design document, focused on concrete engineering details rather than narrative project material.

Behavior and boundaries

It follows fixed sections: database design, architecture, data model, API design, core business flows, and permission configuration. By default it renders detailed Mermaid ER diagrams, orders fields by primary key, business fields, and standard fields, and marks constraints such as PK, FK, and UK. The API section covers Controller, Service, and Mapper methods, with a required // single-line comment before each method that states actions such as paginated query, detail query, export, or status filtering. The skill also enforces module boundaries: it expands only the current business module and does not generate external systems, upstream/downstream services, or cross-module collaboration sections. Use it for backend solution drafts, pre-review design notes, and schema preparation before migrations; avoid relying on it for static code scanning, test generation, or whole-system architecture planning.