api-design

Design REST APIs for Symfony backends with OpenAPI specifications and DTO-based contracts.

1|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/jakubciszak/family-plan --skill api-design-jakubciszak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/jakubciszak/family-plan/tree/main/.claude/skills/api-design
Command: npx skills add https://github.com/jakubciszak/family-plan --skill api-design-jakubciszak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers on designing clear REST API contracts for Symfony backends using OpenAPI and DTOs, reducing ambiguity and integration issues.

Core Features & Use Cases

  • OpenAPI/Swagger-driven API design for Symfony controllers, including request/response schemas, authentication patterns, and API documentation generation.
  • Model-driven DTOs and validation annotations to ensure strict API contracts.
  • Use Case: when adding a new endpoint under /api/tasks, define endpoints, data shapes, and security requirements before implementation.

Quick Start

Outline a new Symfony API endpoint with OpenAPI annotations and wire it to a controller as demonstrated, then generate the API docs.

Frequently Asked Questions about api-design

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

FAQPage Schema
How do I design REST API contracts for Symfony using OpenAPI?

Design REST API contracts for Symfony using OpenAPI by defining endpoints, request/response schemas, and authentication patterns before implementation. This approach uses DTO-based contracts and Symfony Validation annotations to reduce ambiguity and prevent integration issues.

What is the best way to document Symfony controllers with Swagger?

Document Symfony controllers with Swagger by applying OpenAPI annotations directly to your controllers and DTOs. This model-driven approach generates API documentation automatically while ensuring strict validation rules are enforced across your request and response schemas.

How do DTOs help define API endpoints in Symfony?

DTOs help define API endpoints in Symfony by acting as strict data contracts for requests and responses. When combined with Symfony Validation annotations, DTOs ensure that incoming and outgoing data shapes are explicitly documented and enforced via OpenAPI specifications.

Can I use OpenAPI annotations for Symfony authentication integration?

Yes, you can use OpenAPI annotations for Symfony authentication integration. The API design process includes defining security requirements and authentication patterns within your OpenAPI specifications to secure endpoints before writing the controller logic.

When should I define OpenAPI specifications for a new Symfony endpoint?

You should define OpenAPI specifications for a new Symfony endpoint before implementation. Outlining the data shapes, security requirements, and endpoint routes first establishes a clear contract, which reduces ambiguity and prevents downstream integration issues.