From xixu-me-skills-3
Sets up, hardens, or reviews Linux cloud servers for secure web hosting: SSH, firewalls, Nginx for static sites or app reverse proxies, DNS, HTTPS via Let's Encrypt/ACME, HTTP redirects, BBR tuning.
npx claudepluginhub joshuarweaver/cascade-ai-ml-engineering --plugin xixu-me-skills-3This skill uses the workspace's default tool permissions.
Use this skill to turn a cloud server into a safely reachable web host
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Use this skill to turn a cloud server into a safely reachable web host without leaning on stale distro-specific memory or outdated Debian-10-era tutorials.
This skill keeps the familiar teaching arc of a beginner-friendly server guide, but turns it into a reusable operator workflow:
Before giving actionable commands, identify the distro family and verify the current package names, service units, config paths, and ACME-client guidance against official documentation for the user's distro and chosen tools.
Open references/workflow-map.md first for the
phase sequence, then open the narrower reference file you need.
Use this skill when the user mentions any of the following:
acme.sh, certificate renewal, or redirecting
HTTP to HTTPSDo not use this skill for:
Start by identifying:
If the distro is unknown, ask for it or have the user inspect /etc/os-release
before giving concrete package or service commands.
Use bundled references for routing, then verify details against live official docs before giving commands that depend on current distro behavior.
Always verify:
If you cannot verify a detail, say so and give high-level guidance instead of pretending the old Debian tutorial path is universal.
Walk through the phases in this order unless the user is explicitly asking for review or remediation of an existing setup:
Do not collapse the static-site branch and reverse-proxy branch into one default answer. Pick the branch that matches the user's goal.
Treat these as hard stop checks:
Always distinguish:
For a fresh setup, provide:
For a hardening or troubleshooting review, provide:
Use references/workflow-map.md for the phase map,
branching logic, and validation order.
Use references/distro-routing.md when distro
family, package manager, firewall tooling, or config layout matters.
Use references/nginx-patterns.md when the user
needs the static-site branch or the reverse-proxy branch.
Use references/security-and-tls.md for SSH
hardening sequence, firewall posture, certificate issuance, renewal, and
redirect timing.