Laravel:Form Requests
CheckedThis skill streamlines Laravel form validation using Form Requests, simplifying development and improving code maintainability for robust data handling.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add jpcaparas/superpowers-laravel --skill laravel:form-requests -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
jpcaparas
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned jpcaparas/superpowers-laravel at c5198b16cd.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c5198b16cd
- Scanned
- 1 file, 62 lines
About this skill
What it does
This skill enables AI agents to streamline form validation and authorization within Laravel applications using Form Requests. It promotes moving validation logic into dedicated classes, allowing controllers to focus on application orchestration and business logic. The skill facilitates creating these requests and integrating them into controller methods for robust data handling and improved code maintainability.
When to use it
- When building Laravel applications that require complex form validation beyond simple rules.
- To centralize authorization logic and improve the security of your forms.
- For projects where you want to keep controllers clean and focused on core application functionality.
- When needing to validate nested arrays within a form submission (e.g.,
items.*.sku).
Key capabilities
- Form Request Creation: Generates Form Request classes using the command:
sail artisan make:request <RequestName>orphp artisan make:request <RequestName>. - Authorization: Allows defining an
authorize()method within Form Requests to control access. Suggests using Policies for more complex authorization checks. - Custom Validation Rules: Supports the creation and use of custom validation rules, including unique rule objects (e.g.,
Rule::unique('users', 'email')->ignore($user->id)). - Nested Array Validation: Provides capabilities to validate nested array structures within form data.
- Safe Data Retrieval: Facilitates retrieving only specific fields from a request using
$request->safe()->only([...])for partial updates.
Example prompts
- "Create a Form Request class named 'UpdateProfileRequest'."
- "How do I implement authorization in a Laravel Form Request?"
- "Show me an example of validating a nested array within a Form Request."
Tips & gotchas
- For complex authorization requirements, consider using Laravel Policies instead of directly implementing logic within the Form Request.
- Standardize attribute names and validation messages using the
attributes()andmessages()methods in your Form Requests for consistent error reporting. - Remember to feature test endpoints with both successful and failing validation scenarios.