filament-pro

marcelorodrigo/agent-skills · updated May 26, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/marcelorodrigo/agent-skills --skill filament-pro
0 commentsdiscussion
summary

Build powerful Laravel admin panels using Filament v5's server-driven UI with Schemas and Livewire v4 reactivity.

skill.md

Filament v5

Build powerful Laravel admin panels using Filament v5's server-driven UI with Schemas and Livewire v4 reactivity.

Overview

Filament v5 is a Laravel admin panel framework that provides complete CRUD interfaces, forms, tables, and dashboard components through a declarative PHP API. Built on Livewire v4, it offers real-time reactivity without writing JavaScript.

Key Concepts

  • PanelProvider: Central configuration class defining your admin panel
  • Resources: Automatic CRUD interfaces for Eloquent models
  • Schemas: Declarative UI components (forms, tables, infolists)
  • Actions: Interactive buttons with modals and backend logic
  • Widgets: Dashboard components for data visualization

System Requirements

  • Laravel 11.28+
  • PHP 8.2+
  • Livewire v4
  • Node.js 18+
  • Tailwind CSS v4.1+

Installation

Install Filament via Composer and scaffold a panel:

composer require filament/filament:"^5.0" -W
php artisan filament:install --scaffold
npm install && npm run dev
php artisan make:filament-user

This creates the panel provider, directory structure, and assets needed to start building.

Directory Structure

app/
  Filament/
    Resources/          # CRUD resources with forms and tables
    Pages/              # Custom pages
    Widgets/            # Dashboard widgets
  Providers/
    Filament/
      AdminPanelProvider.php

Core Concepts

Panel Configuration

The PanelProvider is the entry point for your admin panel. It configures:

  • Identity: ID, path, branding (name, logo, colors)
  • Discovery: Auto-discovery of resources, pages, and widgets
  • Middleware: Session, authentication, and custom middleware
  • Tenancy: Multi-tenant configuration for SaaS applications

Resources

Resources provide complete CRUD interfaces through:

  • Forms: Schema-based forms with 20+ field types (TextInput, Select, DatePicker, FileUpload, RichEditor, etc.)
  • Tables: Data tables with columns, filters, sorting, and actions
  • Pages: Automatic generation of List, Create, Edit, and View pages
  • Relations: Relation managers for handling model relationships

Forms

Forms use a schema-based approach where you declare fields as PHP objects:

  • Input Fields: Text, select, checkbox, toggle, date/time pickers
  • Media: File and image uploads with validation
  • Complex Fields: Rich text editors, repeaters, builders
  • Layout: Grids, sections, tabs, and wizards
  • Validation: Built-in Laravel validation rules

Tables

Tables display data with extensive customization:

  • Columns: Text, badges, icons, images, colors
  • Filters: Select, ternary, and custom filter logic
  • Actions: Per-row actions, bulk actions, header actions
  • Features: Search, sorting, pagination, grouping

Actions

Actions are interactive buttons that trigger:

  • Modals: Form dialogs for data collection
  • Confirmation: Destructive action confirmation
  • Wizards: Multi-step processes
  • Notifications: User feedback after completion

Widgets

Dashboard widgets include:

  • Stats Overview: Metric cards with trends and sparklines
  • Charts: Line, bar, pie charts using Chart.js
  • Tables: Data tables for recent records

Testing

Filament uses Pest PHP with Livewire testing helpers:

  • Page Testing: List, create, edit, view page functionality
  • Form Testing: Validation, state management, submission
  • Table Testing: Search, filters, sorting, actions
  • Authorization Testing: Access control and permissions

Authorization

Access control through:

  • Panel Access: FilamentUser contract for panel-level access
  • Policies: Laravel policies for resource-level permissions
  • Field Visibility: Show/hide fields based on user roles
  • Multi-Tenancy: Tenant isolation for SaaS applications

Architecture Patterns

Server-Driven UI

Filament uses a server-driven approach where the backend defines the UI structure through schemas. The PHP code describes forms, tables, and layouts which Filament renders as Livewire components.

Schema System

Schemas are PHP configuration objects that define:

  • Form fields and their validation rules
  • Table columns and their formatting
  • Layout containers (grids, sections, tabs)
  • Action definitions and their behavior

