Run any Skill in Manus with one click

server-standards

This skill focuses on backend architecture (Controller/Service/Repository), Prisma interaction, and standardized error/response middleware. Use it when building or modifying backend routes, controllers, or services.

Run Skill in Manus

Stars0

Forks0

UpdatedMarch 21, 2026 at 13:23

Source

TheGreatL

TheGreatL/tindahan

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

SKILL.md

readonly

name	server-standards
description	This skill focuses on backend architecture (Controller/Service/Repository), Prisma interaction, and standardized error/response middleware. Use it when building or modifying backend routes, controllers, or services.

Server Standards Skill

🎯 Purpose

This skill focuses on delivering a robust, scalable, and secure backend using the "Gold Standard" architecture.

🏗️ Core Responsibilities

Pattern Adherence: Enforce the Controller-Service-Repository pattern.
API Predictability: Ensure all responses use the ApiResponse utility and asyncHandler.
Database integrity: Manage Prisma schemas, migrations, and repository-level data access.
Security First: Implement rigorous validation (Zod), auth guards, and rate limiting.

📜 Key References

Server Architecture

🛡️ Backend Gold Standards

Security First:
- Use helmet for security headers.
- Implement rigorous CORS policies.
- Validate all inputs using Zod (Schema Validation).
- Prevent raw Prisma errors from leaking; use errorMiddleware.
API Design:
- Follow RESTful principles (standard HTTP verbs, status codes).
- Always return the unified ApiResponse format.
- Use asyncHandler to keep controllers clean and boilerplate-free.
Architecture:
- Strict adherence to Controller-Service-Repository pattern.
- Use HttpException for predictive, status-aware error throwing.
- Ensure all logic lives in Services, keeping Controllers and Repositories thin.
Data Processing (Pagination & Filtering):
- ALWAYS implement server-side pagination (offset/cursor), filtering (WHERE clauses), and sorting (ORDER BY) for list endpoints.
- NEVER return raw, unfiltered data dumps for the frontend to format. Validate and sanitize pagination parameters (page, limit) using Zod.
API Documentation:
- ALWAYS write Swagger JSDoc annotations (/** @openapi ... */) above new Routes/Controllers to ensure the /api/docs endpoint is automatically updated.
Industry Standards:
- Follow SOLID and DRY principles.
- Maintain structured logging for observability.
- Ensure all code is strictly typed with TypeScript.

More from this repository

same repository

architecture-standards

TheGreatL/tindahan

This skill enforces the strict directory structure and file naming conventions of the project. Use this whenever an agent is creating new files or folders to ensure consistency across the client and server.

2026-03-210

client-standards

TheGreatL/tindahan

This skill focuses on frontend tech stack (React, Vite, TanStack Router), Tailwind v4 aesthetics, and store patterns. Use it when building or modifying frontend components, routes, or stores.

2026-03-210

feature-development

TheGreatL/tindahan

This is the MASTER ORCHESTRATOR skill. Use this skill whenever building a new "feature", "module", "API endpoint", or "full-stack page". It strictly enforces a 4-step process that guarantees all code aligns with the project's Gold Standards.

2026-03-210

testing-standards

TheGreatL/tindahan

This skill enforces robust, scalable testing methodologies for both the frontend and backend. Use it when writing unit or integration tests, setting up testing frameworks like Vitest, or verifying that features conform to the "Gold Standard".

2026-03-210

Server Standards Skill

🎯 Purpose

This skill focuses on delivering a robust, scalable, and secure backend using the "Gold Standard" architecture.

🏗️ Core Responsibilities

Pattern Adherence: Enforce the Controller-Service-Repository pattern.

API Predictability: Ensure all responses use the ApiResponse utility and asyncHandler.

Database integrity: Manage Prisma schemas, migrations, and repository-level data access.

Security First: Implement rigorous validation (Zod), auth guards, and rate limiting.

📜 Key References

🛡️ Backend Gold Standards

Security First:

Use helmet for security headers.
Implement rigorous CORS policies.
Validate all inputs using Zod (Schema Validation).
Prevent raw Prisma errors from leaking; use errorMiddleware.

API Design:

Follow RESTful principles (standard HTTP verbs, status codes).
Always return the unified ApiResponse format.
Use asyncHandler to keep controllers clean and boilerplate-free.

Architecture:

Strict adherence to Controller-Service-Repository pattern.
Use HttpException for predictive, status-aware error throwing.
Ensure all logic lives in Services, keeping Controllers and Repositories thin.

Data Processing (Pagination & Filtering):

ALWAYS implement server-side pagination (offset/cursor), filtering (WHERE clauses), and sorting (ORDER BY) for list endpoints.
NEVER return raw, unfiltered data dumps for the frontend to format. Validate and sanitize pagination parameters (page, limit) using Zod.

API Documentation:

ALWAYS write Swagger JSDoc annotations (/** @openapi ... */) above new Routes/Controllers to ensure the /api/docs endpoint is automatically updated.

Industry Standards:

Follow SOLID and DRY principles.
Maintain structured logging for observability.
Ensure all code is strictly typed with TypeScript.