syarif-laravel-ai-skills

Use Actions and Services as deliberate Laravel application boundaries for use cases, integrations, and reusable workflows.

Build AI features with the first-party Laravel AI SDK (Laravel 13+); agents, embeddings, images, audio, and tool calling with provider-agnostic APIs

Laravel guidance to use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly

Laravel guidance to evolve APIs safely using versioned DTOs/transformers, deprecations, and compatibility tests

Apply Laravel-native architecture decisions without forcing unnecessary repositories, interfaces, DTOs, or custom layers.

Laravel guidance to compose UIs with Blade components, slots, and layouts; keep templates pure and testable

Interactive design refinement tailored to Laravel projects; clarify domain, data, interfaces, testing, and quality gates while accounting for Sail/non‑Sail environments

Request effective code reviews-specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

Laravel guidance to keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches

Laravel guidance to portable storage configuration across S3/R2/MinIO with optional CDN-env toggles, path-style endpoints, and URL generation

Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files

Keep Laravel controllers focused on HTTP orchestration by moving validation, authorization, and business workflows outward.

Laravel guidance to write focused controller tests using HTTP assertions; keep heavy logic in Actions/Services and unit test them

Laravel guidance to create and register small, pure helper functions when they improve clarity; keep them organized and tested

Practical daily checklist for Laravel projects; bring services up, run migrations, queues, quality gates, and tests

Laravel guidance to process large datasets efficiently using chunk(), chunkById(), lazy(), and cursor() to reduce memory consumption and improve performance

Keep Laravel writes atomic and consistent with transactions, locks, retries, idempotency, side-effect boundaries, and after-commit dispatch.

Laravel guidance to create effective debugging prompts-include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

Laravel guidance to remove unneeded Composer packages and assets to improve boot time, memory, and security surface

Laravel guidance to write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code

Laravel E2E testing with official Playwright patterns for locators, auth state, seeds, traces, screenshots, CI, and cross-browser workflows.

Provide comprehensive context in prompts-files, errors, Laravel version, dependencies, and monorepo details-for accurate AI responses

Laravel guidance to keep Eloquent models explicit, query shapes intentional, relationship loading visible, and production data access bounded.

Laravel guidance to define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely

Laravel guidance to use reportable/renderable exceptions, structured logs, and channel strategy for observability and graceful failures

Execute Laravel plans in small batches with checkpoints-TDD first, migrations safe, queues verified, and quality gates enforced

Audit completed Laravel projects and propose reusable updates to personal Laravel standards without importing project-specific details.

Laravel guidance to store and serve files via Storage; set visibility, generate URLs, and handle streaming safely

Use Laravel Form Requests for non-trivial validation and authorization while keeping controllers thin and testable.

Laravel guidance to operate Horizon with confidence-naming, tags, concurrency, failure handling, actionable metrics, and dashboards

Laravel guidance to use the HTTP client with sensible timeouts, retries, and backoff; capture context and handle failures explicitly

Integrate WhatsApp through a secure Baileys sidecar with Laravel, including tests and reusable local Windows and Linux VPS setup documentation.

Laravel guidance to use interfaces and dependency injection to decouple code; bind implementations in the container

Build with i18n in mind from day one using Laravel translation helpers, JSON files, Blade integration, and locale management

Laravel guidance to refine AI-generated code through specific feedback-point out errors, identify gaps, show desired changes, reference style guides

Work in Laravel 11 or 12 apps with stack detection, Boost-aware docs lookup, frontend conventions, tests, and Pint formatting.

Optimize Laravel database work across N+1 queries, indexes, selective columns, caching, pagination, large data, locks, and migrations.

Use Laravel-specific vocabulary-Eloquent patterns, Form Requests, API resources, jobs/queues-to get idiomatic framework code

Coordinate full Laravel feature work across models, APIs, auth, queues, Livewire, tests, and quality checks by routing to focused skills.

Force the laziest working solution before any Laravel skill writes code. Question YAGNI, reuse existing helpers, prefer stdlib/native features, and keep the shortest working diff.

Build, refactor, secure, optimize, and test Laravel Livewire v2-v4 components, including state, forms, events, uploads, pagination, Alpine, and v4 formats.

Provide automatic long-term Laravel AI memory preflight, recall, checkpointing, and secure cross-project context across conversation, project, user, workflow, and codebase scopes.

Laravel guidance to safe database change patterns; when to modify vs add migrations; always pair models with migrations and factories; seeding guidance

Build Laravel projects with one menu or page per module, using small controllers, per-page views, shared layouts/components, and dynamic DB-backed data.

Laravel guidance to consistent Nova resources-fields, actions, metrics, lenses, filters, authorization-and how to evolve resources alongside schema changes

Laravel guidance to use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness

Laravel guidance to prevent N+1 queries by eager loading; enable lazy-loading protection in non-production; choose selective fields

Laravel guidance to select only required columns to reduce memory and transfer costs; apply to base queries and relations

Use first-party PHP attributes (Laravel 13+) for controllers, authorization, queue jobs, and models; declarative configuration colocated with code

Laravel guidance to enforce access via Policies and Gates; use authorize() and authorizeResource() to standardize controller protections