coollabsio/coolify's Claude Code Plugin for Laravel Development

What Flowy indexed in coollabsio/coolify

Coolify is a self-hostable, open source alternative to Heroku, Netlify, and Vercel. Point it at your own servers and it deploys static sites, databases, and full stack applications, plus a large catalog of one click services. That is the product, and it is not what this guide is about.

Flowy's crawler found 12 components in the coollabsio/coolify repository: one MCP server and 11 skills, with no agents, commands, or hooks. Every one of the 11 skills is a Laravel development skill. None of them mention deploying an app, managing a server, or any of Coolify's own product features. If you came here expecting help running a Coolify instance through Claude Code, this bundle will not do that.

Why does a deployment platform ship Laravel skills?

Coolify's own codebase is written in PHP, built on the Laravel framework with Livewire for its interactive pages and Tailwind for styling, tested with Pest, and it depends directly on Laravel's Horizon, Fortify, Socialite, and Nightwatch packages. The skill set that its repository carries for Claude Code matches that stack almost package for package. Read this less as "Coolify's plugin" and more as the toolkit its own engineers keep next to the code they write every day, made public because the repository is public. Coolify has more than 61,000 stars on GitHub, so this is a working example of what a large, real Laravel application's own skill set looks like, not a demo built to fill out a listing.

What the 11 skills cover

Two handle who a user is. fortify-development activates for login, registration, password reset, email verification, two factor authentication, passkeys, and profile updates. socialite-development covers the OAuth side of the same problem: adding social login providers, configuring redirect and callback flows, and reading back the authenticated user's details.

Two cover background work and monitoring. configuring-horizon walks through Horizon's lifecycle, from installing it (horizon:install, Sail setup) to configuring supervisor blocks, queue assignments, and balancing strategies. configure-nightwatch is narrower: setting Nightwatch's data collection, sampling rates, filtering rules, and redaction policies, including protecting personal data before it is ever collected.

Two are for testing and debugging. pest-testing applies whenever a test is written, fixed, or refactored, including converting old PHPUnit suites to Pest and adding datasets. debugging-output-and-previewing-html-using-ray is for a more specific moment: sending data, debug output, or diagrams to the Ray desktop app instead of a log file.

Two cover conventions and reusable code. laravel-best-practices applies broadly, to controllers, models, migrations, form requests, policies, and Eloquent queries, and flags patterns like N+1 queries along the way. laravel-actions is narrower: building and refactoring action classes with the lorisleiva/laravel-actions package, and converting existing service classes or jobs into that shape.

Two cover the frontend. livewire-development triggers on Livewire itself, wire:model, wire:click, and building or debugging reactive components. tailwindcss-development triggers on any mention of Tailwind and covers responsive grids, dashboard layouts, and mobile navigation.

One is about building AI tools rather than app features: mcp-development is for creating MCP tools, resources, and servers inside a Laravel project, through Laravel's own generators and routing instead of a separate framework.

What about the laravel-boost MCP server?

The bundle's only MCP server, laravel-boost, carries no description in Flowy's index, so this guide will not guess at its tool list. What is verifiable is that it is the official Laravel Boost package: coollabsio/coolify depends on it directly and starts it as its own Laravel command rather than a standalone process. For the exact tools it exposes, check the listing page linked at the top of this guide, or the package's own documentation, before you build a workflow around it.

Who this plugin is actually for

Reach for it if you are contributing to Coolify's own codebase, or building a separate Laravel application with a similar shape (Livewire on the frontend, Pest for tests, Horizon for queues) and want a matching skill set. Skip it if you are looking for deployment help: nothing in these 11 skills or the one MCP server touches servers, containers, or Coolify's actual product surface. Flowy indexes this public repository; it does not own, host, or maintain any of these components, and the source and its license sit at the repository linked from the listing page.