Agent skill

Laravel Best Practices

by anonaddy in anonaddy/anonaddy

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

MITAuto-check passedBackend & APIs

Install Laravel Best Practices

skills CLI
$ npx skills add anonaddy/anonaddy --skill laravel-best-practices -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anonaddy/anonaddy laravel-best-practices --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/anonaddy/anonaddy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/laravel-best-practices .claude/skills/laravel-best-practices && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
laravel-best-practices
GitHub stars
4.9k
Used in
13 other repos
Token cost
~1.2k tokens
SKILL.md length
419 words
Files
20
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

  • Works in 6 steps: Check the changed files, nearby code,… → Map every affected concern to the rule… → Make the smallest coherent change. Keep… → …
  • N+1 and query performance issues
  • SKILL.md covers Consistency First, How to Apply, Rule Index and Decision Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Laravel Best Practices is an agent skill from anonaddy/anonaddy. Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files (for example `rules/advanced-queries.md`, `rules/architecture.md` and `rules/blade-views.md`).

It sits in Backend & APIs, covering Backend development and Query optimization. It works with Laravel and PHP. The repository describes itself as: Anonymous email forwarding. The licence is MIT.

When your agent uses it

  • N+1 and query performance issues
  • Caching strategies
  • Authorization and security patterns
  • Queue and job configuration

Example prompts

  • “/laravel-best-practices”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Check the changed files, nearby code, project configuration, and relevant tests for established patterns. Deviate only for a correctness…
  2. Map every affected concern to the rule index below. Read each mapped rule file before editing. Skip unrelated rule files.
  3. Make the smallest coherent change. Keep the application's architecture and naming instead of introducing a second pattern for the same job.
  4. Verify version-sensitive Laravel APIs for the installed version with search-docs, or inspect the installed framework when it is unavailable.
  5. Run the narrowest relevant tests first, then the project's formatting and static-analysis checks when the change warrants them.
  6. Re-read the diff against every mapped rule before finishing.

What it can do on your machine

Read from SKILL.md and the folder at commit 150983e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Laravel Best Practices loads about 1.2k tokens when it runs. Until then it costs about 157 tokens; SKILL.md has 419 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from anonaddy/anonaddy at commit 150983e, republished under its MIT licence (© anonaddy). 419 words, ~1,161 tokens.

Download SKILL.mdSave it as .claude/skills/laravel-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 19 other files; get the full folder from GitHub.
name
laravel-best-practices
description
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.
license
MIT
metadata.author
laravel

Laravel Best Practices

Best practices for Laravel, organized as an index of rule files. Each rule file teaches what to do and why. For exact API syntax, verify with search-docs.

Consistency First

Before applying any rule, check what the application already does. Laravel offers multiple valid approaches, and the best choice is the one the codebase already uses, even if another pattern would be theoretically better. Inconsistency is worse than a suboptimal pattern.

Check sibling files, related controllers, models, or tests for established patterns. If one exists, follow it. Don't introduce a second way. These rules are defaults for when no pattern exists yet, not overrides.

How to Apply

  1. Check the changed files, nearby code, project configuration, and relevant tests for established patterns. Deviate only for a correctness or security defect, and call the deviation out.
  2. Map every affected concern to the rule index below. Read each mapped rule file before editing. Skip unrelated rule files.
  3. Make the smallest coherent change. Keep the application's architecture and naming instead of introducing a second pattern for the same job.
  4. Verify version-sensitive Laravel APIs for the installed version with search-docs, or inspect the installed framework when it is unavailable.
  5. Run the narrowest relevant tests first, then the project's formatting and static-analysis checks when the change warrants them.
  6. Re-read the diff against every mapped rule before finishing.
Show full SKILL.md (190 more words)Show less

Rule Index

Cross-cutting changes often need more than one rule file.

ConcernRead
Query count, eager loading, indexes, large datasetsrules/db-performance.md
Subqueries, aggregates, complex ordering and query plansrules/advanced-queries.md
Models, relationships, scopes, castsrules/eloquent.md
Authentication, authorization, input safety, secrets, uploadsrules/security.md
Form Requests and validation rulesrules/validation.md
Controllers, route binding, resources, middlewarerules/routing.md
Schema changes, columns, foreign keys, indexesrules/migrations.md
Jobs, retries, uniqueness, batches, Horizonrules/queue-jobs.md
Cache lifetime, invalidation, locks, memoizationrules/caching.md
Outbound requests, retries, timeouts, fakesrules/http-client.md
Exceptions, reporting, rendering, log contextrules/error-handling.md
Events and notificationsrules/events-notifications.md
Mailables and mail assertionsrules/mail.md
Scheduled tasks and overlap protectionrules/scheduling.md
Collections, lazy iteration, bulk operationsrules/collections.md
Blade components, attributes, composersrules/blade-views.md
Environment values and application configurationrules/config.md
Tests: coverage, factories, fakes, and assertionsthe testing-best-practices skill
Naming, helpers, file boundaries, PHP stylerules/style.md
Actions, services, dependencies, application structurerules/architecture.md