Livewire Integration

All components mount as Livewire components, providing:

  • Real-time reactivity without page reloads
  • Automatic state management
  • Event handling and AJAX updates
  • Form validation with instant feedback

Resource-First Design

The framework encourages a resource-first approach:

  1. Define your Eloquent models
  2. Create resources that map to those models
  3. Configure forms and tables for each resource
  4. Add actions and widgets as needed

Command Reference

Command Purpose
filament:install --scaffold Install Filament with panel scaffolding
make:filament-resource Create CRUD resource
make:filament-page Create custom page
make:filament-widget Create dashboard widget
make:filament-panel Create additional panel
make:filament-user Create admin user
make:filament-relation-manager Create relation manager
filament:cache-components Cache for production

Detailed Documentation

Reference Guides

Comprehensive documentation for each component:

  • Forms - All form components, validation rules, layouts, and conditional logic
  • Tables - Column types, filters, actions, and table configuration
  • Resources - CRUD resources, relation managers, infolists, and global search
  • Infolists - Read-only data display components (TextEntry, ImageEntry, IconEntry)
  • Widgets - Stats overview, charts, and table widgets
  • Actions - Modal actions, notifications, action groups, and wizards
  • Notifications - Flash messages, database, and broadcast notifications
  • Schemas - Schema system, layouts, and component organization
  • Testing - Pest testing patterns for resources, forms, tables, and authorization
  • Authorization - Access control, policies, roles, and multi-tenancy

Code Examples

See examples.md for complete working code examples including:

  • Complete resource implementations
  • Form configurations
  • Table setups
  • Widget configurations
  • Test suites
  • Authorization patterns

Best Practices

Performance

  • Use getEloquentQuery() to eager load relationships and prevent N+1 queries
  • Enable component caching in production with filament:cache-components
  • Limit pagination options and use deferred loading for large datasets
  • Cache expensive calculations in widgets

Security

  • Always implement the FilamentUser contract for panel access control
  • Use Laravel policies for resource-level authorization
  • Validate all input with appropriate form rules
  • Never skip authorization in production environments
  • Implement proper tenant isolation for multi-tenant applications

Code Organization

  • Organize by feature: app/Filament/Admin/Resources/
  • Extract complex forms and tables to separate classes
  • Create reusable form components for common patterns
  • Keep resources focused on single responsibility
  • Use dedicated pages for non-CRUD functionality

Testing

  • Test all CRUD operations for each resource
  • Validate form validation rules with multiple scenarios
  • Test table features: search, filters, sorting, actions
  • Verify authorization with different user roles
  • Use factories to create realistic test data

When to Use Filament

Filament is ideal for:

  • Admin Panels: Back-office interfaces for managing application data
  • CMS: Content management systems with rich editing capabilities
  • CRM: Customer relationship management tools
  • E-commerce: Product, order, and inventory management
  • SaaS Applications: Multi-tenant admin interfaces
  • Internal Tools: Business process management and data entry

Additional Resources


Version: 1.0.0
License: MIT
Compatibility: Laravel 11+, PHP 8.2+, Livewire v4

how to use filament-pro

How to use filament-pro on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add filament-pro
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/marcelorodrigo/agent-skills --skill filament-pro

The skills CLI fetches filament-pro from GitHub repository marcelorodrigo/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/filament-pro

Reload or restart Cursor to activate filament-pro. Access the skill through slash commands (e.g., /filament-pro) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.562 reviews
  • Ama Thompson· Dec 28, 2024

    Keeps context tight: filament-pro is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kaira Thompson· Dec 20, 2024

    Useful defaults in filament-pro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Zara Ghosh· Dec 16, 2024

    We added filament-pro from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sakura Patel· Dec 16, 2024

    Keeps context tight: filament-pro is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ama Martinez· Dec 12, 2024

    filament-pro reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chaitanya Patil· Dec 4, 2024

    filament-pro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Noah Martinez· Dec 4, 2024

    filament-pro reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kabir Rao· Dec 4, 2024

    Registry listing for filament-pro matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Piyush G· Nov 23, 2024

    filament-pro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aanya Flores· Nov 23, 2024

    Keeps context tight: filament-pro is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 62

1 / 7