About this skill

Problem Solved

Many Solon projects fail or behave inconsistently because developers copy Spring annotations, dependencies, and configuration names. This skill targets Java 8 to Java 26 development on Solon 4.0.3 and keeps Solon separate from Spring: use app.yml, Solon.start(App.class, args), @Component, @Inject, and org.noear coordinates while avoiding @RestController, @Autowired, and spring-boot-starter-* habits.

How It Works

It first maps the task to a scenario, then reads only 1 or 2 relevant references instead of loading all materials. Core coverage includes:
- Foundations: pom.xml, solon-maven-plugin, AOT/Native, REST, filters, and scheduled jobs
- Data and communication: SqlUtils, transactions, MyBatis, Nami RPC, and Socket.D
- AI scenarios: ChatModel, tools, basic RAG, MCP, agents, HarnessEngine, and ACP/A2A
- Cloud and flow: configuration center, service discovery, gateway, breaker, Flow YAML, Workflow, and interceptors
Before generating code, it checks critical rules, such as avoiding Spring dependencies and consulting references or source code for uncertain APIs.

Boundaries

It fits native Solon development, plugin SPI, security validation, testing, logging, and AI component design; complete Spring migrations should use a Spring-to-Solon companion skill. Do not invent missing coordinates such as solon-ai-rag or solon-ai-a2a; when upgrading versions, replace the target version globally and re-review AI, Nami, and shortcut dependency changes.