Filacheck Laravel Package

Product Decisions This Supports

• Adoption of Filament v4/v5: Automatically enforce best practices and deprecation compliance for teams migrating to or maintaining Filament-based admin panels.
• Developer Productivity: Reduce manual code reviews by integrating static analysis into CI/CD pipelines, catching issues early (e.g., deprecated reactive() → live()).
• Build vs. Buy: Avoid reinventing static analysis for Filament; leverage this package instead of custom scripts or third-party tools.
• AI-Generated Code Safety: Validate AI-generated Filament scaffolding (e.g., from GitHub Copilot) before merging, ensuring compatibility with Filament’s evolving API.
• Roadmap for Filament Pro: Justify investment in FilaCheck Pro (19+ rules) for security, performance, and UX improvements if the team prioritizes scalability or compliance.
• Consistency Enforcement: Standardize Filament usage across teams by blocking deprecated patterns (e.g., ->form() → ->schema()) via CI failures.

When to Consider This Package

Adopt FilaCheck if:

• Your project uses Filament v4/v5 and needs to enforce API compliance.
• You want to integrate static analysis into CI/CD (e.g., GitHub Actions) to block deprecated code pre-merge.
• Your team relies on AI tools (e.g., GitHub Copilot) to generate Filament code and needs validation.
• You lack dedicated backend QA but want to catch common Filament pitfalls (e.g., N+1 queries in formatStateUsing).
• You’re migrating from older Filament versions and need to audit deprecated patterns.

Look elsewhere if:

• You’re using Filament v3 or earlier (unsupported).
• Your team prefers manual code reviews over automated tooling.
• You need deep performance profiling (consider Laravel Telescope or Blackfire instead).
• Your project is small-scale with no CI pipeline (manual runs are cumbersome).
• You require custom rule sets beyond Filament’s scope (e.g., Laravel-specific rules → use Laravel Pint or Pest).

How to Pitch It (Stakeholders)

For Executives: "FilaCheck is a no-code static analyzer for our Filament admin panels—like a spellcheck for deprecated APIs. It catches breaking changes (e.g., reactive() → live()) automatically in CI, saving dev time and reducing tech debt. For $0 (free tier) or a small investment (Pro tier), we can enforce best practices at scale, especially as we adopt AI tools. This aligns with our goal to [reduce bugs/improve velocity] while keeping Filament up-to-date."

For Engineers: *"This is Pint for Filament—run it in CI to block deprecated patterns before they hit production. Key perks:

• 16 free rules (e.g., deprecated-action-form, deprecated-reactive) with auto-fix for most.
• Dirty-mode (--dirty) to scan only changed files, like Laravel Pint.
• Pro version adds security/performance rules (e.g., N+1 query detection in formatStateUsing).
• Zero config to start; publish config later to disable rules. Example: vendor/bin/filacheck --dirty --fix auto-updates deprecated ->form() to ->schema() in PRs. CI integration: 5-minute setup for GitHub Actions (see template)."*

For PMs: *"This tool reduces Filament tech debt by surfacing deprecated APIs early. Prioritize:

1. CI integration (block merges with violations).
2. Pro tier if security/performance is critical (e.g., file-upload-missing-accepted-file-types).
3. Auto-fix for low-risk rules (e.g., deprecated-view-property) to save dev time. Tradeoff: Free tier covers 16 rules; Pro adds 19 (justify with audit findings)."*