UI Development Server

VerifiedSafe

Starts the Vite/React development server with hot module replacement. Supports multiple environments (development, staging, production, e2e) and custom ports. Useful for rapid frontend development and testing with real-time updates.

Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#ui-development#vite#react#hot-reload#dev-server

Recommended for

Automated summary

Starts a React/Vite development server with hot module replacement (HMR) and support for different modes (development, staging, production, E2E).

Strengths

  • Quick startup with HMR for responsive development
  • Support for multiple environments via flags (--staging, --prod, --e2e)
  • Ability to expose the server to the network with --host
  • Pre-flight checks (node_modules, port availability, environment files)

Limitations

  • Requires a specific project structure (services/ui/)
  • Depends on Node.js and npm to run
  • Port or API connection issues may require manual intervention
When to use it

When developing UI features and need a local development server with live reload.

When not to use it

When you want to build a production version or deploy the application, as this skill is for development only.

Security analysis

Safe
Quality score90/100

The skill executes npm run dev commands within the project directory, which is a typical development task. There are no risky operations such as downloading external scripts, extracting secrets, or destructive actions.

No concerns found

How this analysis is made

Examples

Start default dev server
/ui-dev
Start with staging API
/ui-dev --staging
Start on custom port and expose to network
/ui-dev --port 3001 --host

name: ui-dev description: Start UI development server with hot reload argument-hint: "[--staging|--prod|--e2e|--port]"

UI Development Server

Start the React/Vite development server with hot module replacement.

Usage

  • /ui-dev - Start dev server (default: development mode)
  • /ui-dev --staging - Start with staging API config
  • /ui-dev --prod - Start with production API config
  • /ui-dev --e2e - Start in E2E test mode
  • /ui-dev --port 3001 - Custom port
  • /ui-dev --host - Expose to network

Tech Stack

  • Vite - Build tool and dev server
  • React 18 - UI framework
  • TypeScript - Type safety
  • Tailwind CSS - Styling
  • React Query - Data fetching
  • Zustand - State management

Project Structure

services/ui/
├── src/
│   ├── components/      # Shared components
│   │   ├── ui/          # Base UI components (button, card, etc.)
│   │   ├── charts/      # Chart components
│   │   └── common/      # Common components
│   ├── features/        # Feature modules
│   │   ├── trading-terminal/
│   │   ├── command-center/
│   │   ├── research/
│   │   └── ...
│   ├── contexts/        # React contexts
│   ├── hooks/           # Custom hooks
│   ├── api/             # API client
│   └── pages/           # Page components
├── vite.config.ts
├── tailwind.config.js
└── package.json

Instructions

When this skill is invoked:

  1. Parse arguments:

    • No args: npm run dev (development mode)
    • --staging: npm run dev:staging
    • --prod: npm run dev:prod
    • --e2e: npm run dev:e2e
    • --port N: Add -- --port N
    • --host: Add -- --host
  2. Pre-flight checks:

    • Verify node_modules exists (suggest npm install if missing)
    • Check if port 5173 is available
    • Verify environment files exist
  3. Start dev server:

    cd services/ui
    npm run dev $MODE_FLAG
    
  4. Display server info:

    UI Development Server
    ═══════════════════════════════════════════════════════════
    
    Mode:     development
    Local:    http://localhost:5173
    Network:  http://192.168.1.100:5173
    
    API:      http://localhost:8000
    WebSocket: ws://localhost:8000/ws
    
    Ready in 1.2s
    
    Press Ctrl+C to stop
    
  5. Common issues:

    • Port in use: Kill existing process or use --port
    • Module not found: Run npm install
    • API connection failed: Ensure backend is running (/deploy-dev)
    • TypeScript errors: Run /ui-lint --typecheck

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/ui-development-server-mmlj2op0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/ui-development-server-mmlj2op0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ui-development-server-mmlj2op0/download' --output '.skill-downloads/ui-development-server-mmlj2op0/SKILL.md.part' && mv '.skill-downloads/ui-development-server-mmlj2op0/SKILL.md.part' '.skill-downloads/ui-development-server-mmlj2op0/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/ui-development-server-mmlj2op0/SKILL.md' && test -s '.skill-downloads/ui-development-server-mmlj2op0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ui-dev' && cp -R '.skill-downloads/ui-development-server-mmlj2op0' '.claude/skills/ui-dev'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/ui-development-server-mmlj2op0'

openskills read 'ui-development-server-mmlj2op0'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/ui-development-server-mmlj2op0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills