proj-common

Provides unified Spring Boot project guidelines and reusable components for common infrastructure.

93|27|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/zhangloveyan/backend-skill --skill proj-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proj-common
Source: https://github.com/zhangloveyan/backend-skill/tree/main/.claude/skills/proj-common
Command: npx skills add https://github.com/zhangloveyan/backend-skill --skill proj-common

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The proj-common skill consolidates common backend patterns and utilities to ensure consistent API design, error handling, and operational practices across services.

Core Features & Use Cases

  • R response wrapper for unified API responses
  • ErrorCode enum for standardized error reporting
  • BusinessException and GlobalExceptionHandler for centralized error handling
  • Transaction and caching guidelines to ensure data integrity and performance
  • Logging conventions and AssertUtils for robust validation
  • Redis utilities and keys, LoginUserHolder for session/user context
  • Documentation references and examples to accelerate onboarding across teams

Quick Start

Import and apply the proj-common guidelines into your Spring Boot project; start by using R for responses, ErrorCode for errors, and following the transaction and caching conventions.

Frequently Asked Questions about proj-common

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

FAQPage Schema
How do I standardize API response handling and error codes in a Spring Boot project?

Standardize API responses in Spring Boot by applying a unified R response wrapper and an ErrorCode enum. This ensures consistent API design and standardized error reporting across all backend modules.

What is the best way to centralize exception handling for backend services?

Centralize exception handling for backend services by implementing a GlobalExceptionHandler alongside a custom BusinessException. This captures errors uniformly, preventing scattered try-catch blocks and ensuring safe operation.

How do I manage Redis caching and user context safely across backend modules?

Manage Redis caching and user context safely by utilizing provided Redis utilities, standardized Redis keys, and a LoginUserHolder. This enforces consistent behavior for session data and caching across modules.

Can I use this backend standardization approach for my existing Java Spring Boot microservices?

Yes, you can apply this to existing Java Spring Boot microservices. Import the guidelines to enforce consistent transaction handling, logging conventions, and validation utilities across your current architecture.

Why do I need unified transaction and logging conventions for backend development?

Unified transaction and logging conventions are needed to ensure data integrity and operational consistency. Standardized guidelines prevent data corruption and make backend system monitoring and debugging reliable.

When should I not use AssertUtils for backend validation?

Avoid using AssertUtils for backend validation when handling complex business rule validations that require multi-step conditional logic. It is designed for robust, straightforward precondition checks rather than intricate workflows.