From proxmox-manager
Skill for building and maintaining a CLAUDE.md tailored to a Proxmox-hosted Ubuntu VM. Guides the user through environment discovery and produces a ready-to-use context file.
npx claudepluginhub danielrosehill/proxmox-manager-pluginThis skill uses the workspace's default tool permissions.
This skill helps the user create and maintain a `CLAUDE.md` file that gives Claude accurate context about their Proxmox-hosted Ubuntu VM. A well-written `CLAUDE.md` makes all other commands and agents in this plugin work much more effectively.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
This skill helps the user create and maintain a CLAUDE.md file that gives Claude accurate context about their Proxmox-hosted Ubuntu VM. A well-written CLAUDE.md makes all other commands and agents in this plugin work much more effectively.
A good CLAUDE.md for a Proxmox-hosted VM should include:
What the server does — its primary function (e.g. Docker host, backup runner, media server, development environment).
The /proxmox-setup command produces a completed version of this template based on the user's answers. The template structure is:
# Server Context
## Role
<server purpose>
## Virtualisation
- Proxmox host: <hostname>
- VMID: <vmid>
- Other VMs on host: <list>
## Hardware
- CPU: <model> (<n> vCPUs)
- RAM: <amount>
- GPU: <model> (passthrough: yes/no)
- Storage: <config> (<filesystem>)
## Network
- LAN: <subnet>
- Gateway: <ip>
- This server: <ip>
- NAS: <ip>
- <other hosts>: <ip>
- External access: Cloudflare Tunnel / reverse proxy / <method>
## Key Directories
- Docker deployments: <path>
- Backup data: <path>
## Active Services
- <service>: <description>
- ...
## Administrative Notes
- Deployment pattern: atomic (one repo per service)
- Backup tools: <list>
- ...