Skip to main content
Glama
saddamalsalfi

laravel-skills-localsetup


name: "laravel-skills-localsetup" title: "Laravel 13 Local Development Setup & Verification" description: "Professional, deterministic AI agent skill and Cursor rule for setting up, configuring, and verifying a local Laravel 13 development environment" version: "1.0.0" author: "Saddam Al-Slfi" repository: "https://github.com/saddamalsalfi/laravel-skills-localsetup" license: "MIT" created_at: "2026-09-12"

Laravel 13 Local Development Setup & Verification 🐘⚑

DOI License: MIT Open Plugins Compliant Cursor Rule Laravel

A battle-tested, production-grade AI agent skill and Cursor Rule engineered to guide AI coding assistants (Cursor, Google Antigravity / Gemini, Claude Code, GitHub Copilot, LangChain agents) through configuring, provisioning, and verifying modern Laravel 13 local development environments with deterministic accuracy and zero hallucinations.

Optimized for submission to cursor.directory, LangChain Hub, and Open Plugins.


Related MCP server: project-scaffold

🎯 What This Skill Solves

Standard AI models frequently fail when provisioning local Laravel projects: they hallucinate outdated artisan commands, ignore host vs. container environments, corrupt database configs, and miss vital 2FA or Livewire requirements.

This skill forces the AI agent to follow a strict, deterministic, step-by-step engineering protocol:

  • Runtime Pre-flight & Discovery: Probes the operating system (Host, WSL2, Docker, remote container) before executing commands; asks for explicit confirmation before installing tools.

  • Modern Laravel 13 Stack: Scaffolds starter kits with Livewire Single-File Components (SFC), Team management, and Tailwind CSS.

  • Complete Auth & Security: Integrates registration, email verification, two-factor authentication (2FA), passkeys, and test user seeders.

  • AI Coding Integration: Out-of-the-box setup for Laravel Boost, coding agent guidelines, and MCP server configuration.

  • Deterministic Health Checks: Verifies dev servers (artisan serve, npm run dev), database connections, and resolves port collisions safely.


πŸ“‚ Repository Structure (Open Plugins Standard)

This repository follows the Open Plugins Standard for plug-and-play installation across agent platforms:

β”œβ”€β”€ skills/
β”‚   └── laravel-skills-localsetup/
β”‚       └── SKILL.md                 # Agent workflow for Antigravity, Claude Code, etc.
β”œβ”€β”€ rules/
β”‚   └── laravel-skills-localsetup.mdc # Optimized rule for Cursor IDE
β”œβ”€β”€ server.py                        # Universal FastMCP executable server
β”œβ”€β”€ requirements.txt                 # Pinned dependencies for MCP runtime
β”œβ”€β”€ Dockerfile                       # Multi-platform OCI rootless container
β”œβ”€β”€ mcp.json                         # Model Context Protocol configuration
β”œβ”€β”€ plugin.json                      # Open Plugins manifest
β”œβ”€β”€ LICENSE                          # MIT License with explicit AI Agent Grant
└── README.md                        # Documentation and usage guides

πŸš€ Quick Start & Installation

1. Cursor IDE (via cursor.directory or local)

Copy the .mdc rule into your project's .cursor/rules/ directory:

mkdir -p .cursor/rules
curl -o .cursor/rules/laravel-skills-localsetup.mdc https://raw.githubusercontent.com/saddamalsalfi/laravel-skills-localsetup/main/rules/laravel-skills-localsetup.mdc

2. Google Antigravity / Gemini IDE

Add the skill into your project's .agents/skills/ directory:

mkdir -p .agents/skills/laravel-skills-localsetup
curl -o .agents/skills/laravel-skills-localsetup/SKILL.md https://raw.githubusercontent.com/saddamalsalfi/laravel-skills-localsetup/main/skills/laravel-skills-localsetup/SKILL.md

3. Open Plugins CLI / Package Manager

Install directly using the repository URL:

