producer-implementation

Automate Producer-based API operations with business logic separated from connection management.

6|Updated Feb 20, 2025
One-click install
npx skills add https://github.com/zerobias-org/module --skill producer-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: producer-implementation
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/producer-implementation
Command: npx skills add https://github.com/zerobias-org/module --skill producer-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a clear separation of concerns by placing all API business logic inside Producers, while the Client manages only connection concerns such as authentication and HTTP setup.

Core Features & Use Cases

  • All API operations (list, get, create, update, delete) are implemented in Producers.
  • Connection context is accessed exclusively through the Client, preventing leakage of base URLs or keys into producer methods.
  • Error handling is standardized via a shared handler (handleAxiosError) and consistent mapper patterns to produce typed outputs.

Quick Start

Implement a Producer-based workflow by moving all business logic into Producers and wiring them to a Client for connection management.

Frequently Asked Questions about producer-implementation

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

FAQPage Schema
How do I separate API business logic from connection management in TypeScript?

Producer patterns separate API business logic from connection management by implementing operations like list, get, create, update, and delete inside Producers, while the Client handles authentication and HTTP setup exclusively.

Can I access connection context such as base URLs directly inside a producer method?

No, connection context is accessed exclusively through the Client to prevent leakage of base URLs or keys into producer methods, ensuring strict separation of concerns between business logic and connection management.

What is the best way to standardize error handling across API producers and clients?

Standardize API error handling by using a shared handler like handleAxiosError and consistent mapper patterns to produce typed outputs across all producers and clients for consistent error responses.

How do I implement list, get, create, update, and delete operations using producer patterns?

Implement list, get, create, update, and delete operations by moving all business logic into Producers and wiring them to a Client for connection management, enforcing a strict separation of API concerns.

Why does my API client architecture mix business rules with authentication setup?

Mixing business rules with authentication setup occurs without producer patterns; enforcing all API business logic inside Producers while the Client manages only connection concerns solves this architectural issue.