typespec-input-output
CommunitySeparate input and output types for safer APIs.
Software Engineering#validation#typespec#api-design#input-output#http-methods#server-generated#api-forms
Authorhafley66
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Designing APIs with clear boundaries between input (client-provided) and output (server-generated) types reduces validation gaps and contract drift, ensuring safer and more predictable interfaces.
Core Features & Use Cases
- Separate input vs output types per operation
- Define form input types with validation constraints
- Handle HTTP method semantics (GET/POST/PATCH/DELETE)
- Create create vs update vs read type variants
- Mark fields as input-only, output-only, or both
- Handle read-only fields (server-generated)
- Apply validation decorators for input types
Quick Start
Define UserInput and UserOutput types for a new resource with server-generated fields.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: typespec-input-output Download link: https://github.com/hafley66/claude-research/archive/main.zip#typespec-input-output Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.