Laravel + Livewire + PostgreSQL

Curated rule SaaS / Web App · DevOps & Infrastructure Updated Oct 2026 Which file does my tool read?

Production guidelines for Laravel 13 monoliths, Livewire reactive components, Eloquent ORM query discipline, and queued job workers.

Laravel Livewire PHP PostgreSQL Alpine.js Tailwind CSS

Formats: 4 files
AGENTS.md: 38 lines
CLAUDE.md: 16 lines
Languages: PHP
Updated: Oct 2026
Used by: 3 projects

Install

Writes .claude/skills/laravel-livewire-postgres/SKILL.md

$ curl -s --create-dirs -o .claude/skills/laravel-livewire-postgres/SKILL.md https://stackitfast.com/rules/laravel-livewire-postgres/SKILL.md

Rule files

AGENTS.md· 38 lines · 3.5 KB

1	# Project Architecture & Guidelines (Laravel + Livewire + PostgreSQL)
2
3	## 1. System Architecture
4	- Framework: Laravel 13 (PHP 8.3+), server-rendered monolith with Livewire for reactive UI components without a separate JS frontend build.
5	- Database & ORM: PostgreSQL with Eloquent ORM; migrations in `database/migrations/`. Coolify (below) self-hosts its own Postgres because it's a self-hosted PaaS by design — for a typical Laravel app, a managed provider (Supabase, Neon, or your cloud's RDS) is usually the easier default unless you specifically want to self-host.
6	- Interactivity: Livewire components (`app/Livewire/`) for dynamic UI; Alpine.js for lightweight client-side behavior Livewire doesn't cover.
7	- Styling: Tailwind CSS compiled via Vite.
8
9	## 2. Eloquent Query Discipline (Critical N+1 Prevention)
10	- Always eager-load relationships accessed in a loop or a Blade/Livewire view: `Project::with('owner', 'tags')->get()`, never `Project::all()` followed by `$project->owner` inside a `@foreach`.
11	- Enable `Model::preventLazyLoading()` in `AppServiceProvider::boot()` for local/testing environments so N+1 queries throw instead of silently degrading production performance.
12	- Use query scopes (`scopeActive()`, `scopePublished()`) on models instead of repeating `->where(...)` chains across controllers and Livewire components.
13
14	## 3. Livewire Component Conventions
15	- One Livewire component per cohesive UI concern (e.g. `ProjectTable`, `ProjectForm`) — avoid a single mega-component handling an entire page.
16	- Validate all public properties with Laravel's `#[Validate]` attribute or `rules()` method before persisting; never trust a Livewire property bound via `wire:model` without server-side validation.
17	- Use `wire:loading` and `wire:target` for loading states instead of hand-rolled JavaScript spinners.
18
19	## 4. Queued Jobs & Background Work
20	- Anything that calls an external API, sends email, or processes a file goes through a queued Job (`php artisan make:job`), never inline in a controller or Livewire action.
21	- Configure a real queue driver (`database` for small deployments, Redis for higher throughput) — never `sync` in production.
22	- Run `php artisan queue:work` under a process supervisor (Supervisor, systemd, or Laravel Horizon for Redis queues) so failed workers restart automatically.
23
24	## 5. Common Pitfalls / Coding Standards
25	- ❌ Running Eloquent queries inside Blade templates or Livewire render methods without eager loading.
26	- ❌ Trusting `wire:model`-bound properties without server-side validation rules.
27	- ✅ Use Form Request classes (`php artisan make:request`) for controller-level validation to keep controllers thin.
28
29	## 6. Testing Conventions
30	- Pest (or PHPUnit) for feature tests covering controllers, Livewire components (`Livewire::test(...)`), and queued jobs.
31	- Use Laravel's `RefreshDatabase` trait with a dedicated test PostgreSQL database — never SQLite-in-memory for tests if production runs PostgreSQL, since dialect differences (JSON operators, array types) can hide bugs.
32	- Run `php artisan test --parallel` in CI for faster feedback on larger suites.
33
34	## 7. Git Workflow & PR Conventions
35	- Conventional Commits scoped to the module, e.g. `fix(livewire/project-form): validate slug uniqueness`.
36	- Migrations ship in the same PR as the model/schema change they support; never edit a migration that has already run in a shared environment — add a new one.
37	- Require `php artisan test`, `phpstan analyse` (or Larastan), and `npm run build` green before merge.
38	- Squash-merge; run `php artisan migrate` as a deploy step, never manually against production.

