SuperAPI AI Directory

abc-backend-guide

Coding & development

View repository

Updated 10-15 08:12

About this skill

ABC Backend Development Guide

ABC Backend Development Standards Reference, covering common scenarios such as development, debugging, and operations.

Scenario Routing

Based on the user's intent, read the corresponding scenario file:

User Intent Scenario File Keywords
Backend Coding Standards and Fundamentals coding-guide.md Java, Spring Boot, annotations, Lombok, layered architecture, coding standards, Controller, Service, Entity, DTO, CRUD, create, read, update, delete
RPC Services (provide/call) rpc-guide.md RPC, Feign, microservice calls, inter-service communication, AbcServiceResponseBody
Database Table Schema Changes db-migration.md create table, add field, add index, alter table, database changes, DDL
Backend Issue Troubleshooting and Debugging debug-guide.md debugging, troubleshooting, error, traceId, SLS, distributed tracing
Logging Standards logging.md logs, log, logging, message-index, AbcLogMarker, @LogReqAndRsp
Exception Handling Standards exception.md exception, Exception, throw exception, error code, NotFoundException, CisCustomException
Starting the Backend Project local-dev.md start, run, port, local development, environment configuration, Gradle
Git Branch Management (General) Use abc-git-flow SKILL (if installed) branch, feature, hotfix, release, submit for testing, merge, canary
Git Branch Management (Backend-specific) backend-git-flow.md dev-join, dev-joint, test-join, test-joint, joint branch, backend release

Instructions

  1. First determine which scenario the user's intent belongs to
  2. Read the corresponding scenario file (multiple related files can be read at the same time)
  3. If the user's purpose is learning, explain concepts in plain and easy-to-understand language
  4. If the user's purpose is coding, generate code strictly according to the standards in the scenario file
  5. If the intent is unclear, first ask the user what they want to do, then route to the corresponding scenario
  6. Project-level differences: Each project can create a SKILL with the same name in .claude/skills/ to override or supplement this guide