podverse/lighthouse-env-alignment
.cursor/skills/lighthouse-env-alignment/SKILL.md
Keeps Lighthouse env handling aligned with apps/api and apps/web startup validation. Use when changing Lighthouse env loading, .env.api/.env.web examples, or app validation requirements.
$ install --global
skillsauthnpx skillsauth add podverse/podverse lighthouse-env-alignmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:48 PM5.7s1 file scanned
SKILL.md
- name:
- lighthouse-env-alignment
- description:
- Keeps Lighthouse env handling aligned with apps/api and apps/web startup validation. Use when changing Lighthouse env loading, .env.api/.env.web examples, or app validation requirements.
Lighthouse Env Alignment
Purpose
Lighthouse runs the API and web apps for testing. Its env files must stay aligned with app startup validation:
apps/api/src/lib/startup/validation.tsapps/web/scripts/validate-env.ts
Rules
- No defaults in Lighthouse managers:
ApiManagerandWebAppManagermust passprocess.envthrough without hardcoded defaults. - Env files are split:
.env.apifor API,.env.webfor web. - App validation is authoritative: if app validation changes, update
.env.api.example/.env.web.exampleand docs.
Files to Update When Validation Changes
tools/web-perf/lighthouse/.env.api.exampletools/web-perf/lighthouse/.env.web.exampletools/web-perf/lighthouse/TOOLS-WEB-PERF-LIGHTHOUSE.mdtools/web-perf/lighthouse/.env.lighthouse.example
Notes
- Keep
.envformatting consistent (double quotes for non-empty values). - Use Lighthouse docker env values from
tools/web-perf/lighthouse/docker/env/db.env. - When app/env validation changes in
apps/apiorapps/web, update the Lighthouse examples and re-check the Lighthouse startup flow.
Related Skills
podverse/podverse-workers-patterns
documentation
VerifiedTrustedCommunity
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.
4SKILL.mdUpdated Apr 16, 2026
podverse/podverse-web-patterns
development
VerifiedTrustedCommunity
Common patterns and examples for the podverse-web Next.js application
4SKILL.mdUpdated Apr 16, 2026
podverse/time-format-local
tools
VerifiedTrustedCommunity
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.
4SKILL.mdUpdated Apr 16, 2026
podverse/.cursor/skills/testing-policy
testing
VerifiedTrustedCommunity
--- 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
4SKILL.mdUpdated Apr 16, 2026