open-plugins install https://github.com/saddamalsalfi/laravel-skills-localsetup

4. Claude Code / LangChain Hub / Custom Agents

Load skills/laravel-skills-localsetup/SKILL.md directly into your agent's system prompt or project knowledge base.

5. Universal Executable MCP Server (Claude Desktop, Cursor, Smithery)

This skill runs natively as an executable Model Context Protocol (MCP) server exposing resources (skill://content) and tools (get_guidelines):

Claude Desktop Configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "laravel-skills-localsetup": {
      "command": "python",
      "args": ["/path/to/laravel-skills-localsetup/server.py"]
    }
  }
}

Docker Container Run:

docker build -t laravel-skills-localsetup .
docker run -i --rm laravel-skills-localsetup

πŸ“‹ Execution Phases Overview

When activated, the agent executes the following stages in order:

Phase

Description

Key Deliverables

1. Runtime Discovery

Inspects host OS, WSL distribution, PHP 8.2+, Composer, Node.js, and DB engines

Pre-flight compatibility matrix

2. Scaffolding

Creates starter-kit Laravel 13 app with single-file components

Clean app skeleton & git init

3. Database & Cache

Provisions MySQL / PostgreSQL / SQLite, configures .env, runs migrations

Verified database connection

4. Auth & Security

Configures Fortify / starter auth with 2FA, passkeys, and seeded accounts

Working authentication suite

5. AI Tooling

Sets up guidelines, MCP configuration, and agent instructions

Optimized developer workflow

6. Verification

Boots dev servers, tests endpoints, performs end-to-end smoke check

Verified working URLs & ports


πŸ›‘οΈ Guiding Principles

  1. Safety First: Never overwrite existing files, databases, or environment variables without explicit user authorization.

  2. Deterministic Outputs: Every command flag is verified against official Laravel 13 release specifications.

  3. Reproducibility: Generates reproducible scripts and idempotent configurations suitable for solo devs and teams.


πŸ“„ License & Attribution

Authored by Saddam Al-Slfi (@saddamalsalfi).

This repository is licensed under the MIT License with a Special Grant for Artificial Intelligence (AI) Agents & Automated Systems, permitting free ingestion, adaptation, and execution by all AI agents and developers.

Available Tools

1 tool
get_guidelinesA

Returns procedural guidelines and domain rules for Laravel 13 local development setup. Args: section: Optional keyword to filter content sections.

ParametersJSON Schema
NameRequiredDescriptionDefault
sectionNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool returns guidelines and supports optional filtering, implying a read-only retrieval. It does not mention edge cases like unknown sections, but the presence of an output schema lowers the need to describe return details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with the primary purpose front-loaded. There is no filler or redundant restatement of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter retrieval tool, the description covers the domain, the resource, and the filtering behavior. The output schema exists, so return structure need not be described. A minor gap is that valid section keywords are not listed, but this is acceptable given the parameter is optional.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explicitly defines the only parameter, 'section', as an optional keyword to filter content sections, adding meaning beyond the schema's type/default fields. It does not enumerate valid keywords, but the parameter is optional and simple.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Returns') and a resource ('procedural guidelines and domain rules for Laravel 13 local development setup'). It is not a tautology and clearly communicates what the tool provides.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is provided: the tool is for retrieving Laravel 13 local development guidelines. There are no sibling tools to differentiate from, so no alternative routing is needed, though explicit when-to-use language is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedget_guidelines

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly distinct by default.

Naming Consistency5/5

With a single tool, there is no mixed convention to evaluate. The name 'get_guidelines' follows a clean verb_noun pattern.

Tool Count3/5

The server has only one tool, which feels thin for a domain that could warrant separate operations (e.g., listing sections, validating setup steps). However, for a simple guidelines retrieval server, one tool is borderline acceptable.

Completeness4/5

The single tool covers the primary need of retrieving procedural guidelines, but there are minor gaps such as an explicit way to enumerate available sections or get more granular support. Agents can likely work around these gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers