project-architecture-standards

Enforce architecture standards and coding conventions for CPS project modules.

15|5|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/zhuangpengLI/AgenticCPS --skill project-architecture-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-architecture-standards
Source: https://github.com/zhuangpengLI/AgenticCPS/tree/main/.qoder/skills/project-architecture-standards
Command: npx skills add https://github.com/zhuangpengLI/AgenticCPS --skill project-architecture-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a formal set of architecture guidelines and coding standards for AgenticCPS projects, ensuring consistency across modules, services, adapters, and frontend components.

Core Features & Use Cases

  • Unified architecture: defines module layout, layering (Controller → Service → Mapper → DO), naming conventions, and multi-tenant/soft-delete rules.
  • Code generation templates: prescribes standard templates and fields for backend and frontend CRUD modules.
  • Quality and safety rules: includes error codes, validation, and MCP integration guidelines.
  • Adoption scenarios: when starting a CPS project, adding new modules, generating adapters, or enforcing conventions.

Quick Start

Describe your CPS module and request standardized architecture, naming conventions, and boilerplate code to apply the standards.

Frequently Asked Questions about project-architecture-standards

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

FAQPage Schema
What are project architecture standards for Java module creation and code generation?

Project architecture standards define module layout, Controller-Service-Mapper-DO layering, naming conventions, and validation rules to ensure consistency across generated Java modules and frontend artifacts.

How do I enforce coding conventions when generating service, controller, and mapper layers?

Apply standardized architecture guidelines to code generation by specifying concrete structure, naming, validation, and documentation rules that generated service, controller, and mapper classes must follow.

When do I need architecture standards for multi-tenant and soft-delete rules in my project?

You need architecture standards when starting a new CPS project, adding modules, or generating adapters to enforce multi-tenant and soft-delete rules consistently across services and database schemas.

Does this architecture standards tool work with frontend page generation and database schema design?

Yes, the architecture standards prescribe standard templates and fields for both backend CRUD modules and frontend page generation, alongside database schema design rules for consistency.

What's the best way to structure a new CPS module with adapter integration?

Describe your CPS module and request standardized architecture to apply predefined layout, layering, MCP integration guidelines, and boilerplate templates for adapters and components.