crud-api

Generate CRUD API layers with entity validation and multi-tenant schema support.

8|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo --skill crud-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crud-api
Source: https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo/tree/main/.agent/skills/crud-api
Command: npx skills add https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo --skill crud-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement a scalable, standardized CRUD API layer for the ReservAqui backend, enforcing layered architecture, multi-tenant isolation, and strict input validation to simplify resource management across master and tenant schemas.

Core Features & Use Cases

  • Entity → Service → Controller → Routes pattern with clear responsibilities, validators, and safe data exposure.
  • Multi-tenant isolation using withTenant(schema, fn) to ensure schema-scoped operations.
  • Soft delete support and audit fields for traceability and compliance.
  • Use case: add a new resource to the master DB or a tenant schema, then expose a full suite of REST endpoints.

Quick Start

Create a complete CRUD resource by defining its entity, service, controller, and routes following the project’s multi-tenant architecture.

Frequently Asked Questions about crud-api

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

FAQPage Schema
How do I build a CRUD API with multi-tenant schema isolation in Express and TypeScript?

To build a multi-tenant CRUD API, this Skill uses an Entity, Service, Controller, and Routes pattern with a `withTenant(schema, fn)` wrapper to enforce schema-scoped operations and tenant isolation in PostgreSQL.

What is the best way to structure a multi-tenant backend API for adding new resources?

The best way to structure a multi-tenant backend API is using layered architecture with clear responsibilities, validators, and safe data exposure, separating Entity, Service, Controller, and Route definitions across master and tenant schemas.

How does soft delete work with PostgreSQL in a multi-tenant CRUD API?

Soft delete in a multi-tenant CRUD API works by retaining records with audit fields for traceability and compliance instead of permanently removing them, ensuring schema-scoped operations maintain data integrity across tenant schemas.

Can I enforce input validation and standardized error handling across master and tenant schemas?

Yes, you can enforce input validation and standardized error handling across master and tenant schemas, including parameterized queries and consistent Portuguese error messages to secure and manage your multi-tenant CRUD API layer.

Do I need to configure PostgreSQL schemas before creating a multi-tenant CRUD API layer?

Yes, you need PostgreSQL schemas configured for master and tenant isolation, as the CRUD API layer relies on `withTenant(schema, fn)` to execute parameterized queries within specific tenant schema scopes.

Why does my multi-tenant CRUD API need layered architecture with separate Service and Controller mappings?

A multi-tenant CRUD API needs layered architecture with separate Service and Controller mappings to orchestrate business logic, enforce input validation, support soft deletes, and expose REST endpoints safely across isolated tenant schemas.