crud-api

Name: crud-api
Availability: InStock
Author: DriveConnect-alpha

Generate complete CRUD REST endpoints with layered architecture and multi-tenant PostgreSQL.

1|1|Updated Apr 25, 2026

Search Tags:#postgresql #backend #controller #crud #api-design #service-layer #multitenancy

Ready to run

npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill crud-api-driveconnect-alpha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: crud-api
Source: https://github.com/DriveConnect-alpha/DriveConnect/tree/main/.agent/skills/crud-api
Command: npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill crud-api-driveconnect-alpha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a ready-to-use CRUD API framework for the ReservAqui backend, enforcing a clean, layered architecture (Entity → Service → Controller → Routes) and multi-tenant PostgreSQL patterns to speed up API development and ensure consistency across resources.

Core Features & Use Cases

Layered architecture: Entity validations, service business logic, controllers, and routes stay decoupled for maintainability.
Multi-tenant PostgreSQL support: Master/global data and tenant-specific schemas are isolated per hotel or owner.
Wrapper pattern for services: Public wrappers delegate to private implementations to enable logging, caching, or metrics without changing core logic.
Security and auditing: Input validation, access guards, and soft delete patterns with audit fields.

Quick Start

Create a new CRUD resource by describing the resource name and fields; the Skill will generate the full backend scaffolding.

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 PostgreSQL isolation?▼

To build a CRUD API with multi-tenant PostgreSQL, use a layered architecture that separates master global data and tenant-specific schemas. This ensures safe tenant isolation and standardized error handling across your REST endpoints.

What is the layered architecture pattern for backend API design?▼

The layered architecture pattern for backend API design flows from Entity to Service to Controller to Routes. This approach keeps entity validations, business logic, and routing decoupled to maintain consistency and simplify modifications across API resources.

How do I generate REST endpoints with service layer wrappers?▼

You generate REST endpoints with service layer wrappers by defining a resource name and fields. The system then scaffolds the backend, applying public wrappers that delegate to private implementations to enable logging or caching without altering core logic.

Does this CRUD scaffolding handle soft delete and input validation?▼

Yes, this CRUD scaffolding handles soft delete and input validation. It integrates access security guards and soft delete patterns with audit fields directly into the generated code, ensuring safe and versioned data management across tenant schemas.

Can I use this CRUD API generator for hotel reservation systems?▼

You can use this CRUD API generator for hotel reservation systems like ReservAqui. It specifically enforces multi-tenant PostgreSQL patterns to isolate data per hotel or owner, speeding up API development for multi-tenant hospitality backends.

What's the best way to enforce tenant isolation in a PostgreSQL backend?▼

The best way to enforce tenant isolation in a PostgreSQL backend is by separating master and tenant-specific schemas. Applying standardized error handling and access guards across these schemas ensures data isolation per hotel or owner.