jmilinovich

Set up a fresh Ubuntu VPS for web development with Node.js, Python, Nginx, PM2, SSL, and security hardening. Use when setting up a new server, configuring web hosting, deploying apps, or helping users create a development playground server.

Evaluate, improve, and write tests using a signal-over-coverage philosophy. Use this skill whenever the user asks to write new tests, audit or improve an existing test suite, diagnose flaky or brittle tests, decide whether a test is worth keeping, review test PRs, or work out how many tests a feature needs. Also trigger when the user mentions "test coverage," "unit vs integration," "mocks," "test smells," "parametrize," "table-driven tests," or expresses frustration with tests being brittle, slow, or uninformative. Applies to any language, with Python/pytest examples.

DRAFT reliability protocol for the OFFICIAL remote Figma MCP (mcp.figma.com via the Claude Code plugin, mcp__plugin_figma_figma__*). Makes the non-deterministic use_figma write / round-trip pipeline repeatable: skill-gating, plan/file setup, one-wrapper-per-call section building (never reparent across calls), serialized (never parallel) library builds, small op-batches that return node IDs not payloads, font + color + image discipline, and per-call screenshot/metadata self-validation with atomic retry-after-fix. Use BEFORE any use_figma / generate_figma_design / upload_assets write, when a write "succeeded" but the canvas is wrong, when a build orphaned nodes, or when a library build is flaky.