agentsclimarketplace

Laravel validation

Skill event4u-app/agent-config/dist/agent-src/skills/laravel-validation

Universal AI Agent OS — audited skills, governance rules, replayable state. One contract, every host agent.

Install
npx -y skills add event4u-app/agent-config --skill laravel-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when writing validation — Form Requests, rules, custom rule objects, request-boundary design — even when the user just says 'validate this input' or 'check the request' without naming it.

SKILL.md

2.4 KB, 450 tokens by cl100k_base, as published. Nobody here has run it

laravel-validation

When to use

Use when creating FormRequests, validation rules, or custom rule objects.

Do NOT use when:

  • Authorization logic only (use security skill)
  • API response format (use api-design skill)

Procedure: Create a FormRequest

Step 0: Inspect

  1. Check existing FormRequests — match style, naming, authorization, rule structure.
  2. Check existing custom rules — reuse before creating new ones.
  3. Check API error response format — match it.

Step 1: Create the class

  1. Name: {Action}{Entity}Request — e.g. CreateProjectRequest.
  2. Implement authorize() using Policies.
  3. Implement rules() with array syntax — never pipe-separated.
  4. Use prepareForValidation() only when normalization is truly necessary.

Step 2: Rules

  1. Use Laravel's Illuminate\Validation\Rules classes where possible.
  2. Keep rules explicit — prefer clarity over cleverness.
  3. For nested arrays: validate structure AND leaf values.
  4. Extract custom rule objects for complex/reusable logic.

Step 3: Test

  • Test required fields, invalid formats, boundary conditions, conditional rules.
  • Test authorization where relevant.
  • Use focused tests per validation concern.

Conventions

→ See guideline php/validations.md for array syntax, route params, property mapping, custom rules.

Output format

  1. FormRequest class with rules, messages, and authorization
  2. Custom Rule object if validation logic is complex

Gotcha

  • required ≠ not nullable — required means present, nullable means value can be null.
  • Custom Rule objects must return $fail callback, not throw exceptions.
  • Don't validate data you already trust (e.g., from a verified internal service).

Do NOT

  • Do NOT validate in controllers — use FormRequest classes.
  • Do NOT use $request->all() — use $request->validated().
  • Do NOT put business logic in validation classes.

Auto-trigger keywords

  • validation
  • Form Request
  • validation rules
  • custom rule

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.