Help us improve
Share bugs, ideas, or general feedback.
From laravel-cloud
Deploys and manages Laravel apps on Laravel Cloud via cloud CLI. Manages environments, databases, caches, domains, instances, deployments, and infrastructure.
npx claudepluginhub laravel/agent-skills --plugin laravel-cloudHow this skill is triggered — by the user, by Claude, or both
Slash command
/laravel-cloud:deploying-laravel-cloudThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```sh
Covers Craft Cloud serverless hosting for Craft CMS: configuration, build-migrate-release pipeline, edge image transforms, static caching, plugin compatibility, and self-hosted migration.
Provides Laravel patterns for PHP apps including Eloquent ORM, migrations, routing, controllers, queues, jobs, authentication, middleware, and testing. Use for Laravel projects.
Design Laravel app architecture with services, repositories, actions, and clean code patterns. Use when structuring projects, creating services, implementing DI, or organizing code layers.
Share bugs, ideas, or general feedback.
composer global require laravel/cloud-cli
cloud auth -n
Commands follow a CRUD pattern: resource:list, resource:get, resource:create, resource:update, resource:delete.
Available resources: application, environment, instance, database-cluster, database, cache, bucket, domain, websocket-cluster, background-process, command, deployment.
Some resources have additional commands (e.g., domain:verify, database:open, instance:sizes, cache:types). Discover these via cloud -h.
Never hardcode command signatures. Always run cloud <command> -h to discover options at runtime.
Always add -n to every command — prevents the CLI from hanging.
Never use -q or --silent — they suppress all output.
Flag combos per operation:
:list, :get) → --json -n:create) → --json -n:update) → --json -n --force:delete) → -n --force (no --json)-n --force-n with all options passed explicitly (no --json)Determine the task and follow the matching path:
First deploy? → cloud ship -n (discover options via cloud ship -h)
Existing app? →
cloud repo:config
cloud deploy {app_name} {environment} -n --open
cloud deploy:monitor -n
Environment variables? → cloud environment:variables -n --force
Provision infrastructure? → cloud <resource>:create --json -n
Custom domain? → cloud domain:create --json -n then cloud domain:verify -n
For multi-step operations, see reference/checklists.md.
Not sure what the user needs? → ask them before running anything.
:list --json -n or :get --json -ncloud auth -nAlways run cloud deploy:monitor -n after every deploy. If it fails, show the user what went wrong before attempting a fix.
Delegate high-output operations to subagents (using the Task tool) to keep the main context window small. Only the summary comes back — verbose output stays in the subagent's context.
Delegate these to a subagent:
cloud deploy:monitor -n — deployment logs can be very longcloud deployment:get --json -n — full deployment detailscloud <resource>:list --json -n — listing many resources produces large JSONWebFetchKeep in the main context:
:create, :delete, :update — output is smallcloud deploy -n — you need the deployment ID immediatelyFollow exact steps:
Use your judgment:
~/.config/cloud/config.json — auth tokens and preferences.cloud/config.json — app and environment defaults (set by cloud repo:config)Laravel Cloud Docs: https://cloud.laravel.com/docs/llms.txt
When the user asks how something works or needs an explanation of a Laravel Cloud feature, fetch the docs from the URL above using WebFetch and use it to provide accurate answers.
cloud <command> -h for any command's optionscloud -h to discover commands