trent-local-server-prod_skill

Overview

This skill deploys a local development environment that points to the production configuration (DECAGON_ENV=prod). It launches backend and frontend processes in separate tmux panes so you can run, test, and iterate locally while targeting production resources. The original tmux pane stays available for other commands.

How this skill works

The skill automates splitting the current tmux window into three panes and runs the backend and frontend dev servers with DECAGON_ENV=prod. It installs backend Python requirements and starts uvicorn with reload enabled, and starts the Next.js frontend dev server with yarn. Pane IDs are captured and used to send commands reliably.

When to use it

• You need to test local changes against production services or data.
• You want to run backend and frontend concurrently while pointing both to prod.
• You need hot-reload backend while evaluating production environment behavior.
• You prefer using tmux to manage persistent panes for dev workflows.
• You must keep an interactive pane available for debugging or auxiliary commands.

Best practices

• Run this from the project root so relative paths (backend/, frontend/) resolve correctly.
• Ensure tmux is installed and you are inside a tmux session before running pane-splitting commands.
• Verify credentials and access to production resources are appropriate and safe for local testing.
• Use the original pane for monitoring logs, running migrations, or running one-off commands.
• Stop services and clean up panes when finished to avoid accidental prod-side effects.

Example use cases

• Reproduce a production-only bug locally while using production data endpoints.
• Validate frontend behavior when backend is served with production configuration.
• Develop backend fixes with hot reload while keeping the frontend connected to prod.
• Run quick integration checks after a change to configuration that only affects prod.