java-dao

Generate standard Java DAO interfaces and MyBatis XML mappers for CRUD operations.

36|10|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jie023/trae-setting --skill java-dao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-dao
Source: https://github.com/jie023/trae-setting/tree/main/skills/java-dao
Command: npx skills add https://github.com/jie023/trae-setting --skill java-dao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes Java DAO layer templates, ensuring consistent interfaces, MyBatis XML mappings, and CRUD operation patterns across projects, reducing boilerplate and improving maintainability.

Core Features & Use Cases

  • DAO Interface & XML Template Guide: defines naming conventions, parameter annotations, and return types for all CRUD operations.
  • Consistency Across Projects: enables uniform DAO code and mapper definitions to speed development and reduce errors.
  • Use Case: when starting a new module, generate standard DAO interfaces and MyBatis XMLs for entities like AdminDepartment quickly.

Quick Start

Use the java-dao skill to scaffold standard DAO interfaces and MyBatis XML mappers for a new entity.

Frequently Asked Questions about java-dao

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Java DAO layer interfaces and MyBatis XML mappings?

Standardize Java DAO layers by applying consistent interface specifications, method naming conventions, parameter annotations, and MyBatis XML templates to ensure uniform CRUD operations and reduce boilerplate code across backend projects.

What is the best way to generate MyBatis XML mappers for new Java entities?

Generate MyBatis XML mappers for new Java entities by using predefined DAO templates that define standard CRUD patterns, return types, and parameter annotations, accelerating backend data access implementation while maintaining consistency across modules.

Why do I need a DAO layer standard for Java CRUD operations?

A DAO layer standard for Java CRUD operations is needed to enforce consistent interfaces and mapper definitions, which reduces development errors, minimizes boilerplate code, and improves the overall maintainability of backend data access modules.

Can I use this DAO template approach for existing Java projects with MyBatis?

You can apply this DAO template approach to existing Java projects with MyBatis to refactor and align interface specifications, method naming, and XML mappings with standard CRUD patterns, ensuring uniform data access implementation across the codebase.

What naming conventions and parameter annotations should MyBatis DAO methods follow?

MyBatis DAO methods should follow standardized naming conventions and use specific parameter annotations for all CRUD operations, ensuring consistent return types and uniform interface specifications across different modules and backend project implementations.