wf-laravel-create-package-method

Enforce explicit contracts and host adapters for decoupled Laravel packages.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill wf-laravel-create-package-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-laravel-create-package-method
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/wf-laravel-create-package-method
Command: npx skills add https://github.com/belluga/delphi-ai --skill wf-laravel-create-package-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel package development often suffers from tight coupling to host app internals. This skill defines a workflow to enforce explicit contracts, host adapters, and comprehensive documentation to ensure reusable, testable packages.

Core Features & Use Cases

  • Enforces contracts in src/Contracts and provides a clear host integration layer.
  • Generates or updates a package README with scope, data model, and integration guidance.
  • Applicable to new package creation and refactoring efforts that remove App\Http coupling and add host adapters for stability.

Quick Start

Initialize the decoupled Laravel package workflow and run architecture guardrails to validate contracts and adapters.

Frequently Asked Questions about wf-laravel-create-package-method

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

FAQPage Schema
How do I decouple a Laravel package from host application internals?

To decouple a Laravel package, enforce explicit contracts in src/Contracts and implement host adapters to define integration boundaries. This workflow ensures reusable, testable packages by isolating package logic from host app coupling.

What are architecture guardrails in Laravel package development?

Architecture guardrails validate that Laravel packages maintain explicit contracts and adapter boundaries. They run during the decoupled package workflow to ensure package code remains isolated from host application internals and adheres to structural requirements.

When should I refactor a Laravel package to use contracts and host adapters?

Refactor a Laravel package to use contracts and host adapters when removing App\Http coupling or preparing reusable package publication. This ensures stability by enforcing explicit boundaries between package logic and host integrations.

Does this Laravel decoupling workflow require specific package dependencies?

No specific package dependencies are required to implement this Laravel decoupling workflow. It focuses entirely on establishing structural requirements like src/Contracts, host adapters, and tests within your existing project architecture.

How do I generate a README with integration guidance for a decoupled Laravel package?

Generate or update a package README through this workflow to document scope, data models, and integration guidance. It creates formal architecture documentation required for publishing reusable Laravel packages with explicit boundaries.