hot-reload

Watch source files with chokidar to rebuild Astro frontends and reload uvicorn backends.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/krazyuniks/guitar-tone-shootout-archive --skill hot-reload
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hot-reload
Source: https://github.com/krazyuniks/guitar-tone-shootout-archive/tree/main/.claude/skills/hot-reload
Command: npx skills add https://github.com/krazyuniks/guitar-tone-shootout-archive --skill hot-reload

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill documents and guides reliable hot-reload behavior during development, enabling automatic rebuilds when source files change and keeping frontend and backend in sync.

Core Features & Use Cases

  • Automatic frontend rebuilds: Watches for changes in frontend sources and regenerates assets ready for serving.
  • Backend auto-reload: Keeps Python server fresh with file changes without manual restarts.
  • Seamless templates: Jinja2 templates auto-refresh as changes are requested.

Quick Start

  • Terminal 1: Start services with just up-d
  • Terminal 2: Start file watching for templates with just watch-templates (REQUIRED for frontend hot reload)

Frequently Asked Questions about hot-reload

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

FAQPage Schema
How do I set up hot-reload for an Astro frontend and Python backend?

Automating hot-reload watches src/ and static assets via chokidar to trigger Astro builds, while uvicorn --reload handles Python backend updates and Jinja2 templates refresh automatically on request.

Why do I need to run watch-templates separately for frontend hot reload?

You must run watch-templates separately in a second terminal because it activates the chokidar file watcher required to monitor source files and trigger Astro builds for frontend hot reload.

How does Jinja2 template hot-reload work with uvicorn?

Jinja2 templates automatically refresh as changes are requested, while uvicorn --reload keeps the Python backend fresh by detecting file modifications and reloading the server without manual restarts.

Does this hot-reload setup work with nginx serving updated assets?

Yes, the hot-reload workflow integrates with nginx serving updated assets, delivering the rebuilt Astro distributions from astro/dist and refreshed static files directly through the nginx server.

What's the best way to keep frontend builds and backend servers in sync during development?

Automating hot-reload behavior keeps frontend builds and backend servers in sync by using chokidar to trigger Astro builds and uvicorn --reload for Python code whenever source files change.