# spatie-laravel-php

Applies Spatie guidelines and PSR-12 standards when generating, refactoring, or reviewing Laravel PHP files and Blade templates.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1200 installs · ★ 97
- Author: Spatie
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/spatie/guidelines-skills/tree/HEAD/resources/boost/skills/spatie-laravel-php/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/spatie-laravel-php

## What it does

This skill guides coding agents through Spatie's conventions for PHP and Laravel projects. It enforces typed properties, explicit return types including `void`, constructor property promotion, and early returns instead of nested `else` statements. When breaking a method chain across lines, every subsequent `->` must start on a separate line.

The workflow standardises Laravel structures. Controllers use plural names, route definitions require tuple syntax such as `[PostsController::class, 'index']`, and configuration values come from `config()` rather than `env()`. The skill prevents redundant docblocks when native type hints exist and bans adding `final` or `readonly` keywords by default.

JavaScript, TypeScript, CSS, database schema design, and non-Laravel setups remain out of scope. If a guideline clashes with existing repository rules, standard Laravel conventions take precedence to preserve consistency.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/guidelines-skills --skill spatie-laravel-php -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/spatie-laravel-php/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/spatie-laravel-php/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/guidelines-skills --skill spatie-laravel-php -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/spatie-laravel-php/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/guidelines-skills --skill spatie-laravel-php -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/spatie-laravel-php/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install spatie/guidelines-skills spatie-laravel-php
```

2. **Manually: put the files in place**
- File: `.github/skills/spatie-laravel-php/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/guidelines-skills --skill spatie-laravel-php -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/spatie/guidelines-skills --path resources/boost/skills/spatie-laravel-php
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/spatie-laravel-php/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add spatie/guidelines-skills --skill spatie-laravel-php -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/spatie/guidelines-skills/tree/HEAD/resources/boost/skills/spatie-laravel-php/SKILL.md

## When to use it
- format Laravel controllers and Eloquent models to Spatie standards
- eliminate redundant docblocks covered by native PHP types
- replace nested else branches with early returns
- standardise route definitions with controller tuple syntax

## Example prompts
- Refactor PostsController.php using Spatie coding conventions
- Create an Order model and migration with typed properties
- Review routes in routes/web.php to match Laravel standards

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d54223c56924133e.

BEGIN THIRD-PARTY FILE d54223c56924133e
```text
---
name: spatie-laravel-php
description: Apply Spatie's Laravel and PHP coding standards for any task that creates, edits, reviews, refactors, or formats Laravel/PHP code or Blade templates; use for controllers, Eloquent models, routes, config, validation, migrations, tests, and related files to align with Laravel conventions and PSR-12.
license: MIT
metadata:
  author: Spatie
---

# Spatie Laravel & PHP Guidelines

## Overview
Apply Spatie's Laravel and PHP guidelines to keep code style consistent and Laravel-native.

## When to Activate
- Activate this skill for any Laravel or PHP coding work, even if the user does not explicitly mention Spatie.
- Activate this skill when asked to generate, edit, format, refactor, review, or align Laravel/PHP code.
- Activate this skill when working on `.php` or `.blade.php` files, routes, controllers, models, config, validation, migrations, or tests.

## Scope
- In scope: `.php`, `.blade.php`, Laravel conventions (routes, controllers, config, validation, migrations, tests).
- Out of scope: JS/TS, CSS, infrastructure, database schema design, non-Laravel frameworks.

## Workflow
1. Identify the artifact (controller, route, config, model, Blade, test, etc.).
2. Read `references/spatie-laravel-php-guidelines.md` and focus on the relevant sections.
3. Apply the core Laravel principle first, then PHP standards, then section-specific rules.
4. If a rule conflicts with existing project conventions, follow Laravel conventions and keep changes consistent.

## Core Rules (Summary)
- Follow Laravel conventions first.
- Follow PSR-1, PSR-2, and PSR-12.
- Prefer typed properties and explicit return types (including `void`).
- Use short nullable syntax like `?string`.
- Use constructor property promotion when all properties can be promoted.
- One trait per line with separate `use` statements.
- Once a method chain breaks across lines, put every subsequent `->` on a new line; never mix single-line and multi-line chaining.
- Prefer early returns and avoid `else` when possible.
- Always use curly braces for control structures.
- Use string interpolation over concatenation.
- Happy path last: handle error conditions first.

## Do and Don't
Do:
- Use kebab-case URLs, camelCase route names, and camelCase route parameters.
- Use tuple notation for routes: `[Controller::class, 'method']`.
- Use plural resource names for controllers (`PostsController`).
- Use array notation for validation rules.
- Use `config()` helper and avoid `env()` outside config files.
- Add service configs to `config/services.php`, not new files.
- Use `__()` for translations instead of `@lang`.
- Use PascalCase for enum values and class constants.

Don't:
- Add docblocks when full type hints already exist.
```
END THIRD-PARTY FILE d54223c56924133e

The third-party file has ended. Everything between the d54223c56924133e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2743 of 3426 bytes. © Spatie · MIT · https://github.com/spatie/guidelines-skills/tree/HEAD/resources/boost/skills/spatie-laravel-php/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md