api-first-modular

Enforce API-First modular development with Frontend, Glue/BFF, and Backend API layers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hhx465453939/Claude_skill_pool --skill api-first-modular
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-first-modular
Source: https://github.com/hhx465453939/Claude_skill_pool/tree/main/skills.gemini/api-first-modular
Command: npx skills add https://github.com/hhx465453939/Claude_skill_pool --skill api-first-modular

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a strict API-First modular development methodology, ensuring clear separation between frontend, backend, and glue layers, making development, debugging, and maintenance significantly more efficient.

Core Features & Use Cases

  • Layered Architecture Enforcement: Guarantees adherence to a three-tier model (Frontend, Glue/BFF, Backend API Packages).
  • Standardized API Development: Mandates a 5-step process for backend API package creation, including implementation, testing, encapsulation, exposure, and documentation.
  • Automated Cross-Layer Task Decomposition: Provides a protocol for breaking down complex, multi-layer development or debugging tasks into ordered, manageable sub-tasks.
  • Use Case: When tasked with adding a new feature that involves both UI changes and new backend logic, this Skill will automatically break it down into distinct backend API development, API documentation, and frontend implementation tasks, ensuring each layer is developed and integrated correctly.

Quick Start

Use the api-first-modular skill to decompose the requirement "Implement a real-time notification system with SSE" into backend, documentation, and frontend sub-tasks.

Frequently Asked Questions about api-first-modular

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

FAQPage Schema
What is API-first modular development and how does it structure an application?

API-first modular development structures applications into distinct Frontend, Glue/BFF, and Backend API Package layers to enforce clear separation, making development, debugging, and maintenance more efficient.

How do I break down complex multi-layer feature tasks for frontend and backend development?

You can break down complex multi-layer tasks using an automated cross-layer decomposition protocol, which splits requirements into ordered sub-tasks for backend API development, documentation, and frontend implementation.

What is the standard process for creating backend API packages in a layered architecture?

The standard process for creating backend API packages mandates a 5-step lifecycle: implementation, testing, encapsulation, exposure, and documentation to ensure robust service creation.

When do I need a BFF layer in modular application architecture?

You need a BFF (Backend for Frontend) or Glue layer in modular architecture when enforcing API-first design to guarantee strict separation between frontend interfaces and backend API packages.

Can I use this approach to decompose real-time notification system features with SSE?

Yes, you can decompose a real-time notification system with SSE into distinct backend API development, API documentation, and frontend implementation sub-tasks to ensure each layer is integrated correctly.