api

Design and enforce REST and GraphQL API patterns with contract-first OpenAPI/SDL.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mrsknetwork/nemodev --skill api-mrsknetwork
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api
Source: https://github.com/mrsknetwork/nemodev/tree/main/skills/domains/references/api
Command: npx skills add https://github.com/mrsknetwork/nemodev --skill api-mrsknetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

API design and governance across teams is often inconsistent, leading to fragile integrations and security gaps. This skill provides a domain-first approach to choosing REST vs GraphQL, enforcing contract-first design, and standardizing security, validation, and versioning practices.

Core Features & Use Cases

  • Consistent API strategy: guidance on when to use REST vs GraphQL or tRPC based on complexity and client needs.
  • Production-grade patterns: contract-first OpenAPI/SDL, standard envelopes for responses, inclusive error handling, authentication, rate limiting, and versioning.
  • Real-world scenarios: building a multi-client API for web and mobile with secure authentication and smooth migration paths.

Quick Start

Ask me to evaluate REST or GraphQL for your project and implement a production-ready API following the recommended patterns.

Frequently Asked Questions about api

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

FAQPage Schema
How do I choose between REST and GraphQL for multi-client API environments?▼

Choosing between REST and GraphQL depends on client complexity and data needs. This skill provides domain-first guidance to evaluate your project and select the right API strategy for consistent multi-client environments.

How do I implement contract-first OpenAPI design for production APIs?▼

Implementing contract-first OpenAPI design involves defining standard response envelopes and error handling before coding. This skill enforces production-ready patterns to standardize validation and secure your API architecture.

What is the best way to standardize authentication and rate limiting across services?▼

Standardizing authentication and rate limiting requires applying dependency-based security patterns consistently. This skill enforces production-grade governance to manage access controls and protect services across your API.

How do I handle safe API versioning and smooth migration paths?▼

Handling safe API versioning requires enforcing standardized practices to prevent breaking existing integrations. This skill provides structured migration paths for evolving APIs without disrupting multi-client environments.

When do I need standardized response envelopes and inclusive error handling?▼

You need standardized response envelopes and inclusive error handling when building multi-client APIs to ensure predictable integrations. This skill applies contract-first design to satisfy OpenAPI/SDL requirements and standardize outputs.

Does this approach support tRPC and GraphQL SDL contracts?▼

Yes, this approach supports evaluating tRPC alongside REST and GraphQL based on client needs. It enforces contract-first design using OpenAPI and GraphQL SDL to standardize security, validation, and versioning.