create-payment-adapter

Generate a Java Spring hexagonal adapter scaffold for a given PSP name.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill create-payment-adapter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-payment-adapter
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/commands/create-payment-adapter
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill create-payment-adapter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a ready-to-use hexagonal PSP adapter scaffold for a given PSP name, accelerating integration by eliminating boilerplate.

Core Features & Use Cases

  • Generates a complete file tree including the adapter, ports, service, configuration, and test stubs.
  • Provides a consistent, reusable structure for adding new PSPs with minimal manual setup.
  • Use Case: You need to add a new PSP like "adyen" or "stripe" and want a ready skeleton to implement API calls.

Quick Start

Provide the PSP name (e.g., adyen) to generate the adapter scaffold.

Frequently Asked Questions about create-payment-adapter

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

FAQPage Schema
How do I generate a Spring boilerplate for a new PSP integration?

To generate a Spring boilerplate for a PSP integration, provide the target PSP name to produce a standardized Java Spring-based project structure with adapters, ports, service, configuration, and tests.

What is a hexagonal adapter scaffold and when do I need one for payments?

A hexagonal adapter scaffold is a normalized project skeleton separating payment ports, adapters, and services. You need it when adding a new PSP like Adyen or Stripe to ensure consistent, reusable integration structures.

Can I use this to create a Java project structure for any PSP name?

Yes, you can create a Java project structure for any specified PSP name. The generator outputs a complete file tree including adapter, ports, service, configuration, and test stubs under a normalized library-psps skeleton.

What's the best way to automate PSP integration boilerplate setup in Java?

The best way to automate PSP integration boilerplate setup is using a generator that outputs a complete, ready-to-use hexagonal adapter scaffold, eliminating manual file creation and accelerating API implementation.

Does the generated PSP adapter include test stubs and configuration files?

Yes, the generated PSP adapter includes test stubs and configuration files. It produces a complete file tree encompassing adapters, ports, service definitions, configuration, and tests for immediate implementation.