api-platform-crud

Generate API Platform 4 CRUD layers with DDD, CQRS, and hexagonal architecture from YAML.

5|Updated May 30, 2023
One-click install
npx skills add https://github.com/VilnaCRM-Org/core-service --skill api-platform-crud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-platform-crud
Source: https://github.com/VilnaCRM-Org/core-service/tree/main/.claude/skills/api-platform-crud
Command: npx skills add https://github.com/VilnaCRM-Org/core-service --skill api-platform-crud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to implement production-grade REST API CRUD layers for new resources using API Platform 4, aligned with DDD, CQRS, and hexagonal architecture, delivering clear separation of concerns and reproducible patterns.

Core Features & Use Cases

  • Schema-driven CRUD: Generate domain entities, DTOs, YAML resource configurations, processors, commands, and handlers following a hexagonal layout.
  • Config-first approach: Keep all API configuration in YAML to keep domain models framework-agnostic.
  • End-to-end lifecycle: Provides full Create, Read, Update, Delete operations with validation, input/output DTOs, and a Command Bus-based write path.
  • Use Case: When adding a new API resource, set up resource config, data validation, and CQRS handlers with minimal boilerplate.

Quick Start

Configure a new resource by following the 10-step guide to implement full API CRUD with CQRS and YAML configurations.

Frequently Asked Questions about api-platform-crud

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

FAQPage Schema
How do I generate CRUD operations in API Platform 4 using DDD and CQRS patterns?

Yes, you can keep API configuration in YAML to maintain framework-agnostic domain models. This config-first approach ensures DTO validation and resource definitions are managed externally, preserving clear separation of concerns in hexagonal architecture.

Do I need to manually create command handlers when setting up CQRS write paths for new API resources?

No, manual creation of command handlers is unnecessary. The Skill automates generating CQRS commands and handlers alongside processors, establishing a Command Bus-based write path for Create, Update, and Delete operations with minimal boilerplate.

Does API Platform 4 support hexagonal architecture for CRUD resource generation?

API Platform 4 supports hexagonal architecture when generating CRUD resources through this Skill. It separates domain, application, and infrastructure layers, keeping domain models framework-agnostic while providing deterministic processor-driven flows for all HTTP methods.

What are the limitations of YAML-based configuration for API Platform CRUD generation?

YAML-based CRUD generation requires strict adherence to the 10-step configuration process and works specifically within API Platform 4 projects using DDD, CQRS, and hexagonal architecture. Complex custom business logic beyond standard CRUD operations may need manual implementation.