invoice-development

Implement provider-specific invoice adapters using TypeScript interfaces and testing patterns.

6|3|Updated Apr 8, 2022
One-click install
npx skills add https://github.com/Rytass/Utils --skill invoice-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: invoice-development
Source: https://github.com/Rytass/Utils/tree/main/.claude/skills/invoice-development
Command: npx skills add https://github.com/Rytass/Utils --skill invoice-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach for teams to implement provider-specific invoice adapters on top of the base @rytass/invoice package, standardizing interfaces and patterns to reduce duplication and risk.

Core Features & Use Cases

  • Reference base interfaces (Invoice, InvoiceGateway, InvoiceAllowance) and architecture patterns used by all adapters.
  • Document provider typings, gateway implementations, and testing strategies to streamline adapter creation.
  • Use Case: When adding a new provider, follow the guide to scaffold an adapter with consistent structure and behavior.

Quick Start

Install the base package and read the core references to begin scaffolding a new adapter; then consult the CREATE-ADAPTER.md for step-by-step scaffolding guidance.

Frequently Asked Questions about invoice-development

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

FAQPage Schema
How do I build a custom invoice gateway adapter in TypeScript?▼

To build an invoice gateway adapter in TypeScript, implement provider-specific logic on top of the base @rytass/invoice package by following standardized interfaces like InvoiceGateway and InvoiceAllowance to ensure safe, scalable integration.

What design patterns are used for invoice gateway architecture?▼

Invoice gateway architecture uses the adapter design pattern to standardize provider-specific implementations, relying on base entities like Invoice and InvoiceGateway to maintain consistent structure and behavior across different invoice providers.

Do I need the @rytass/invoice package to develop a new invoice adapter?▼

Yes, you need the @rytass/invoice package installed as a dependency before scaffolding a new invoice adapter, as it provides the required base TypeScript interfaces and core architectural patterns for development.

What's the best way to scaffold a new provider-specific invoice adapter?▼

The best way to scaffold an invoice adapter is to read the core base entity references, install the base package, and follow the step-by-step scaffolding guidance detailed in the CREATE-ADAPTER.md documentation.

How do I test provider typings for an invoice adapter implementation?▼

You test invoice adapter implementations by following the documented testing strategies and patterns specific to provider typings, ensuring your TypeScript gateway implementations behave safely and consistently before deployment.