Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

backend-audit

Étoiles1

Forks0

Mis à jour26 juin 2026 à 08:40

Run this skill when auditing backend code. Covers error message format, architecture boundaries, input validation, DI compliance, Prisma safety, test coverage, API contracts, and security.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

coji831

coji831/mandarin-vite-react-ts

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	backend-audit
description	Run this skill when auditing backend code. Covers error message format, architecture boundaries, input validation, DI compliance, Prisma safety, test coverage, API contracts, and security.
user-invocable	true

Backend Audit Skill

When to Use

After implementing a backend feature (self-audit by Backend Engineer)
During code review (Code Reviewer checking backend changes)
Before closing a story that touches API or database
Before running a Prisma migration

Always Check (in order of priority)

Error message format — do all controller error responses follow "Failed to {action} {resource}" pattern? Check backend-error-messages.instructions.md for details.
Architecture boundaries — any service importing from another service's internals? Any controller bypassing the service layer to call repositories directly?
Input validation — all endpoints validated at the controller boundary. No raw request body data passed directly to Prisma queries.
DI compliance — all service dependencies injected via constructor/factory. No internal instantiation (e.g., new Service() inside another service).
Prisma safety — any schema changes that could drop data? Migrations reviewed before applying? Never drop columns — use @map or additive migrations. See prisma-schema-changes.instructions.md.
Test coverage — new/modified business logic has corresponding unit tests (mocked deps) or integration tests (test DB). Coverage target >80% for business logic.
API contract — response shape matches what the frontend expects? Shared types in packages/shared-types/ updated?
Security — authentication/authorization checks on protected endpoints? Input sanitized against XSS? Rate limiting considered?

Output Format

Group findings by file path
For each: file, description, severity (HIGH/MEDIUM/LOW), suggested fix
End with summary: X violations found (Y high, Z medium)

Plus depuis ce dépôt

même dépôt

component-decomposition

coji831/mandarin-vite-react-ts

Use when: designing a new page or feature UI, deciding where to place a component, or choosing between creating new vs reusing existing components.

2026-06-261

frontend-audit

coji831/mandarin-vite-react-ts

Run this skill when auditing frontend code. Covers CSS tokens, shared component reuse, API client rules, barrel files, store placement, accessibility, responsiveness, memoization, timer edge cases, console leftovers, and wireframe alignment.

2026-06-261

add-instruction

coji831/mandarin-vite-react-ts

Extract a lesson from recent agent struggles and create a .instructions.md file to prevent recurrence. Use when: agent made a mistake, discovered a new convention, found a recurring issue pattern.

2026-06-261

prisma-migration

coji831/mandarin-vite-react-ts

Run Prisma schema changes safely after editing schema.prisma. Use when: editing schema.prisma, adding new models, changing columns, database migration.

2026-06-261

name	backend-audit
description	Run this skill when auditing backend code. Covers error message format, architecture boundaries, input validation, DI compliance, Prisma safety, test coverage, API contracts, and security.
user-invocable	true

Backend Audit Skill

When to Use

After implementing a backend feature (self-audit by Backend Engineer)
During code review (Code Reviewer checking backend changes)
Before closing a story that touches API or database
Before running a Prisma migration

Always Check (in order of priority)

Error message format — do all controller error responses follow "Failed to {action} {resource}" pattern? Check backend-error-messages.instructions.md for details.
Architecture boundaries — any service importing from another service's internals? Any controller bypassing the service layer to call repositories directly?
Input validation — all endpoints validated at the controller boundary. No raw request body data passed directly to Prisma queries.
DI compliance — all service dependencies injected via constructor/factory. No internal instantiation (e.g., new Service() inside another service).
Prisma safety — any schema changes that could drop data? Migrations reviewed before applying? Never drop columns — use @map or additive migrations. See prisma-schema-changes.instructions.md.
Test coverage — new/modified business logic has corresponding unit tests (mocked deps) or integration tests (test DB). Coverage target >80% for business logic.
API contract — response shape matches what the frontend expects? Shared types in packages/shared-types/ updated?
Security — authentication/authorization checks on protected endpoints? Input sanitized against XSS? Rate limiting considered?

Output Format

Group findings by file path
For each: file, description, severity (HIGH/MEDIUM/LOW), suggested fix
End with summary: X violations found (Y high, Z medium)