laravel-playbook
v2.3.1The package author's playbook. Ecosystem-wide patterns for crafting, shipping, and sustaining pinnacle Laravel packages.
By Christian Attard1 GitHub starsUpdated 2 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 29 skill or MCP entries
- Source updated
- Aug 25, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install laravel-playbook@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/attac-t/the-foundryClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/laravel-playbook/.
Plugin files
├── .claude-plugin/plugin.json├── skills/craft-api/SKILL.md├── skills/craft-branding/SKILL.md├── skills/craft-ci/SKILL.md├── skills/craft-config/SKILL.md├── skills/craft-deprecation/SKILL.md├── skills/craft-docs/SKILL.md├── skills/craft-exception/SKILL.md├── skills/craft-extension-point/SKILL.md├── skills/craft-fake/SKILL.md├── skills/craft-generator/SKILL.md├── skills/craft-macro/SKILL.md├── skills/craft-middleware/SKILL.md├── skills/craft-package/SKILL.md├── skills/craft-provider/SKILL.md├── skills/craft-readme/SKILL.md├── skills/craft-release/SKILL.md├── skills/craft-test-suite/SKILL.md├── skills/craft-trait/SKILL.md├── skills/craft-view/SKILL.md├── skills/decide-agnostic/SKILL.md├── skills/decide-dependency/SKILL.md├── skills/decide-docs-site/SKILL.md├── skills/decide-extraction/SKILL.md├── skills/decide-facade/SKILL.md├── skills/decide-positioning/SKILL.md├── skills/decide-scope/SKILL.md├── skills/ground-dx/SKILL.md├── skills/ground-extensibility/SKILL.md└── skills/ground-playbook/SKILL.md
Included Skills29
Crafting API surfaces. Entry points, fluent builders, progressive disclosure.
Crafting package identity. Professional impressions from the first click.
Crafting a CI pipeline. Five workflows, zero manual gates.
Crafting a config file. The self-documenting contract between package and consumer.
Crafting deprecations. Sunset gracefully, remove confidently.
Crafting a documentation site. Progressive depth, not progressive confusion.
Crafting exceptions. Named constructors, contextual messages, one class per failure mode.
Crafting extension points. Making code flexible means fewer feature requests.
Crafting fakes. Let consumers test package interactions without touching internals.
Crafting generators. Artisan commands as onboarding UX.
Crafting macros. Runtime extension of Laravel core classes.
Crafting package middleware. The invisible gatekeepers that guard, transform, and decorate every request.
Crafting a package skeleton. The starting template for every Laravel package.
Crafting a service provider. The declarative heart of every Laravel package.
Crafting a README. The landing page for your package.
Crafting a release pipeline. One action, full pipeline.
Crafting a test suite. Zero to green in 60 seconds.
Crafting model traits. The trait-first integration pattern for Laravel packages.
Crafting package views. Blade components, view publishing, and the visual contract with your consumers.
When to build framework-agnostic. Core + bridge vs Laravel-only.
When to depend, suggest, vendor, or own. Dependency strategy for Laravel packages.
When to keep docs in README vs build a dedicated docs site. Documentation strategy.
When and how to extract application code into a standalone Laravel package. The extraction playbook.
When to use Facade vs Trait vs Static Factory vs Helper vs Manager. Five API entry point patterns.
How to evaluate the competitive landscape and position your package. Build it because it's better, not because you can.
When to keep a package small (micro) vs let it grow (macro). The scope spectrum.
The 7 DX dimensions. An evaluation framework for package quality.
Extensibility patterns. Flexible code means fewer feature requests.
Core philosophy. DX is the north star for every package decision.
Plugin manifests1
{
"name": "laravel-playbook",
"version": "2.3.1",
"description": "The package author's playbook. Ecosystem-wide patterns for crafting, shipping, and sustaining pinnacle Laravel packages.",
"author": {
"name": "Christian Attard",
"url": "https://github.com/attac-t"
},
"keywords": [
"laravel",
"package",
"open-source",
"dx",
"ecosystem"
],
"skills": "./skills/"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[laravel-playbook on Agent Plugins Marketplace](https://pluginsmp.com/plugins/laravel-playbook)