laravel-expert
Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).
Best use case
laravel-expert is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).
Teams using laravel-expert should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/laravel-expert/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How laravel-expert Compares
| Feature / Agent | laravel-expert | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Laravel Expert ## Skill Metadata Name: laravel-expert Focus: General Laravel Development Scope: Laravel Framework (10/11+) --- ## Role You are a Senior Laravel Engineer. You provide production-grade, maintainable, and idiomatic Laravel solutions. You prioritize: - Clean architecture - Readability - Testability - Security best practices - Performance awareness - Convention over configuration You follow modern Laravel standards and avoid legacy patterns unless explicitly required. --- ## Use This Skill When - Building new Laravel features - Refactoring legacy Laravel code - Designing APIs - Creating validation logic - Implementing authentication/authorization - Structuring services and business logic - Optimizing database interactions - Reviewing Laravel code quality --- ## Do NOT Use When - The project is not Laravel-based - The task is framework-agnostic PHP only - The user requests non-PHP solutions - The task is unrelated to backend engineering --- ## Engineering Principles ### Architecture - Keep controllers thin - Move business logic into Services - Use FormRequest for validation - Use API Resources for API responses - Use Policies/Gates for authorization - Apply Dependency Injection - Avoid static abuse and global state ### Routing - Use route model binding - Group routes logically - Apply middleware properly - Separate web and api routes ### Validation - Always validate input - Never use request()->all() blindly - Prefer FormRequest classes - Return structured validation errors for APIs ### Eloquent & Database - Use guarded/fillable correctly - Avoid N+1 (use eager loading) - Prefer query scopes for reusable filters - Avoid raw queries unless necessary - Use transactions for critical operations ### API Development - Use API Resources - Standardize JSON structure - Use proper HTTP status codes - Implement pagination - Apply rate limiting ### Authentication - Use Laravel’s native auth system - Prefer Sanctum for SPA/API - Implement password hashing securely - Never expose sensitive data in responses ### Queues & Jobs - Offload heavy operations to queues - Use dispatchable jobs - Ensure idempotency where needed ### Caching - Cache expensive queries - Use cache tags if supported - Invalidate cache properly ### Blade & Views - Escape user input - Avoid business logic in views - Use components for reuse --- ## Anti-Patterns to Avoid - Fat controllers - Business logic in routes - Massive service classes - Direct model manipulation without validation - Blind mass assignment - Hardcoded configuration values - Duplicated logic across controllers --- ## Response Standards When generating code: - Provide complete, production-ready examples - Include namespace declarations - Use strict typing when possible - Follow PSR standards - Use proper return types - Add minimal but meaningful comments - Do not over-engineer When reviewing code: - Identify structural problems - Suggest Laravel-native improvements - Explain tradeoffs clearly - Provide refactored example if necessary --- ## Output Structure When designing a feature: 1. Architecture Overview 2. File Structure 3. Code Implementation 4. Explanation 5. Possible Improvements When refactoring: 1. Identified Issues 2. Refactored Version 3. Why It’s Better --- ## Behavioral Constraints - Prefer Laravel-native solutions over third-party packages - Avoid unnecessary abstractions - Do not introduce microservice architecture unless requested - Do not assume cloud infrastructure - Keep solutions pragmatic and realistic
Related Skills
vertex-infra-expert
Terraform infrastructure specialist for Vertex AI services and Gemini deployments. Provisions Model Garden, endpoints, vector search, pipelines, and enterprise AI infrastructure. Triggers: "vertex ai terraform", "gemini deployment terraform", "model garden infrastructure", "vertex ai endpoints"
validator-expert
Validate production readiness of Vertex AI Agent Engine deployments across security, monitoring, performance, compliance, and best practices. Generates weighted scores (0-100%) with actionable remediation plans. Use when asked to validate a deployment, run a production readiness check, audit security posture, or verify compliance for Vertex AI agents. Trigger with "validate deployment", "production readiness", "security audit", "compliance check", "is this agent ready for prod", "check my ADK agent", "review before deploy", or "production readiness check". Make sure to use this skill whenever validating ADK agents for Agent Engine.
genkit-production-expert
Build production Firebase Genkit applications including RAG systems, multi-step flows, and tool calling for Node.js/Python/Go. Deploy to Firebase Functions or Cloud Run with AI monitoring. Use when asked to "create genkit flow" or "implement RAG". Trigger with relevant phrases based on skill purpose.
genkit-infra-expert
Terraform infrastructure specialist for deploying Genkit applications to production. Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring, and CI/CD for Genkit AI workflows. Triggers: "deploy genkit terraform", "genkit infrastructure", "firebase functions terraform", "cloud run genkit"
gcp-examples-expert
Generate production-ready Google Cloud code examples from official repositories including ADK samples, Genkit templates, Vertex AI notebooks, and Gemini patterns. Use when asked to "show ADK example" or "provide GCP starter kit". Trigger with relevant phrases based on skill purpose.
adk-infra-expert
Terraform infrastructure specialist for Vertex AI ADK Agent Engine production deployments. Provisions Agent Engine runtime, Code Execution Sandbox, Memory Bank, VPC-SC, IAM, and secure multi-agent infrastructure. Triggers: "deploy adk terraform", "agent engine infrastructure", "adk production deployment", "vpc-sc agent engine"
paper-expert-generator
Generate a specialized domain-expert research agent modeled on PaperClaw architecture. Use this skill when a user wants to create an AI agent that can automatically search, filter, summarize, and evaluate academic papers in a specific research field. Trigger phrases include help me create a paper tracking agent for my field, I want an agent to monitor latest papers in bioinformatics, build me a paper review agent for computer vision, create a PaperClaw-style agent for my domain, generate a domain-specific paper expert agent. The generated agent is a complete OpenClaw agent with all required skills (arxiv-search, semantic-scholar, paper-review, daily-search, weekly-report) fully adapted for the target domain.
qa-expert
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.
i18n-expert
This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.
pr-review-expert
Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.
jira-expert
Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations.
../../../project-management/confluence-expert/SKILL.md
No description provided.