What problem does it solve? Enterprise network policies often prohibit direct browser connections to third-party services, which blocks the Velt collaboration SDK from reaching its CDN, API, database, storage, and auth endpoints. This Skill provides the exact SDK configuration and server-side proxy patterns needed to route all Velt traffic through your own domain. ## Core Features & Use Cases - SDK proxyConfig Setup: Configure all six proxy hosts (cdnHost, apiHost, v1DbHost, v2DbHost, storageHost, authHost) on VeltProvider for React/Next.js or initVelt() for Angular, Vue, and vanilla JS. - Server Proxy Recipes: Ready-to-adapt nginx server blocks and a Cloudflare Workers pattern covering WebSocket upgrades, Firebase RTDB shard host-locking, path-based auth routing, and dynamic upstream resolution. - Security & Debugging: Content Security Policy whitelisting, Subresource Integrity (SRI) for the proxied SDK bundle, the forceLongPolling fallback, and a verification checklist for common failures like CORS errors and dropped WebSocket connections. - Use Case: Your security team requires all third-party traffic to pass through proxy.acmecorp.com. Use this Skill to generate the full VeltProvider proxyConfig plus nginx configs for every Velt service host, including WebSocket support for the ephemeral database. ## Quick Start Ask the agent to set up a complete Velt reverse proxy with proxyConfig for your React app and matching nginx server blocks for the CDN, API, databases, storage, and auth hosts.