producer-implementation
Producer implementation patterns for API operations and business logic
Browse published AI skills maintained by zerobias-org. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
58Repository stars across indexed skills
0Repository forks
112Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Producer implementation patterns for API operations and business logic
Agent orchestration protocol and coordination patterns
Client class responsibilities - connection ONLY, no business operations
TypeScript implementation standards, file organization, and code patterns
Connector wrapper (Impl) class patterns and delegation rules
Local memory storage patterns, file coordination, and cleanup
Connection profile and state schema design rules and core profile selection
Module export patterns including factory functions and public API design
Gate 3 validation: Implementation quality and type safety
Module scaffolding using Yeoman generator including validation and sync-meta
Gate 2 validation: TypeScript type generation from OpenAPI spec
Type mapping reference for OpenAPI formats to TypeScript core types
OpenAPI standards and guidelines for professional API specifications
HTTP client patterns for axios configuration, interceptors, and request handling
OpenAPI operation rules 11-13 for naming, pagination, and responses
Advanced OpenAPI schema patterns including allOf, naming hierarchies, and context separation
Core error types and HTTP status code mapping patterns
OpenAPI schema rules 14-24 for response models, nullable handling, and data modeling
OpenAPI core rules 1-10 covering servers, naming, parameters, and basic patterns
Agent invocation syntax and boundary rules
Agent parameter passing, memory files, and data handoffs between agents
Production readiness checklist before module release
Required tools and version requirements for module development
Immediate failure conditions that stop work
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.