.cursor/skills/lighthouse-docker-sync/SKILL.md
Keeps Lighthouse Docker compose/env files aligned with infra Docker changes. Use when editing infra docker-compose files, docker envs, or scripts that Lighthouse services depend on.
npx skillsauth add podverse/podverse lighthouse-docker-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Lighthouse owns its own Docker services under tools/web-perf/lighthouse/docker.
When infra Docker definitions or scripts change, ensure the Lighthouse copies stay aligned.
tools/web-perf/lighthouse/docker/docker-compose.yml when DB/MQ/KeyvalDB
images, commands, volumes, or ports change in infra.tools/web-perf/lighthouse/docker/env/*.env when infra env files change.tools/web-perf/lighthouse/docker/docker-compose.ymltools/web-perf/lighthouse/docker/env/db.envtools/web-perf/lighthouse/docker/env/mq.envtools/web-perf/lighthouse/docker/env/keyvaldb.envdocumentation
Per-job env validation and config patterns for the workers app. Use when adding or changing worker commands, touching workers startup validation, or documenting worker env vars.
development
Common patterns and examples for the podverse-web Next.js application
tools
Ensures client-side time displays use formatDateTimeAbbrev for localized, readable timestamps. Use when rendering dates/times in the UI or when the user mentions time formatting or local timezone display.
testing
--- name: podverse-testing-policy description: Skip test implementation unless the user explicitly asks. Use when a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". version: 1.0.0 --- # Testing policy — skip tests for now ## When to use - When a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". - When deciding whether to implement tests for a feature. ## Rules 1. **We are not concerning ourselves with tests at this time.** Skip test imp