Skip to content
cccskills
FreePublished on GitHub

creating-integration

Add, change, or debug external API integrations, vendor SDK adapters, and bridges to legacy business workflows. Use when an Action or domain service needs an outer technical dependency.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

External and legacy integrations

Put concrete external adapters in App\Infrastructure\Integrations, grouped by provider when useful. Legacy workflow bridges may live in App\Infrastructure\Legacy. Keep HTTP clients, SDK objects, transport failures, and provider-specific payloads at this boundary; translate them into consumer concepts.

Connect the consumer

A consumer in Domain or Application cannot depend on a concrete Infrastructure class. This boundary is a concrete reason for a contract:

  • Application need: App\Application\<Capability>\Contracts.
  • Domain need: App\Domain\<Capability>\Contracts.
  • Implementation: Infrastructure.
  • Binding: a standard Laravel service provider.
// App\Application\Orders\Contracts\PaymentGateway
interface PaymentGateway
{
    public function refund(string $paymentReference, string $idempotencyKey): void;
}

// In a service provider's register() method:
$this->app->bind(
    \App\Application\Orders\Contracts\PaymentGateway::class,
    \App\Infrastructure\Integrations\Payments\ProviderPaymentGateway::class,
);

After OrderCancelled commits, a queued listener can invoke a refund Action that receives PaymentGateway. The adapter implements that interface and translates the provider response. Derive a stable idempotency key for a refund operation and use the provider's supported mechanism or an application deduplication strategy.

Do not inject SDK types into the contract or resolve concrete adapters from Actions through app(), strings, or custom facades. Do not create an interface for every helper inside Infrastructure.

Keep external calls outside database transactions where possible. A local rollback cannot reverse a remote refund; design retries and failure handling for the actual use case rather than treating the database transaction as distributed atomicity.

For migrated code using legacy business workflows, the same contract/adapter pattern applies. Direct Eloquent persistence is still allowed; it must not become a shortcut into legacy workflow orchestration.

Use events by default for asynchronous reactions. A scheduling contract is warranted only for a real infrastructure capability, not merely because a Job exists.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create, modify, or refactor application use cases into Laravel-native DDD Actions. Use for business operations such as placing or cancelling orders, extracting controller orchestration, and fixing use-case behavior.

The English summary is being prepared. Showing the original description.

maiobarbero/laravel-boost-ddd11Updated Sep 29, 2026

Create or change structured input for application use cases, including extracting HTTP request data for Actions invoked from controllers, jobs, or commands. Avoid DTOs for trivial scalar input.

The English summary is being prepared. Showing the original description.

maiobarbero/laravel-boost-ddd11Updated Sep 29, 2026

Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.

The English summary is being prepared. Showing the original description.

maiobarbero/laravel-boost-ddd11Updated Sep 29, 2026

Create, extend, or fix Eloquent business models and their state transitions. Use when moving business rules out of controllers or Actions, or explicitly migrating a model into a DDD capability.

The English summary is being prepared. Showing the original description.

maiobarbero/laravel-boost-ddd11Updated Sep 29, 2026

Create or refactor business calculations and rules spanning multiple domain objects when no single entity or value object naturally owns the behavior. Use when assessing a growing service class.

The English summary is being prepared. Showing the original description.

maiobarbero/laravel-boost-ddd11Updated Sep 29, 2026

Create or change immutable business values with meaningful invariants, equality, or behavior, such as order numbers and money. Use when primitive values obscure domain rules; avoid wrapping every scalar.

The English summary is being prepared. Showing the original description.

maiobarbero/laravel-boost-ddd11Updated Sep 29, 2026

See all skills by maiobarbero

Report a problem with this skill