Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
OpenAPI Spec Generation
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation…
Everything you need to author, generate, and validate OpenAPI 3.1 specifications that stay in sync with your code. It covers design-first specs, code-first generation from FastAPI and tsoa, and automated linting so your API contract becomes the single source of truth for docs, SDKs, mocks, and tests. No more drift between what the API says and what it does.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Contract first, code second. The skill produces and enforces the API contract in this exact loop, so SDKs, docs and tests all derive from one source:
- Decide the approach per project: design-first (spec written and agreed before code) for new APIs, code-first (FastAPI/Pydantic or tsoa decorators generating the spec) for existing services
- Write the spec skeleton: info with version and rate limit docs, server list (production, staging, local), tags, then every path with operationId, summary, parameters and examples
- Build the components layer for reuse: shared schemas referenced with $ref, common parameters (pagination, IDs), a single consistent Error schema with code, message, details and requestId used by every 4xx/5xx response
- Lock down security in the spec itself: bearerAuth and apiKey schemes defined, a security requirement on every endpoint, sensitive fields marked readOnly, rate limit headers documented on 429 responses
- Lint before anything ships: Spectral ruleset enforces operationIds, descriptions and naming conventions, Redocly validates examples and mime types, failures block the merge
- Generate the downstream artifacts from the validated spec: TypeScript, Python or Go clients via openapi-generator, bundled docs via Redocly, and version every breaking change with a new path prefix while keeping operationIds stable
One power source. 6 lines out.
openapi-spec-generation · core
core active · 6 lines
- ✓ writing an api contract
Writing an API contract before any code (design-first)
- ✓ generating a spec from e…
Generating a spec from existing FastAPI or Express code
- ✓ linting and validating an
Linting and validating an OpenAPI document
- ✓ generating client sdks in
Generating client SDKs in TypeScript, Python, or Go
- ✓ standing up swagger ui or
Standing up Swagger UI or Redoc documentation portals
- ✓ enforcing naming and sec…
Enforcing naming and security conventions across endpoints
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Eliminates drift by deriving SDKs, docs, and mocks from one canonical spec
license: perpetual -
Lets frontend and backend build in parallel against an agreed contract
license: perpetual -
Catches contract violations early with Spectral and Redocly linting in CI
license: perpetual -
Documents every error code and auth scheme so consumers integrate without guesswork
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
A full annotated OpenAPI 3.1 spec with schemas, parameters, responses, and examples
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
For backend and platform engineers who treat the API contract as a product and want spec, code, and docs to never disagree.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We run Express, not FastAPI, am I covered?
Partly by templates, fully by method. The ready code-first templates target Python/FastAPI and TypeScript/tsoa, and generating a spec from existing Express code is a supported use case; the design-first authoring, $ref patterns, and Spectral/Redocly linting are framework-agnostic.
-
How does it keep the spec from drifting away from the actual API?
By making the spec the single canonical source: SDKs, docs, and mocks are all derived from it, and Spectral plus Redocly rulesets run in CI to catch contract violations before merge. Drift stops being something you discover from angry API consumers.
-
Does it write the API implementation for me?
No. It produces the contract, lint rules, SDK generation commands, and documentation portals, the endpoint logic behind that contract is still your code. It also targets OpenAPI 3.1, so legacy Swagger 2.0 documents need upgrading first.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.