create-provider-claude

Scaffold provider interfaces and fake/real implementations under src/Plugins/Providers.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/dezverev/AnimalAL-v1 --skill create-provider-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-provider-claude
Source: https://github.com/dezverev/AnimalAL-v1/tree/main/.claude/skills/create-provider-claude
Command: npx skills add https://github.com/dezverev/AnimalAL-v1 --skill create-provider-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of provider interfaces and corresponding fake/real implementations for plugin data sources, reducing boilerplate and ensuring consistent design across domains.

Core Features & Use Cases

  • Interface scaffolding: Generates I[Feature]DataProvider interfaces following project naming conventions.
  • Fake/Real implementations: Creates Fake[Feature]DataProvider and Real[Feature]DataProvider templates to support testing and production use.
  • Plugin integration: Places artifacts under src/Plugins/Providers and wires them into plugin constructors for seamless switching.

Quick Start

Create a provider pattern for Weather data sources by generating IWeatherDataProvider interface and FakeWeatherDataProvider and RealWeatherDataProvider implementations under the Providers folder.

Frequently Asked Questions about create-provider-claude

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

FAQPage Schema
How do I scaffold a provider pattern interface with fake and real implementations in C#?

Scaffolding a provider pattern in C# generates an I[Feature]DataProvider interface alongside Fake[Feature]DataProvider and Real[Feature]DataProvider templates. This Skill automates that boilerplate, placing files under src/Plugins/Providers and enforcing naming conventions for immediate integration.

What is a fake provider used for when generating plugin data source layers?

A fake provider provides mock data for testing scenarios without hitting actual external sources. This Skill generates a Fake[Feature]DataProvider template alongside the real implementation, allowing you to switch between mock and live data based on configuration.

Can I wire generated provider interfaces into existing C# plugin classes?

Yes, generated provider interfaces and implementations wire directly into existing plugin classes. This Skill handles constructor wiring under src/Plugins/Providers, enabling seamless dependency injection and configuration-based switching between fake and real providers.

What's the best way to auto-generate C# data layer boilerplate for plugin data sources?

Auto-generating C# data layer boilerplate is handled by scaffolding the provider pattern automatically. This Skill creates the interface and both fake and real implementations, reducing manual coding errors and ensuring consistent design across all plugin domains.

Does this provider scaffolding enforce specific file layout and naming conventions?

Yes, provider scaffolding enforces strict file layout and naming conventions. Generated artifacts like I[Feature]DataProvider and its implementations are automatically placed under the src/Plugins/Providers directory, ensuring structural consistency across the project.

How do I switch between a fake provider and a real provider based on configuration?

Switching between fake and real providers is managed through optional wiring rules driven by configuration. This Skill sets up the generated implementations to support seamless toggling, enabling test environments to use fake data while production uses real data.