artisan-build

Stand up a self-hosted Hone telemetry instance on Laravel Cloud with the `cloud` CLI. Gathers expected volume as a small/medium/large tier, recommends and — only after confirmation — provisions the matching resources (Postgres, Redis, a web instance, a managed queue, the scheduler), wires HONE_* config, deploys, migrates, and issues the first source-app token. Use when the user wants to deploy, set up, or provision a Hone instance / server / environment on Laravel Cloud, stand up Hone telemetry infrastructure, or onboard a new client's Hone environment.

Configure a Laravel app to send its laravel/nightwatch telemetry to a self-hosted Hone instance via artisan-build/hone-client. Use when enabling/installing/wiring Hone telemetry in a source app, pointing an app at a Hone ingest URL, running hone:install, or troubleshooting why telemetry isn't reaching Hone. Triggers on 'send telemetry to Hone', 'enable Hone in this app', 'install hone-client', 'configure the Hone client', 'point this app at our Hone server'.

Deploy, provision, set up, or stand up a self-hosted Sink mail-capture instance on Laravel Cloud with the `cloud` CLI. Gathers expected mail volume as a small/medium/large tier, recommends and only after confirmation provisions the matching isolated environment resources (Postgres, Redis, object-storage bucket, web instance, managed queue, scheduler), wires SINK_* config, deploys, migrates, runs create-admin, and issues the first source-app token. Use when the user wants to deploy, provision, set up, or stand up a Sink server / instance / environment on Laravel Cloud, fork-and-deploy Sink for a client, or onboard a new client's Sink environment.

Configure a Laravel app to capture outbound mail in a self-hosted Sink instance via artisan-build/sink-client. Use when installing, enabling, wiring, or troubleshooting Sink mail capture in a source app, pointing an app at a Sink server, running sink:install, setting MAIL_MAILER=sink, or verifying test mail arrived in Sink.

Method for provisioning Laravel Cloud environments + resources and enabling deployments safely. THE CARDINAL RULE: never set environment variables for Cloud-provisioned resources — Cloud auto-injects ALL resource config (credentials AND connection selectors like QUEUE_CONNECTION/DB_CONNECTION/CACHE_STORE) into a separate managed env file the app reads; any value you set yourself overwrites/shadows the injected one and breaks the resource (and is easy to get wrong). Use whenever asked to create/provision a Cloud environment, attach resources (DB/Redis/queue/object storage), or restore/enable deploys. Requires the project's .cloud repo config (cloud repo:config) bound first.

Orchestrate building a planned, multi-PR feature (or a greenfield MVP from a PRD) with a coordinated subagent loop: one agent implements each PR, independent agents review and judge it, and the agent running THIS skill is the coordinator that verifies the gate, arbitrates findings, and ships each PR. Trigger when the user (or the brain orchestrator) hands over a planning scratchpad / PRD and asks to build it via the multi-agent / coordinated workflow ('orchestrate this', 'have the agents build it', 'run the loop'). Each PR runs implement -> hard gate -> independent quality review + acceptance judge -> coordinator arbitration -> ship, with a 3-attempt cap. Two modes: A (autonomous, merge each PR on green CI) and B (open PR, human merges, then continue). Do NOT use for single-file edits, quick fixes, refactors, bugs, or maintenance — this spawns multiple agents and burns real tokens; it is only for substantial, plan-driven feature builds explicitly opted into. Requires Solo and a per-project .solo/workflow.md p

Deploy a self-hosted Matte background-removal instance to Laravel Cloud with the `cloud` CLI. Guides the one-time interactive bootstrap (`cloud ship` + `cloud repo:config`), then provisions the rest mostly non-interactively: attaches a Postgres database, sets the build command that bakes the bg-remover binary into the deploy artifact, wires the object-storage bucket, the managed queue, env vars, deploys, migrates, and issues the first API token. Use when the user wants to deploy, set up, provision, or stand up a Matte server / instance / environment on Laravel Cloud, or fork-and-deploy Matte for a client.