Skip to content
Back to skills

Reviewing Filament Plans

ASecurity

Reviews the current application repository checkout against a previously generated Filament Blueprint, checking adherence to Filament v5.x modular structure (Schemas/, Tables/, and Infolists/ classes), widgets, multi-tenancy scoping, authorization policies, and test suites.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsphpsecurity

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add edmer664/fila-boost --skill reviewing-filament-plans --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Reviewing Filament Plans?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Reviewing Filament Plans
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/edmer664-reviewing-filament-plans/badge)](https://www.skillsdirectory.com/skills/edmer664-reviewing-filament-plans)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: reviewing-filament-plans
description: "Reviews the current application repository checkout against a previously generated Filament Blueprint, checking adherence to Filament v5.x modular structure (Schemas/, Tables/, and Infolists/ classes), widgets, multi-tenancy scoping, authorization policies, and test suites."
version: 1.1.0
triggers:
  - "review filament"
  - "verify filament"
  - "audit filament blueprint"
  - "filament blueprint review"
---

# Filament v5.x Review Skill (`reviewing-filament-plans`)

When invoked, the AI coding agent MUST evaluate an existing application codebase checkout against a saved Filament v5.x Blueprint document.

## Auditing Rules

1. **Filament v5.x Modular Directory Compliance**:
   - Verify that Resource classes do NOT declare monolithic inline form, table, or infolist closures.
   - Confirm presence of `app/Filament/Resources/{Cluster?}/{Name}s/Schemas/{Name}Form.php`.
   - Confirm presence of `app/Filament/Resources/{Cluster?}/{Name}s/Tables/{Name}sTable.php`.
   - If an infolist was planned, confirm presence of `app/Filament/Resources/{Cluster?}/{Name}s/Infolists/{Name}Infolist.php`.

2. **Widgets & Dashboards**:
   - Verify that planned widgets (`StatsOverviewWidget`, charts, tables) exist in `app/Filament/Widgets/` or resource subdirectories.

3. **Multi-Tenancy Scoping**:
   - If multi-tenancy is planned, confirm the Tenant model (`Team` or `Company`) exists and that panel routing configures `->tenant()`.
   - Verify scoped models possess tenant relationship foreign keys (`team_id`).

4. **Security & Authorization Defaults**:
   - Confirm Model Policies exist (`app/Policies/{Name}Policy.php`) with explicit gate abilities (`viewAny`, `create`, `update`, `delete`).
   - If multi-tenancy is active, verify policies check tenant ownership.

5. **Pest Tests & Quality Gates**:
   - Ensure corresponding test suites exist in `tests/Feature/Filament/`.
   - Require automated verification via `vendor/bin/pint --test` and `vendor/bin/pest`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.