Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/ForceInjection/domain-driven-design-skills --skill openapi-designEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Conduct deep academic research for philosophy, neuroscience, cognitive science, and theoretical computer science (computability, complexity, AI theory, logic). Use when user asks to: research academic topics, find scholarly papers, conduct literature reviews, analyze citations, synthesize research findings, explore philosophical arguments, investigate consciousness/cognition, study computability/decidability/Turing machines, or analyze academic debates. Triggers on: 'research papers', 'literature review', 'academic sources', 'scholarly articles', 'philosophy of mind', 'computability theory', 'neuroscience studies', 'find papers on', 'what does the research say'.
Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.
Add keyboard navigation to a feature using CommandRegistryService. Use when implementing keyboard shortcuts, vim-style navigation, or hotkeys for a page or component.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | openapi-design |
| description | Contract-first REST API design with OpenAPI 3.1 specification |
| allowed-tools | Read, Glob, Grep, Write, Edit, mcp__perplexity__search, mcp__context7__resolve-library-id, mcp__context7__query-docs |
Use this skill when:
Contract-first REST API design using OpenAPI 3.1 specification for consistent, well-documented APIs.
Before creating OpenAPI specifications:
docs-management skill for API design patternsRequirements → OpenAPI Spec → Review → Generate → Implement → Test
↑ ↓
←←←←←←←←←←←←← Iterate as needed ←←←←←←←←←←←←←←←←←←←←←←
openapi: 3.1.0
info:
title: Order Management API
description: |
API for managing customer orders in the e-commerce platform.
## Features
- Create and manage orders
- Track order status
- Process payments
version: 1.0.0
contact:
name: API Team
email: api-support@example.com
license:
name: MIT
url: https://opensource.org/licenses/MIT
servers:
- url: https://api.example.com/v1
description: Production
- url: https://api.staging.example.com/v1
description: Staging
- url: http://localhost:5000/v1
description: Development
tags:
-
paths:
/orders:
get:
operationId: listOrders
summary: List orders
description: Retrieve a paginated list of orders with optional filtering
tags:
- Orders
security:
- bearerAuth: []
parameters:
- $ref: '#/components/parameters/PageNumber'
- $ref: '#/components/parameters/PageSize'
- name: status
in: query
description: Filter by order status
schema:
$ref: '#/components/schemas/OrderStatus'
- name: customerId
in: query
description: Filter by customer ID
schema:
[]
[]
[]
[]
[]
components:
schemas:
# Enums
OrderStatus:
type: string
enum:
- draft
- submitted
- paid
- shipped
- delivered
- cancelled
description: Current status of the order
# Value Objects
Money:
type: object
required:
- amount
- currency
properties:
amount:
type: number
format: decimal
minimum: 0
example: 99.99
currency:
type: string
pattern: '^[A-Z]{3}$'
example: USD
# Entities
Order:
type: object
# Use camelCase for properties
customerId: string # ✓ Good
customer_id: string # ✗ Avoid
# Use plural for collections
/orders # ✓ Good
/order # ✗ Avoid
# Use nouns for resources
/orders # ✓ Good
/getOrders # ✗ Avoid
# Use kebab-case for multi-word paths
/line-items # ✓ Good
/lineItems # ✗ Avoid
| Method | Purpose | Idempotent | Safe |
|---|---|---|---|
| GET | Retrieve resource(s) | Yes | Yes |
| POST | Create resource | No | No |
| PUT | Replace resource | Yes | No |
| PATCH | Partial update | No* | No |
| DELETE | Remove resource | Yes | No |
| Code | Use For |
|---|---|
| 200 | Successful GET, PUT, PATCH |
| 201 | Successful POST (resource created) |
| 204 | Successful DELETE (no content) |
| 400 | Malformed request syntax |
| 401 | Authentication required |
| 403 | Authenticated but not authorized |
| 404 | Resource not found |
| 409 | Conflict (state transition, duplicate) |
| 422 | Validation error |
| 500 | Server error |
# URL Path (recommended for breaking changes)
servers:
- url: https://api.example.com/v1
# Header-based
parameters:
- name: API-Version
in: header
schema:
type: string
enum: ['2024-01-01', '2024-06-01']
# Use constraints
quantity:
type: integer
minimum: 1
maximum: 1000
email:
type: string
format: email
maxLength: 255
productCode:
type: string
pattern: '^[A-Z]{3}-\d{6}$'
# Use enums for known values
status:
type: string
enum: [draft, submitted, paid]
# Use nullable for optional fields (OpenAPI 3.1)
middleName:
type: ['string', 'null']
When designing OpenAPI contracts:
For detailed guidance:
Last Updated: 2025-12-26