Agent skill · Backend & API

api-platform-crud

Create complete REST API CRUD operations using API Platform 4 with DDD and CQRS patterns. Use when adding new API resources, implementing CRUD endpoints, creating DTOs, configuring operations, or setting up state processors. Follows the repository's hexagonal architecture with YAML resource configuration and command bus pattern.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill api-platform-crud-vilnacrm-org-user-service-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/api/api-platform-crud-vilnacrm-org-user-service-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# API Platform CRUD Skill ## Context (Input) - Need to create new API resource with REST endpoints - Implementing CRUD operations (Create, Read, Update, Delete) - Adding DTOs for input/output transformation - Configuring API Platform operations, filters, or pagination - Working with state processors following CQRS pattern ## Task (Function) Implement production-ready REST API CRUD operations following DDD, CQRS, and hexagonal architecture patterns. **Success Criteria**: - All CRUD operations functional (POST, GET, PUT, PATCH, DELETE) - DTOs properly validated - Domain entities remain framework-agnostic - Command bus pattern used for write operations - `make ci` outputs "✅ CI checks successfully passed!" > Template examples reference MongoDB/Doctrine ODM. In this service, use Doctrine ORM with MySQL (`.orm.xml` mappings, `EntityManagerInterface`) while keeping the same layering and DTO/processor patterns. --- ## Quick Start: Complete CRUD in 10 Steps > **Full Implementation Example**: See [examples/complete-customer-crud.md](examples/complete-customer-crud.md) for detailed code. ### Step 1: Create Domain Entity Create pure PHP entity in `src/Core/{Context}/Domain/Entity/{Entity}.php

What's inside
Steps it walks through
  1. Context (Input)
  2. Task (Function)
  3. Quick Start: Complete CRUD in 10 Steps
  4. Step 1: Create Domain Entity
  5. Step 2: Create Doctrine XML Mapping
  6. Step 3: Create Input DTOs
  7. Step 4: Configure Validation
  8. Step 5: Create API Platform Resource Configuration
  9. Step 6: Configure Serialization Groups
  10. Step 7: Create State Processors
  11. Step 8: Create Command and Handler
  12. Step 9: Create Repository
  13. Step 10: Configure Filters (Optional)
  14. Architecture Flow
Ships with 1 file
  • metadata.json
Commands it runs
make generate-openapi-spec
Generates .github/openapi-spec/spec.yaml
Clear cache after config changes
make cache-clear
Generate OpenAPI spec
Validate architecture
make deptrac
Run E2E tests
make behat
Full CI check
More from claude-skill-registry
All skills →
About this skill
What does the api-platform-crud skill do?

Create complete REST API CRUD operations using API Platform 4 with DDD and CQRS patterns. Use when adding new API resources, implementing CRUD endpoints, creating DTOs, configuring operations, or setting up state processors. Follows the repository's hexagonal architecture with YAML resource configuration and command bus pattern.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill api-platform-crud-vilnacrm-org-user-service-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going