Menu
Use when writing or reviewing Java code involving Tongdun/Alibaba Java rules, exceptions, logging, SQL/MyBatis, security, middleware, concurrency, virtual threads, JVM JIT performance, or project layering.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.
Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.
Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.
Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.
Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.
Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.
Based on SOC occupation classification
| name | td-java-coding-guidelines |
| description | Use when writing or reviewing Java code involving Tongdun/Alibaba Java rules, exceptions, logging, SQL/MyBatis, security, middleware, concurrency, virtual threads, JVM JIT performance, or project layering. |
This skill provides Java coding guidance based on Alibaba Java Coding Guidelines.
Guideline severity has three levels:
Covers naming style, constants, code formatting, OOP rules, collections, concurrency, control statements, and comments.
Detailed rules: read references/programming-specification.md.
Covers exception handling and logging rules.
Detailed rules: read references/exception-and-logs.md.
Covers table design, indexes, SQL, and ORM mapping rules.
Detailed rules: read references/mysql-rules.md.
Covers application layering, second-party library dependencies, and server configuration.
Detailed rules: read references/project-specification.md.
Covers permission checks, data masking, SQL injection prevention, CSRF protection, and related security rules.
Detailed rules: read references/security-specification.md.
Covers dedicated rules for Dubbo, Kafka, ZooKeeper/Curator, InfluxDB, APEXDB, and HBase.
Detailed rules: read references/middleware-framework-specification.md.
Database transaction rules are included in the MySQL rules.
Detailed rules: read references/mysql-rules.md.
Covers pinning prevention, third-party library compatibility checks, ThreadLocal buffer hazards, thread-pool configuration, and virtual-thread-specific constraints.
Detailed rules: read references/virtual-thread-specification.md.
Covers HotSpot C2 / Graal JIT-friendly code for method inlining, escape analysis, scalar replacement, lock elimination/coarsening, devirtualization, loop optimization, bounds-check elimination, and branch prediction.
Detailed rules: read references/jvm-jit-performance-specification.md.
references/programming-specification.md.references/exception-and-logs.md.references/mysql-rules.md.references/project-specification.md.references/security-specification.md.references/middleware-framework-specification.md.references/mysql-rules.md and references/virtual-thread-specification.md.
ThreadLocal, per-thread buffers/caches, Aerospike-client, fastjson, legacy JDBC drivers, serialization clients, or other old blocking clients, apply the virtual-thread third-party compatibility checklist before writing code. Do not default to Executors.newVirtualThreadPerTaskExecutor() until the reference rules say it is safe.references/jvm-jit-performance-specification.md.