holix-studio-frontend-backend

Solid

Wire frontend API base to the real Holix Studio backend public origin when both apps run in Studio. Use when building or fixing SPA/API monorepos, Vite/Next/React + FastAPI/Express, or any FE that calls a BE on another Studio preview port. Invoke via /holix-studio-frontend-backend.

Web & Frontend 11 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

## When to use You are in **Holix Studio** and the project has (or will have) **both**: - a **frontend** (Vite, Next, CRA, static SPA, etc.) on one listen port - a **backend** API (FastAPI, Express, Django, …) on another listen port Apply this skill **before** telling the user the app is ready, and whenever the frontend still points at `localhost` after both services are up. ## Goal The browser loads the frontend from Studio’s **public** preview URL (H2 subdomain or path proxy). From that browser context, `http://localhost:8000` is **the user’s machine**, not the Studio host. API calls must use the backend’s **real Studio public origin**. ## Mandatory workflow 1. Start backend and frontend under the **profile workspace** (`start_background_process` / project scripts). Keep the **project’s configured ports** (do not invent random ports). 2. Wait until both are healthy (listen + health check). 3. Resolve public origins via built-in MCP **`holix_studio`** (tools appear as `mcp_holix_studio_*`): - `open_preview_url(port=…)` for each service (user Browser + registers H2 when enabled) - `preview_origins` — map `port → origin` for the whole profile - `resolve_preview_origin_tool(port=BACKEND_PORT)` — single backend origin + siblings 4. Set the **frontend** API base to the **backend** `origin` from that response (not localhost). 5. If the backend enforces CORS, allow the **frontend** public origin (from `origins` / `open_preview_url` for the FE port). 6. Restart the f...

Details

Author
javded-itres
Repository
javded-itres/Holix
Created
1 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

fastreact

Scaffold and build a full-stack web app: FastAPI backend (Python, uv, SQLModel, Postgres, Alembic, JWT + Google OAuth, boto3/S3) + React frontend (Vite, TypeScript, shadcn/ui + Tailwind, TanStack Router/Query/Table, Zod, Axios), wired with Docker Compose. Use this skill whenever the user wants to spin up, bootstrap, create, or design a new full-stack webapp; an API-first backend + SPA frontend; an admin/portal/dashboard app; file upload + S3; RBAC / role-based auth with seeded test users; local docker dev; or asks for a 'FastAPI + React' / 'Python + React' project. Runs mockup-first: marketing-design (brand/logo raster) + opendesign (HTML page mockups) before code, then ports the design to Tailwind/shadcn. Covers project structure, local setup, auth/RBAC, S3 uploads, and the gotchas that break these stacks.

2 Updated today
vanducng
Web & Frontend Listed

dev-frontend

Use when a frontend change must be implemented or refactored across UI, state, data, styling, build/tooling, accessibility, performance, or desktop integration; owns source edits and validation, not audit-only, browser-only, UI-spec, or Git-delivery work.

2 Updated today
idaibin
API & Backend Listed

backend-build

Implement the backend from a BACKEND_DESIGN.md brief — set up plugins, database, routes, tests, and wire everything into the server entry. Biased toward Fastify + Node. Use when user says "build the backend", "implement the server", "code the API from the brief", or after running /backend-design.

0 Updated 2 days ago
muzalee