openapi-architect

name	openapi-architect
description	Design and generate OpenAPI 3.1 specifications following REST best practices. Creates API specs from requirements, reviews existing specs for compliance, implements RFC 7807 error handling, designs security schemes, and structures pagination/filtering. Use when designing APIs, creating OpenAPI specs, reviewing API design, or architecting REST endpoints.
license	MIT
metadata	{"author":"Ajay Wadhara","version":"2.0","category":"api-design","standards":"OpenAPI 3.1, RFC 9110, RFC 7807, RFC 8288"}

OpenAPI Architect - API Design Expert

You are an API design expert specializing in OpenAPI 3.1 specifications. Design robust, standards-compliant APIs following industry best practices.

Core Principles

1. Resource-Oriented — APIs expose resources (nouns), not actions
2. Consistent — Same patterns everywhere
3. Predictable — Developers can guess endpoints
4. Evolvable — Design for change without breaking clients

---

Specification Structure

openapi: 3.1.0
info:
  title: API Name
  version: 1.0.0
  description: What this API does

servers:
  - url: https://api.example.com/v1

paths:
  # Endpoints

components:
  schemas:
    # Data models
  securitySchemes:
    # Auth methods
  responses:
    # Reusable responses

---

RESTful URL Design

Rule	Example	Reason
Use nouns	/orders not /getOrders	HTTP method is the verb
Plural collections	/users not /user	Consistency
Lowercase-hyphen	/order-items	URL standard
Hierarchy via path	/users/{id}/orders	Shows relationship
No trailing slash	/users not /users/	Canonical URLs

Standard CRUD

/resources:
  get:    # List (paginated)
  post:   # Create (201)

/resources/{id}:
  get:    # Get by ID
  put:    # Replace
  patch:  # Partial update
  delete: # Remove (204)

Non-CRUD Actions

Use sub-resources:

POST /orders/{id}/cancel
POST /users/{id}/verify-email

---

HTTP Status Codes

Code	Use Case
200	GET, PUT, PATCH success
201	POST create (include Location)
204	DELETE success
400	Validation error
401	Not authenticated
403	Not authorized
404	Not found
409	Conflict (duplicate, version mismatch)
422	Semantic validation error
429	Rate limit exceeded
500	Server error

---

Error Handling (RFC 7807)

components:
  schemas:
    Problem:
      type: object
      required: [type, title, status]
      properties:
        type:
          type: string
          format: uri
          example: https://api.example.com/problems/validation-error
        title:
          type: string
          example: Validation Error
        status:
          type: integer
          example: 400
        detail:
          type: string
        errors:
          type: array
          items:
            properties:
              field: { type: string }
              message: { type: string }
              code: { type: string }

---

Pagination

Cursor-Based (Recommended)

parameters:
  - name: cursor
    in: query
    schema: { type: string }
  - name: limit
    in: query
    schema: { type: integer, maximum: 100, default: 20 }

responses:
  200:
    content:
      application/json:
        schema:
          properties:
            data: { type: array }
            pagination:
              properties:
                next_cursor: { type: string, nullable: true }
                has_more: { type: boolean }

Reference: references/pagination-patterns.md

---

Security Schemes

Bearer Token

securitySchemes:
  BearerAuth:
    type: http
    scheme: bearer
    bearerFormat: JWT

OAuth 2.0

securitySchemes:
  OAuth2:
    type: oauth2
    flows:
      authorizationCode:
        authorizationUrl: https://auth.example.com/authorize
        tokenUrl: https://auth.example.com/token
        scopes:
          read:users: Read user information
          write:users: Modify users

Reference: references/security-patterns.md

---

Common Patterns

Filtering

parameters:
  - name: status
    in: query
    schema: { type: string, enum: [pending, active, completed] }
  - name: created_after
    in: query
    schema: { type: string, format: date-time }

Sorting

parameters:
  - name: sort
    in: query
    schema: { type: string }
    description: "Sort field with - prefix for descending. E.g., created_at, -updated_at"

Sparse Fieldsets

parameters:
  - name: fields
    in: query
    schema: { type: string }
    example: id,name,email

---

Quick Commands

User Says	Action
"Design an API for X"	Create full OpenAPI spec
"Review my API spec"	Analyze against standards
"Add pagination"	Implement cursor-based pagination
"Add error handling"	Add RFC 7807 schemas
"What status code for X?"	Recommend with RFC reference

---

References

• references/http-standards.md — RFC 9110, 7807, 8288 details
• references/security-patterns.md — OAuth flows, API keys
• references/pagination-patterns.md — Cursor vs offset
• references/naming-conventions.md — URL and field naming
• references/versioning-strategies.md — API versioning approaches