
Laravel Api
This is Steve's opinionated take on building Laravel REST APIs with strict architectural boundaries. Everything is stateless, explicitly typed, and organized by resource. You get invokable controllers, form request DTOs with payload methods, single-purpose Action classes, and ULID-based models. Routes are versioned with HTTP Sunset headers baked in. The code quality section is aggressive about PSR-12, no nested ternaries, and preserving exact behavior during refactors. If you want a prescriptive pattern that eliminates decision fatigue on API structure, this locks you into a defensible convention. Good for teams that need consistency or solo devs tired of reinventing routing organization.
- skills.sh installs
- 292
- GitHub stars
- 31
- last updated
- Aug 21, 2026
Install
$ npx -y skills add juststeveking/laravel-api-skill --skill laravel-api --agent claude-codeInstalls into .claude/skills of the current project.
Files
Laravel API - Steve's Architecture
Build Laravel REST APIs with clean, stateless, resource-scoped architecture.
Quick Start
When user requests a Laravel API, follow this workflow:
- Understand requirements - What resources? What operations? Authentication needed?
- Initialize project structure - Set up routing, remove frontend bloat
- Build first resource - Complete CRUD to establish pattern
- Add authentication - JWT via PHP Open Source Saver
- Iterate on remaining resources - Follow established pattern
Core Architecture Principles
Read references/architecture.md for comprehensive details. Key principles:
- Stateless by design - No hidden dependencies, explicit data flow
- Boundary-first - Clear separation of HTTP, business logic, data layers
- Resource-scoped - Routes, controllers organized by resource
- Version discipline - Namespace-based versioning, HTTP Sunset headers
Code Quality Standards
All code must follow Laravel best practices and PSR-12 standards:
Sponsors
Details
- Repository
- github.com/juststeveking/laravel-api-skill
- Categories
- Backend & APIs, Security, DevOps & CI/CD, Git & Pull Requests, Code Review & Quality, Design & UI/UX, PHP & Laravel
- First seen
- Jun 3, 2026