reflex-process-management — Claude Code skill: run and reload Reflex
A skill that walks the agent through compiling, running and reloading a Reflex app: build check, production server, process lookup by port, logs.
npx skills add reflex-dev/agent-skills --skill reflex-process-management -a claude-codeWhat reflex-process-management does
The skill spells out how an agent should handle Reflex app processes. First comes a build check: reflex compile --dry catches syntax, import and component errors without starting a server. Handy right after edits.
Running happens in production mode with output captured to a log: reflex run --env prod --single-port 2>&1 | tee reflex.log. There is no hot reload in that mode, so code changes only land after a stop and a fresh start. Reloading is broken into steps: read the port from the line in reflex.log instead of assuming one, then locate the process with lsof -i :<port> -sTCP:LISTEN -t. The -sTCP:LISTEN flag matters — it filters out browser connections, and without it you can kill the user's browser. If lsof is missing, the skill falls back to ss -tlnp | grep :<port> or fuser <port>/tcp. Then SIGINT, SIGTERM if needed, truncate the log, start again.
When a user reports an error, the skill sends the agent to reflex.log. You need Reflex itself plus a port tool on the machine: lsof, ss or fuser.
What it helps with
- check that a Reflex app compiles without errors
- start a production server and capture output to a log
- find the app process by port and restart it
- diagnose a failure from the contents of
reflex.log - avoid killing the browser while hunting the listening process
Example prompts for the agent
- check that the app compiles with reflex compile --dry
- run Reflex in production mode and write the log to reflex.log
- reload the Reflex app: find the process by port and restart it
How to install reflex-process-management
1Skills CLI (Vercel)
npx skills add reflex-dev/agent-skills --skill reflex-process-management -a claude-code2Manually: put the files in place
~/.claude/skills/reflex-process-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/reflex-process-management/
1Skills CLI (Vercel)
npx skills add reflex-dev/agent-skills --skill reflex-process-management -a codex2Manually: put the files in place
.agents/skills/reflex-process-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reflex-dev/agent-skills --skill reflex-process-management -a cursor2Manually: put the files in place
.cursor/skills/reflex-process-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reflex-dev/agent-skills reflex-process-management2Manually: put the files in place
.github/skills/reflex-process-management/SKILL.md1Skills CLI (Vercel)
npx skills add reflex-dev/agent-skills --skill reflex-process-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/reflex-dev/agent-skills --path skills/reflex-process-managementManually: put the files in place
.devin/skills/reflex-process-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reflex-dev/agent-skills --skill reflex-process-management -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about reflex-process-management
How do I install reflex-process-management in Claude?
Run npx skills add reflex-dev/agent-skills --skill reflex-process-management -a claude-code. The skill lands in ~/.claude/skills/reflex-process-management/SKILL.md.
What does reflex-process-management do?
It guides the agent through compiling, running in production mode, reloading a running app and reading logs to diagnose errors.
Why does -sTCP:LISTEN matter when reloading?
It keeps only the process listening on the port. Without it browser connections show up too, and you may terminate the wrong one.
