Laravel House Laravel Package

Adoption checklist that puts a Laravel project on the kanban board shipped with petar-spasic/laravel-house: prerequisites, `kanban:install`, the project's decisions archived and its open questions put on cards, a Claude Code restart with the lease takeover, the card-ready stack checked by `kanban doctor`, a first real card through the agent loop and the first publish. Also upgrades a board: consolidating several boards and a decisions board into one work board with epics on its cards (`fold-boards`), and judging which archived decisions become CLAUDE.md rules. Cases: an existing project whose decisions live in docs/decisions.md, a new project fresh from laravel-project-setup, a board on an older house version, and the separate kanban package. Use when the owner types /implement-kanban, to adopt the board or to upgrade it. Triggers — implement kanban, adopt the kanban board, upgrade the kanban board, fold-boards, an older board format, kanban:install, import-house-docs.

For a project on the kanban board (docs/kanban present, kanban:install run). The main session orchestrates: it cuts cohesive cards an agent finishes in one go, runs `vendor/bin/kanban run --until-attention` in the background (the routine in code: clones, Docker stacks, headless agents, the merge queue) and acts on what it hands back, and runs the owner's morning: the summary, every open question as a multiple choice, the answers recorded with `kanban answer`. Covers card sizing and folding, the question format, provisional decisions, wrapping up, recovery, the exact vendor/bin/kanban commands and exit codes, and filing package findings upstream. Use when asked to run or drive the board, cut or split work into cards, answer or record the owner's questions, do the morning, or wrap up. Triggers — kanban, board, run the board, kanban run, morning, questions, answer, cut cards, fold cards, kanban-planner, kanban-worker, kanban-evaluator, kanban-merger, merge queue, vendor/bin/kanban.

Tells the owner in plain words what is happening on the project's kanban board right now: whether the board is being driven, which cards are in progress and which agents run on them, where approved cards stand in the merge queue, what merged in the last 24 hours, what is blocked and why, how many questions wait for the owner, and what the agents spent. Read-only. Use when the owner asks what is up, how the board is doing, what the agents are doing, or types /kanban-status. Triggers — kanban status, board status, what's up, what are the agents doing, how far are we, kanban-status.

House hosting for a Laravel app in Docker in three images: local (Caddy + php-fpm + Xdebug + the Vite or SvelteKit dev server, bind-mounted source), agent (the same with Octane in place of php-fpm, no Xdebug: card and merge-queue stacks) and production (FrankenPHP + Octane, non-root), each running the web server, the scheduler and Horizon under supervisor next to Postgres and Redis. Ships the Dockerfiles, entrypoints, compose files, Caddyfiles and configs as templates rendered per module, plus the boot order, the queue timeout chain, worktree stacks from one compose, forced phpunit env and the traps behind a container that boots but serves nothing. Module references: Reverb, spa, tenancy database roles. Use when dockerizing a Laravel project, writing or debugging its Docker, compose or Caddy files, or filling the Hosting section of its CLAUDE.md. Triggers — Laravel Docker, docker-compose Laravel, Caddy Laravel, FrankenPHP, Octane deploy, Reverb deploy, adapter-node deploy, supervisord Laravel.

House rules for a Laravel project: the CLAUDE.md rule system (root + one per layer directory), Stripe-style prefixed ids, E2E tests only where a failure hurts (Pest, Playwright with spa; Boost's test guidance overridden), core auth in every app (Fortify, Socialite, Sanctum), the Horizon gate, the four-seeder standard, the PHP minor and host ports, plus modules chosen per project: Blade + htmx, Svelte islands, a SvelteKit SSR app (adapter-node) in frontend/, Reverb, row-level tenancy. Frontend, Socialite and tenancy ship as binding rules, not code. Also brings an existing house project onto the current core. Hands off to laravel-deployment and /implement-kanban. Use when starting a Laravel project, bringing one onto the house rules, or when the user types /laravel-project-setup. Triggers — new Laravel project, Laravel project setup, house rules, CLAUDE.md per layer, prefixed ids, Stripe-style ids, seeding standard, multi-tenancy, Socialite, Sanctum, adopt house core, validation:export.