Works with Cursor · Claude Code · Windsurf · AGY

Architecture notes

Architecture Overview

Standardized production guidelines for Laravel 13, Livewire, and PostgreSQL — a server-rendered PHP monolith pattern that avoids a separate frontend build for most CRUD-heavy applications.

Verified Real-World Adoption

Coolify, a self-hosted PaaS for deploying applications and databases, is built on exactly this stack: Laravel + Livewire + Alpine.js + Tailwind CSS + PostgreSQL, run inside Docker.

Key Architectural Nuances

N+1 Prevention as a First-Class Concern: Model::preventLazyLoading() turns silent N+1 query degradation into a loud local exception, catching the single most common Eloquent performance bug before it reaches production.
Queues as the Default for Side Effects: Any external call (email, webhook, file processing) is expected to go through a queued Job rather than execute inline, keeping request/response cycles fast and retryable on failure.

Frequently asked questions

Does this AGENTS.md work with Cursor, Claude Code, and Windsurf?

Yes — AGENTS.md is the open, cross-tool standard read by Cursor, Claude Code, Windsurf, and 30+ other agents. A dedicated .mdc file is also included for Cursor's native .cursor/rules format.

Why Livewire instead of a separate React/Vue frontend?

Livewire lets a Laravel monolith ship reactive, dynamically-updating UI while keeping all state and logic in PHP on the server — no separate API layer, no client-server type duplication, and no second build pipeline. It trades some client-side interactivity ceiling for a much simpler architecture, which fits most CRUD-heavy SaaS and admin tools well.

Why does PHP/Laravel appear as its own stack instead of folded into the "Ruby / PHP" survey option?

Rails and Laravel solve the same class of problem (server-rendered monolith, batteries-included ORM, background job queue) but have distinct enough conventions -- Eloquent vs ActiveRecord, Livewire vs Hotwire, Artisan vs Rails generators -- that a single AGENTS.md covering both would blur the guidance. This rule is the Laravel-specific counterpart to the Rails + PostgreSQL + Redis rule.

Used in production

Explore all stacks

Nextcloud

Self-Hosted Collaborative Productivity Suite · 20+ people

Server internals (OC) are kept separate from a versioned public API (OCP) so that independently namespaced apps under apps/ can extend Nextcloud without depending on private implementation details, while database support is validated per-engine in CI.

Coolify

Self-Hosted Cloud PaaS · Solo

A Laravel + Livewire monolith that bundles its own buildpacks (Nixpacks, Railpack) and a self-hosted Soketi realtime server lets one application both serve the dashboard and build/deploy arbitrary user code on remote servers without depending on external SaaS.

Appwrite

Backend-as-a-Service · 20+ people

A single PHP/Swoole codebase shares its API and worker processes so every product (Auth, Databases, Functions, Realtime) scales as copies of one image, while pluggable adapters keep PostgreSQL and Redis as defaults without hard-coding them.

Every stack ships as files

More AI agent coding rules and skills

View all

django-postgres-redis/AGENTS.mdDjango + PostgreSQL + Redis + CeleryDjango · Python · PostgreSQL fastapi-python-postgres/AGENTS.mdFastAPI + Python + PostgreSQL (Async SQLAlchemy & Pydantic v2)FastAPI · Python · PostgreSQL go-echo-sqlite/AGENTS.mdGo + Echo + SQLite (Embedded, Self-Hosted Tools)Go · Echo · SQLite nestjs-postgres-redis/AGENTS.mdNestJS + PostgreSQL + Redis + BullMQNestJS · Node.js · TypeScript