agentleFS
Sign inStart free
jackson2wjackson2w/claude-code-skills/laravel-filament-proxmox-lxc/SKILL.md

laravel-filament-proxmox-lxc

Skill1 starsChanged 11 days agoNo licenceView on GitHub

This skill should be used when deploying a Laravel + Filament v3 app (an admin panel, internal dashboard, or CMDB) as a native systemd service inside an unprivileged Proxmox LXC, instead of Docker — dedicated PHP-FPM pool, Caddy loopback front, Pest testing, Laravel Boost, Laravel Nightwatch APM, and adding a read-only Sanctum token API for an external consumer. Also covers a Filament panel behind Tailscale Serve generating mixed-content http:// asset URLs on an https:// page (including a plain asset() call not honoring URL::forceScheme), Eloquent's belongsToMany pivot-table naming surprising an agent building the schema by hand, php-fpm socket permission errors from a restrictive service-user home directory, Boost's guideline generation silently doing nothing under --no-interaction, Sanctum's abilities/ability middleware aliases not existing on a bootstrap/app.php (no Kernel.php) app, and an unauthenticated api/* request 500ing instead of 401ing when no Accept header is sent. For theming/skinning an already-deployed panel (custom colors, self-hosted fonts, brand name), see the sibling `filament-panel-theming` skill instead. Trigger phrases include "laravel filament proxmox", "filament admin panel native install", "php-fpm dedicated pool ansible", "laravel behind tailscale serve mixed content", "APP_URL forceScheme https", "asset() secure true mixed content", "eloquent belongsToMany pivot table wrong name", "credential_service vs service_credential", "laravel nightwatch systemd agent", "boost:install no agents selected", "pest --init not pest:install", "php-fpm socket permission denied caddy", "sanctum personal access token read only", "Target class [abilities] does not exist", "sanctum middleware alias missing", "Route [login] not defined api", "unauthenticated api request 500", "redirectGuestsTo bootstrap/app.php", "FilamentUser canAccessPanel api-only user", "APP_DEBUG true production laravel".

  • Reads credentials

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 0 are distinctive, and 7 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.

  • 7

    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