skills.rest
wesuuu
wesuuuCOMMUNITY
Explore all skills by this author →
GitHub

frontend_dev

Start and coordinate dual Vite dev servers for localhost and Tailscale access.

Updated Feb 19, 2026
Search Tags:#frontend#vite#tailscale#local-development#development-server#script-orchestration
One-click install
npx skills add https://github.com/wesuuu/runbook --skill frontend-dev-wesuuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend_dev
Source: https://github.com/wesuuu/runbook/tree/main/.agent/skills/frontend_dev
Command: npx skills add https://github.com/wesuuu/runbook --skill frontend-dev-wesuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the overhead of manually starting multiple frontend dev servers by automating their startup, ensuring both local and remote accessibility for frontend work.

Core Features & Use Cases

  • Dual-server orchestration: starts two Vite dev servers from the frontend directory for local and Tailscale access.
  • Network routing consistency: API calls are directed to the backend (localhost or Tailscale as described) to mirror production behavior.
  • Flexible workflow: allows running both processes simultaneously with separate terminals or in the background to streamline development.

Quick Start

From the frontend directory, run npm run dev:local to start localhost and npm run dev:tailscale to start the Tailscale server.

Frequently Asked Questions about frontend_dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Vite dev server on both localhost and Tailscale simultaneously?▼

To run dual Vite dev servers, use npm run dev:local for localhost and npm run dev:tailscale for Tailscale access. This automates frontend script orchestration, routing API calls to the backend on port 8000 to mirror production.

What problem does dual Vite server orchestration solve for frontend development?▼

Dual Vite server orchestration reduces the overhead of manually starting multiple frontend dev servers. It ensures both local and remote Tailscale accessibility, maintaining network routing consistency to mirror production behavior.

Do I need a backend running on my Tailscale IP to use the dev:tailscale script?▼

Yes, the dev:tailscale script requires a backend listening on the Tailscale IP for the second Vite instance. Your backend must be reachable at port 8000 to ensure API calls route correctly during local and remote development.

What dependencies are required to start local and Tailscale frontend dev servers?▼

Starting local and Tailscale frontend dev servers requires Node.js and npm installed. Your project must also include the dev:local and dev:tailscale scripts within the frontend directory to execute the dual Vite instances.

Can I run the local and Tailscale Vite development servers in the background?▼

Yes, you can run both Vite development servers in the background or in separate terminals. This flexible workflow streamlines development by allowing the local and Tailscale processes to run simultaneously without blocking.

Related Skills

Explore More Software Engineering Skills→
PytaichukBohdanPytaichukBohdan

Start Orchestrator

Start the Orchestrator 3 Stream backend and frontend in background mode.

Community
Advanced
alsk1992alsk1992
650

tailscale

Manage Tailscale VPN connections to share ports and expose services.

Community
Intermediate
koshimazakikoshimazaki
1

tailscale-runpod

Configure Tailscale mesh VPN for direct SSH access to cloud GPU instances.

Community
Intermediate
ichuanichuan
1

deploy-caddy-reverse-proxy

Deploy Caddy reverse proxy with Let's Encrypt SSL and systemd integration.

Community
Advanced