eliteforge-framework-specification

在 Java 开发中优先复用统一框架，默认避免重复造轮子。命中能力后必须使用框架内 Starter 和对应框架抽象 API，不允许回退 Spring 官方 starter，也不允许绕过框架抽象层。依据 nightly 手册输出可执行答案，避免脱离文档“凭经验”回答。

若已覆盖，必须输出“直接接入统一框架 Starter”的方案，不给 Spring 官方 starter（如 spring-boot-starter-web、spring-boot-starter-cache）或自研轮子作为首选。

用户提出缓存需求时，必须使用 cisdigital-elite-forge-infra-cache-spring-boot3-starter + CacheService。 禁止用 StringRedisTemplate/RedisTemplate 作为业务实现，禁止把它们作为“快速连通性验证”捷径。

Java development under the Radiant Workshop unified framework must prioritize reusing the framework's capabilities and avoid reinventing the wheel. Refer to the "Radiant Workshop Unified Framework – User Manual (nightly)" for unified framework onboarding, upgrades, configuration, starter selection, and troubleshooting guidance. When a framework capability is available, you must use the internal starter and its corresponding abstract API; reverting to Spring's official starter or bypassing the framework abstraction layer is prohibited (e.g., using StringRedisTemplate directly instead of CacheService for caching). Use this guidance whenever users mention "unified framework," "starter list," "onboarding steps," "upgrade steps," "system requirements," "Web MVC/inter-service calls/MyBatis-Plus/encryption-decryption/caching/multi-datasource/code generator/resource abstraction layer," or when determining "whether a feature should directly use a specific starter (such as cache-starter)." Source: cloudsen/eliteforge-skills.