Application features
Build routes, controllers, requests, services, resources, views, Livewire or Inertia flows, and clear error behavior.
Codex Skills for Laravel give Codex a focused process for building routes, controllers, validation, Eloquent models, authorization, queues, tests, APIs, and deployment-ready application changes. Download the skills and configure them for your PHP version, Laravel release, database, frontend stack, and hosting environment.
task: complete laravel application development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong laravel application development work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for laravel application development while preserving local conventions, important constraints, and human review.
Build routes, controllers, requests, services, resources, views, Livewire or Inertia flows, and clear error behavior.
Design models, relationships, scopes, migrations, transactions, indexes, factories, and query-efficient data access.
Apply policies, gates, authentication, validation, rate limits, queues, retries, idempotency, and safe file handling.
Create feature and unit tests, seed controlled data, inspect logs, optimize configuration, and prepare migrations and workers.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read composer files, framework and PHP versions, routes, service providers, models, policies, jobs, frontend stack, and tests.
Trace middleware, validation, authorization, transactions, events, queues, storage, and responses.
Use container bindings, requests, policies, resources, Eloquent patterns, and existing application structure.
Run tests, check migrations and queues, inspect queries and authorization, and document deployment order.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Build server-rendered, Livewire, or Inertia experiences with forms, sessions, permissions, and data.
Create authenticated endpoints, resources, validation, pagination, rate controls, and contract tests.
Develop jobs, events, listeners, retries, uniqueness, monitoring, and failure recovery.
Improve models, relationships, migrations, transactions, query counts, indexes, and data integrity.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable laravel application development work with a visible process.
Build features, APIs, data models, queues, tests, and production fixes.
Use Laravel conventions consistently while retaining application-specific architecture.
Deliver maintainable client applications with repeatable security, testing, and deployment checks.
Develop tenants, billing flows, permissions, background work, notifications, and operational controls.
The skills assist Laravel work, but production migrations, credentials, payment logic, authorization, and infrastructure changes require authorized review and backups.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included laravel application development guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this laravel application development work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
The installed project and composer constraints define the framework and PHP APIs available.
Yes. They cover routing, requests, resources, authentication, policies, validation, pagination, and tests.
Yes, when those tools are already configured or explicitly requested.
They can inspect query counts, eager loading, relationships, indexes, pagination, and transaction behavior.
They can create and test migrations. Production execution requires explicit authorization, backups, and a rollback plan.
Clear context. Purposeful work. Relevant checks. A result others can understand.