mendez-async-api

Design event-driven architectures with AsyncAPI specifications and channel-centric contracts.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/copyleftdev/sk1llz --skill mendez-async-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mendez-async-api
Source: https://github.com/copyleftdev/sk1llz/tree/main/domains/api-design/mendez
Command: npx skills add https://github.com/copyleftdev/sk1llz --skill mendez-async-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of designing and documenting asynchronous, event-driven systems, ensuring clarity, consistency, and maintainability by treating message contracts with the same rigor as REST APIs.

Core Features & Use Cases

  • Event-First Design: Promotes defining message contracts (AsyncAPI spec) before implementation.
  • Channel-Centric Architecture: Focuses on message channels and schemas for clear system design.
  • Protocol Agnosticism: Designs systems independent of underlying messaging protocols (Kafka, MQTT, etc.).
  • Schema Governance: Encourages schema reuse for data consistency.
  • Use Case: Building a real-time notification system for a ride-sharing app, ensuring that location updates, ride requests, and driver assignments are clearly defined, documented, and consistently handled across microservices.

Quick Start

Act as Fran Méndez and design an AsyncAPI 3.0 specification for a system that handles user sign-ups and login events, ensuring clear channel definitions and payload schemas.

Frequently Asked Questions about mendez-async-api

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

FAQPage Schema
How do I design event-driven architectures using AsyncAPI?

Designing event-driven architectures with AsyncAPI involves creating protocol-agnostic message contracts and channel-centric schemas before implementation, ensuring consistent data exchange across microservices and message brokers.

What is event-first design for asynchronous microservices?

Event-first design for asynchronous microservices prioritizes defining AsyncAPI message contracts and payload schemas before implementation, ensuring maintainability and consistency across event-driven systems.

Can I define protocol-agnostic message contracts for Kafka and MQTT?

Yes, AsyncAPI specifications define protocol-agnostic message contracts, allowing you to design event-driven systems independently of underlying messaging protocols like Kafka or MQTT while maintaining clear channel definitions.

How do I document pubsub message schemas for an IoT platform?

You document pubsub message schemas for an IoT platform by creating an AsyncAPI specification that defines channel-centric architectures and payload schemas, ensuring consistent event-driven communication across devices and microservices.

Does this approach work for building real-time notification systems?

Yes, this approach works for building real-time notification systems by using AsyncAPI to clearly define and document event channels and payload schemas, ensuring location updates and ride requests are consistently handled across microservices.