Filament Panel Theming

This skill should be used when applying a custom color palette, self-hosted fonts, or a brand name to a Filament v3 admin panel — anything beyond the stock Tailwind-gray/Inter/Amber default. Covers `php artisan make:filament-theme` recommending the Tailwind v3 CLI instead of Vite when the host app is on Tailwind v4, `->theme()` vs `->viteTheme()`, which Filament surfaces are re-themable via `FilamentColor`/`Color::hex()` versus literal Tailwind colors needing direct CSS overrides on `fi-*` component classes, self-hosting fonts via `LocalFontProvider`, and `->brandName()`. Also covers a second, more specific mixed-content bug than the one in `laravel-filament-proxmox-lxc`: `asset()` not honoring `URL::forceScheme('https')` even after that skill's fix is already in place. Trigger phrases include "skin the filament panel", "filament custom theme", "filament design system", "make:filament-theme", "filament Tailwind v4 conflict", "filament bg-white not themed", "filament dark:bg-gray-900 override", "FilamentColor register", "Color::hex generate palette", "filament LocalFontProvider", "self-hosted fonts filament", "filament brandName", "filament fi-section fi-sidebar override", "asset() secure true", "theme.css http:// mixed content".

mkdir -p ~/.claude/skills/filament-panel-theming
curl -L https://claudskills.com/skills/filament-panel-theming/SKILL.md \
  -o ~/.claude/skills/filament-panel-theming/SKILL.md

@misc{filament-panel-theming-2026,
  author    = {jackson2w},
  title     = {Filament Panel Theming [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/filament-panel-theming/}
}