CtrlK
BlogDocsLog inGet started
Tessl Logo

nitinjain999/platform-skills

Production-grade platform engineering handbook — Kubernetes, Terraform, Flux CD, GitHub Actions, AWS, and more.

67

Quality

84%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

README.mdexamples/documentation/

Status: Stable

Documentation Examples

Reference implementations for OpenAPI 3.1 specifications with shared components, security schemes, and response definitions.

Examples

ExampleTypeDescription
openapi-spec/openapi.yamlOpenAPI 3.1Orders API — create, read, list orders with auth, pagination, error schemas

Quick Start

# Validate the spec with Redocly (recommended)
npx @redocly/cli lint openapi-spec/openapi.yaml

# Preview rendered documentation in browser
npx @redocly/cli preview-docs openapi-spec/openapi.yaml

# Generate HTML docs
npx @redocly/cli build-docs openapi-spec/openapi.yaml -o docs/

# Validate with Spectral (alternative linter)
npx @stoplight/spectral-cli lint openapi-spec/openapi.yaml

What the Orders API Spec Covers

SectionWhat it shows
infoVersion, contact, license metadata
serversEnvironment URLs (production, staging)
securityBearer token and API key schemes
pathsPOST /orders, GET /orders/{id}, GET /orders with pagination
components/schemasOrder, CreateOrderRequest, ErrorResponse, PaginatedResponse — reused across paths
components/responsesShared 400, 401, 404, 500 responses referenced by $ref
components/parametersShared page, limit, sort pagination parameters

Key Patterns

Shared error responses (avoid duplication)

# Define once in components
components:
  responses:
    NotFound:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: "#/components/schemas/ErrorResponse"

# Reference everywhere
paths:
  /orders/{id}:
    get:
      responses:
        "404":
          $ref: "#/components/responses/NotFound"

Pagination schema

components:
  schemas:
    PaginatedOrders:
      type: object
      required: [data, total, page, limit]
      properties:
        data:
          type: array
          items:
            $ref: "#/components/schemas/Order"
        total:
          type: integer
        page:
          type: integer
        limit:
          type: integer

Security scheme

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

Validate in CI

# .github/workflows/docs.yml
- name: Lint OpenAPI spec
  run: npx @redocly/cli lint openapi-spec/openapi.yaml --fail-on-warnings

Checklist

  • All paths have operationId, summary, and tags
  • All schemas use $ref for reusable types — no inline duplication
  • All error responses reference shared components/responses
  • Security schemes declared in components/securitySchemes and referenced in security
  • required fields listed explicitly on all request body schemas
  • Examples provided for request and response bodies
  • Spec passes @redocly/cli lint with zero errors

See Also

  • references/documentation.md — docstring styles (Google/NumPy/JSDoc), OpenAPI 3.1, doc sites (MkDocs/TypeDoc), developer guides
  • /platform-skills:document — generate docstrings, OpenAPI spec, doc site, or getting started guide

examples

documentation

BEFORE_AFTER.md

CHANGELOG.md

CODE_OF_CONDUCT.md

COMMANDS.md

CONTRIBUTING.md

EDITOR_INTEGRATIONS.md

GETTING_STARTED.md

HOW_IT_WORKS.md

install.sh

INSTALLATION.md

LAUNCH.md

PROMPTS.md

QUICKSTART.md

README.md

renovate.json

SECURITY.md

SKILL.md

tessl.json

tile.json