gateway-api-tasks

Update ApiClient wiring and gateway task definitions in Madoc TS.

57|15|Updated Nov 28, 2018
One-click install
npx skills add https://github.com/digirati-co-uk/madoc-platform --skill gateway-api-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gateway-api-tasks
Source: https://github.com/digirati-co-uk/madoc-platform/tree/main/.agents/skills/gateway-api-tasks
Command: npx skills add https://github.com/digirati-co-uk/madoc-platform --skill gateway-api-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need clear guidance to adjust the Madoc TypeScript ApiClient wiring and define or modify gateway task types without breaking integration.

Core Features & Use Cases

  • ApiClient Extension Wiring: Understand and update how extensions (pages, media, themes, etc.) are composed.
  • Gateway Task Definitions: Add new task types, modify payload structures, and align handlers.
  • Integration Consistency: Ensure changes work across server, browser, and queue worker contexts.

Quick Start

Use the gateway-api-tasks skill to explain the ApiClient extension wiring and show how to add a new gateway task type.

Frequently Asked Questions about gateway-api-tasks

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

FAQPage Schema
How do I add a new gateway task type in Madoc TypeScript?

To add a new gateway task type in Madoc TypeScript, you update the task definitions and align the task handlers within the services/madoc-ts codebase, ensuring payload structures adhere to existing BaseTask interfaces.

What is ApiClient extension wiring in Madoc and how does it work?

ApiClient extension wiring in Madoc governs how extensions like pages, media, and themes are composed and integrated, ensuring updates to the TypeScript client maintain consistency across server, browser, and queue worker contexts.

Do I need TypeScript knowledge to modify Madoc API client tasks?

Yes, modifying Madoc API client tasks requires knowledge of TypeScript and the Madoc project structure to ensure changes correctly adhere to existing ApiClient and BaseTask interfaces without breaking integration.

What's the best way to ensure integration consistency when updating Madoc task definitions?

The best way to ensure integration consistency when updating Madoc task definitions is to verify that handler adjustments and payload structures work seamlessly across server, browser, and queue worker contexts.

Why does modifying extension composition break the Madoc API client?

Modifying extension composition breaks the Madoc API client when changes fail to adhere to existing ApiClient and BaseTask interfaces, disrupting integration across server, browser, and queue worker environments.

Can I adjust task handler integration for queue workers in the Madoc TS codebase?

Yes, you can adjust task handler integration for queue workers in the Madoc TS codebase by updating gateway task definitions and ensuring payload structures align correctly across all execution contexts.