Decision Rules

  • Prefer framework features and existing application abstractions over new helpers or dependencies.
  • Avoid speculative abstractions. Extract code when it creates a clear domain boundary, removes meaningful duplication, or makes behavior independently testable.
  • Keep database access out of Blade views and prevent hidden N+1 queries across controllers, resources, jobs, and serialization.

© anonaddy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 19 other files in .junie/skills/laravel-best-practices of anonaddy/anonaddy.

  • SKILL.md
  • rules/advanced-queries.md
  • rules/architecture.md
  • rules/blade-views.md
  • rules/caching.md
  • rules/collections.md
  • rules/config.md
  • rules/db-performance.md
  • rules/eloquent.md
  • rules/error-handling.md
  • rules/events-notifications.md
  • rules/http-client.md
  • rules/mail.md
  • rules/migrations.md
  • rules/queue-jobs.md
  • rules/routing.md
  • rules/scheduling.md
  • rules/security.md
  • rules/style.md
  • rules/validation.md

Open the folder on GitHubat commit 150983e

Used in 15 other repositories

We found 31 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 13 other GitHub owners. This page covers the copy in anonaddy/anonaddy, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Laravel Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Laravel Best Practices compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Laravel Best Practices this skillanonaddy/anonaddy4.9k13 repos~1.2kAutomated safety check: PassMIT
Lerdliberusoftware/real-estate-laravel112—~7.8kAutomated safety check: WarnMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Geoflowyaojingang/GEOFlow3.8k—~722Automated safety check: PassAGPL-3.0
Livewire Developmentcoollabsio/coolify63k—~964Automated safety check: PassMIT

Similar skills

  • Lerd

    liberusoftware/real-estate-laravel

    Manage the lerd local PHP development environment via MCP tools: run framework console commands (artisan, bin/console, etc.), manage services, start/stop queue workers, run composer, manage Node.js…

    112 GitHub stars~7.8k tokensUpdated yesterday
    Backend & APIsAuto-check: warnings
  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed
  • Geoflow

    yaojingang/GEOFlow

    Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.

    3.8k GitHub stars~722 tokensUpdated today
    Backend & APIsAuto-check passed
  • Livewire Development

    coollabsio/coolify

    A skill your agent uses for any task or question involving Livewire.

    63k GitHub stars~964 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Laravel Specialist

    Jeffallan/claude-skills

    Builds Laravel 10+ applications with Eloquent models, Sanctum authentication, Horizon queues, API resources and Livewire components, tested with Pest or PHPUnit.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Backend & APIsAuto-check passed

More from anonaddy/anonaddy

  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Auto-check passed
  • Inertia Vue Development

    anonaddy/anonaddy

    Develops Inertia.js v3 Vue client-side applications. An agent skill from anonaddy/anonaddy.

    4.9k GitHub starsUsed in 3 repos~3.4k tokens
    Auto-check passed
  • Infer Conventions

    anonaddy/anonaddy

    A skill your agent uses to analyze how a Laravel application is actually written and record its conventions as shared rules.

    4.9k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed
  • Testing Best Practices

    anonaddy/anonaddy

    Laravel test design and review. An agent skill from anonaddy/anonaddy.

    4.9k GitHub starsUsed in 5 repos~1k tokens
    Auto-check passed
  • A skill your agent uses when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop…

    4.9k GitHub stars~2.3k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Laravel Best Practices

What does Laravel Best Practices do?

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. Laravel Best Practices is an agent skill from anonaddy/anonaddy. Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

When should I use Laravel Best Practices?

Laravel Best Practices fits situations like: N+1 and query performance issues; caching strategies; authorization and security patterns; queue and job configuration.

How do I install Laravel Best Practices in Claude Code?

Run `npx skills add anonaddy/anonaddy --skill laravel-best-practices -a claude-code`. Or copy the skill folder (.junie/skills/laravel-best-practices in anonaddy/anonaddy) into .claude/skills/laravel-best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Laravel Best Practices in Codex?

Run `npx skills add anonaddy/anonaddy --skill laravel-best-practices -a codex`. Or copy the skill folder (.junie/skills/laravel-best-practices in anonaddy/anonaddy) into .agents/skills/laravel-best-practices in your project. Codex loads it when a task matches its description.

Can I use Laravel Best Practices in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anonaddy/anonaddy --skill laravel-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/laravel-best-practices, .gemini/skills/laravel-best-practices, .github/skills/laravel-best-practices and .opencode/skills/laravel-best-practices in your project.

What does Laravel Best Practices need to run?

SKILL.md names no scripts, command-line tools or credentials: Laravel Best Practices is instructions for the agent only.

Does Laravel Best Practices access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Laravel Best Practices safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Laravel Best Practices use?

Laravel Best Practices is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Laravel Best Practices use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Laravel Best Practices?

Skills that share tags, products or a category with Laravel Best Practices: Lerd (liberusoftware/real-estate-laravel, 112 stars), Configuring Horizon (coollabsio/coolify, 63k stars), Fortify Development (coollabsio/coolify, 63k stars) and Geoflow (yaojingang/GEOFlow, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Laravel Best Practices?

anonaddy (a GitHub organization) maintains it in anonaddy/anonaddy, which has 4,895 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.

Source: anonaddy/anonaddy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.