holix-studio-frontend-backend

## When to use (always in Studio) Apply this skill **whenever** you start, fix, or demo a **web** frontend (or FE+API) in Holix Studio: - User asks to run the app, open the UI, “подними фронт”, “запусти preview”, “открой в браузере” - Project has Vite / Next / Nuxt / CRA / static SPA ± API - You are about to say the app is ready This skill is **platform / required**: do not ignore it for Studio web work. ## Non‑negotiable rules 1. **Listen on `0.0.0.0` (never only `127.0.0.1`)** for any process that Studio Preview must reach (Vite/Nuxt `host: '0.0.0.0'`, uvicorn `--host 0.0.0.0`, nginx published port, etc.). 2. **Always form real preview links in chat** after the app listens: - Call MCP **`open_preview_url(port=…)`** (and for FE+BE, for **every** public port users need). - Paste into the chat reply: `frame_url` / public origin from the tool result (Markdown link). - Never tell the user to open `localhost` / bare `host:port` as the main URL. 3. **Prefer docker-compose + nginx** for “run the app” demos: - One **published** port on the host (nginx). - Frontend and backend only on the **compose network** (expose, not host-publish unless needed). - Nginx routes UI + API on the **same origin** (`/` → FE, `/api/` → BE) so the browser does not need a separate API host when possible. 4. **Do not use Desktop / noVNC** for web apps — only **Studio → Browser** via `open_preview_url`. 5. **Do not claim** “preview is ready” without a successful tool result that ...