skills.rest
LiorCohen
LiorCohenCOMMUNITY
Explore all skills by this author →
GitHub

contract-standards

Define OpenAPI contract standards and generate TypeScript types from specs.

39|3|Updated Nov 21, 2025
Search Tags:#typescript#linting#openapi#code-generation#api-design#spectral#contract-standards
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill contract-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contract-standards
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/fullstack-typescript/skills/components/contract/contract-standards
Command: npx skills add https://github.com/LiorCohen/sdd --skill contract-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contract components establish a single source of truth for API definitions by standardizing OpenAPI contracts and the TypeScript types that consume them.

Core Features & Use Cases

  • Standardize API definitions with OpenAPI 3.0 YAML
  • Generate TypeScript types for server and web applications
  • Validate API consistency via Spectral linting
  • Enforce versioning and naming conventions across projects

Quick Start

Create an OpenAPI contract and generate its TypeScript types for immediate use in your API project.

Frequently Asked Questions about contract-standards

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

FAQPage Schema
How do I generate TypeScript types from an OpenAPI contract?▼

OpenAPI contract standards allow you to define API schemas in OpenAPI 3.0 YAML and apply a build-time workflow that generates standardized TypeScript types for immediate use across server and web applications.

What is the best way to enforce API consistency across multiple projects?▼

Establishing OpenAPI contracts as a single source of truth standardizes path naming, operation IDs, and schemas across server and front-end codebases, eliminating structural drift and ensuring API consistency across multiple projects.

Can I use Spectral linting to validate OpenAPI 3.0 YAML definitions?▼

Yes, you can use Spectral linting to validate OpenAPI 3.0 YAML definitions, enforcing versioning and naming conventions at build-time to ensure API consistency and schema validation before code generation.

How do Spectral linting rules work with OpenAPI contract standards?▼

Spectral linting works with OpenAPI contract standards by validating API consistency at build-time, checking OpenAPI 3.0 YAML definitions against enforced naming conventions and versioning rules before generating TypeScript types.

Do I need a single OpenAPI YAML file to standardize both server and front-end codebases?▼

You need an OpenAPI 3.0 YAML contract to standardize both server and front-end codebases, serving as the single source of truth for schemas, path naming, and generated TypeScript types applied across the stack.

Related Skills

Explore More Software Engineering Skills→
H2OSLabsH2OSLabs
1

schema-to-openapi

Converts Synnovator data schemas into OpenAPI 3.0 YAML or JSON specifications.

Official
Intermediate
ultramaxoAIultramaxoAI

typed-service-contracts

Enforce end-to-end type safety for frontend-backend API contracts with Zod and TypeScript.

Official
Advanced
gil00pitagil00pita

openapi

Generate OpenAPI 3.1 specifications and TypeScript types from API definitions.

Community
Advanced
michaelsvanbeekmichaelsvanbeek
1

api-design

Define REST API design patterns and contract standards for endpoints and OpenAPI documentation.

Community
Advanced