agentleFS
Sign inStart free
jackson2wjackson2w/claude-code-skills/filament-panel-theming/SKILL.md

filament-panel-theming

Skill1 starsChanged 9 days agoNo licenceView on GitHub

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".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free