api-enrichment

Map UI fields to OpenAPI endpoints and generate TypeScript state models.

2|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/Eva813/skills-base --skill api-enrichment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-enrichment
Source: https://github.com/Eva813/skills-base/tree/main/.agents/skills/api-enrichment
Command: npx skills add https://github.com/Eva813/skills-base --skill api-enrichment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill fills missing API and data specifications after a Vue3 UI handoff so frontend engineers and logic-coders receive concrete endpoint mappings, request/response schemas, TypeScript state structures, mapping rules, and error handling guidance instead of ambiguous design notes.

Core Features & Use Cases

  • OpenAPI parsing: Extract relevant endpoints, request and response schemas, and error codes from provided OpenAPI/Swagger documents and map them to UI fields.
  • Data model inference: Produce candidate data models and TypeScript types when API documentation is absent, based on spec.md inferred fields and Figma-provided UI props.
  • State & mapping design: Generate Vue 3 + TypeScript state structures, view-model mapping functions, and composable-level error handling recipes ready for logic-coder implementation.
  • Deliverable: Produce an enriched-spec.md that aligns design, API, and frontend implementation expectations.

Quick Start

Generate an enriched-spec.md that maps UI fields from spec.md to OpenAPI endpoints or inferred data models and includes state structures, mapping logic, and error handling guidance.

Frequently Asked Questions about api-enrichment

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

FAQPage Schema
How do I map Vue3 UI fields to OpenAPI endpoints after a design handoff?

Mapping Vue3 UI fields to OpenAPI endpoints requires parsing the API document and correlating schemas with UI props. This skill extracts endpoints, request/response schemas, and error codes, producing an enriched specification document for frontend implementers.

What is the best way to generate TypeScript state structures from UI handoffs?

Generating TypeScript state structures from UI handoffs involves analyzing UI fields to infer data models. This skill produces Vue3 TypeScript state structures, view-model mapping functions, and composable-level error handling recipes for logic-coders.

Can I infer data models for frontend implementation if API documentation is missing?

You can infer data models for frontend implementation when API documentation is missing by analyzing spec.md inferred fields and UI props. This skill generates candidate data models and TypeScript types based on available UI handoff data.

How do I create an error handling plan for Vue3 API requests?

Creating an error handling plan for Vue3 API requests requires defining composable-level error handling recipes and mapping error codes. This skill extracts error codes from OpenAPI documents and integrates error handling rules into the enriched specification.

Does this approach work for filling missing request and response schemas from Figma UI props?

Yes, this approach works for filling missing request and response schemas by using Figma-provided UI props and spec.md inferred fields. It maps these UI elements to produce concrete request and response schemas within an enriched specification document.

What limitations exist when enriching API specs without Swagger documentation?

When enriching API specs without Swagger documentation, the limitation is that data models are inferred rather than definitively parsed. This skill generates candidate data models based on UI props, which may require validation against actual backend implementations.