add-provider

Add new AI providers to ClaudeBar using a test-driven workflow.

7|2|Updated Sep 28, 2022

Search Tags:#testing #architecture #TDD #integration #CLI #swift #provider

Ready to run

npx skills add https://github.com/kiminmonaco/ClaudeBar --skill add-provider

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-provider
Source: https://github.com/kiminmonaco/ClaudeBar/tree/main/.claude/skills/add-provider
Command: npx skills add https://github.com/kiminmonaco/ClaudeBar --skill add-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClaudeBar teams need a reliable blueprint to add new AI providers following a repeatable, test-driven workflow. This guide ensures consistent integration by outlining the necessary steps to implement parsing tests, probes, provider classes, and registration.

Core Features & Use Cases

Guided TDD workflow: outlines parsing tests, probe behavior, provider implementation, and registration.
Reusable architecture blueprint: shows how to structure tests, probes, and provider classes.
Reference patterns: includes file layout examples and architecture overview to copy for new providers.

Quick Start

Follow the four phases: parse tests, implement a probe, create the provider, and register it.

Frequently Asked Questions about add-provider

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

FAQPage Schema

How do I integrate a new AI provider using a test-driven approach?▼

To integrate a new AI provider using TDD, you follow a structured workflow: write parsing tests, implement a usage probe, create the provider class, and complete the provider registration across the app.

What is the test-driven workflow for adding AI providers to an architecture?▼

The TDD workflow for adding providers enforces a defined sequence including frontmatter creation, parsing tests, probe behavior implementation, provider class creation, and final registration to ensure consistent integration.

How do I structure usage probes and provider classes for AI integration?▼

You structure usage probes and provider classes by following a reusable architecture blueprint that defines file layouts, test patterns, and component wiring to correctly integrate new AI providers.

Do I need to write parsing tests before implementing an AI provider probe?▼

Yes, writing parsing tests is the first phase of the test-driven workflow, ensuring that the provider implementation and probe behavior match expected parsing outcomes before registration.

What's the best way to scaffold a new AI provider to ensure consistent integration?▼

The best way to scaffold a new AI provider is to use a guided TDD workflow that provides reference patterns and file layout examples, ensuring consistent integration across the app architecture.

Why does my AI provider registration fail without a defined architecture blueprint?▼

AI provider registration fails without a blueprint because the test-driven workflow requires completing all prior phases—parsing tests, probe implementation, and provider class creation—before registration can be validated.