extensions-completions

Register and parse completion sources for Madoc TS autocomplete extensions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Registers and coordinates multiple completion sources for Madoc TS, ensuring consistent autocomplete behavior across extensions and external integrations.

Core Features & Use Cases

  • Registration and execution of multiple completion sources
  • Parsing of completion requests (type, language, paging) and resolving sources
  • Manage external source integrations and backend wiring for autocomplete

Quick Start

Review the existing completion sources in services/madoc-ts/src/extensions/completions/sources/ and add new ones by registering them in the CompletionsExtension constructor.

Frequently Asked Questions about extensions-completions

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

FAQPage Schema
How do I add new autocomplete sources to a Madoc TS backend?

To add new autocomplete sources, register them directly in the CompletionsExtension constructor. This wires your custom sources into the backend integration, enabling consistent completion behavior across the Madoc TS platform.

How does parsing completion requests work in a TypeScript backend extension?

Parsing completion requests involves extracting parameters like type, language, and paging data. The extension resolves the appropriate registered source using these parsed parameters to return accurate autocomplete suggestions.

How do I integrate external completion sources with my TypeScript service?

External completion sources are integrated by managing backend wiring and utilizing integration hooks specified by the extension. This coordinates external connectivity with your existing TypeScript service architecture.

What is the best way to coordinate multiple autocomplete sources in a TypeScript application?

The best way to coordinate multiple autocomplete sources is to register and execute them through a centralized extension. This ensures consistent behavior by resolving requests and routing them to the correct registered source.

Can I use TypeScript to handle paged completion requests for external integrations?

Yes, TypeScript can handle paged completion requests by parsing the paging parameters during the request phase. The extension processes these parameters to fetch the correct page of results from external integrations.

Why are my custom autocomplete sources not showing up in Madoc TS?

Custom autocomplete sources will not appear if they are not properly registered in the CompletionsExtension constructor. Ensure your source registration satisfies the required parsing and wiring constraints within the Madoc TS backend.