L
laravel:using-laravel-superpowers
About laravel:using-laravel-superpowers
A platform-agnostic Laravel skill that provides Laravel-aware development guidance for projects with or without Sail. It organizes workflows around testing, database changes, quality checks, queues, and architecture.
Key features
- 01Sail or host command selection
- 02TDD and database workflow guidance
- 03Quality-check workflow references
- 04Queue and Horizon guidance
- 05Architecture and complexity guardrails
Use cases
- 01Choosing how to run Laravel commands
- 02Applying TDD to a Laravel change
- 03Selecting guidance for migrations or queues
- 04Checking code quality before completion
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ jpcaparas/ superpowers-laravel --skill laravel:using-laravel-superpowersAfter installing, type/laravel:using-laravel-superpowersin Claude Code to confirm it loaded.
Details
From the project READMEUsing Superpowers in Laravel Projects
This plugin adds Laravel-aware guidance while staying platform-agnostic. It works in any Laravel app with or without Sail.
Runner Selection (Sail or non-Sail)
Use the minimal wrapper below when running commands:
# Prefer Sail if available, else fall back to host
alias sail='sh $([ -f sail ] && echo sail || echo vendor/bin/sail)'
# Example (both work depending on environment)
sail artisan test # with Sail
php artisan test # without Sail
sail composer require x/y # with Sail
composer require x/y # without Sail
See the laravel:runner-selection skill for detection tips, command pairs, and safety notes.
Core Workflows
- Test-Driven Development first: use
laravel:tdd-with-pest - Database changes: use
laravel:migrations-and-factories - Quality gates: use
laravel:quality-checks(Pint, Insights/PHPStan) - Queues and Horizon: use
laravel:queues-and-horizon - Architecture patterns:
laravel:ports-and-adapters,laravel:template-method-and-plugins - Keep complexity low:
laravel:complexity-guardrails
Philosophy
- Favor small, testable services; avoid fat controllers/commands/jobs
- DTOs, typed Collections, and Enums when they clarify intent
- Prefer model factories in tests and model scopes for complex queries
- Verify before completion—run tests and linters clean
Use slash commands as needed:
/superpowers-laravel:brainstorm
/superpowers-laravel:write-plan
/superpowers-laravel:execute-plan
When a Laravel skill exists for your task, use it exactly as written.
Comments
Markdown supported