Setting up proper feedback loops is crucial for Claude to validate it’s work, so I put together some things that have yielded great results, particularly when leveraging worktrees for parallel development. it’s baked in a workflow here https://github.com/reliant-labs/reliant/blob/main/examples/workflows/env-setup.yaml#L71 , but you can just copy out the system prompt to use with Claude or whatever harness you prefer The gist is: Sets up dynamic port allocation so you can run multiple processes simultaneously, with global reservation mechanism Ensures the database is namespace based Looks to setup hot reloading as possible for whatever language the project is in. Process naming by worktree name (this helps when claude tries to pkill the process, but whacks processes from other worktrees) looks to integrate with existing process management tools (package.json, makefile, etc) redirect all logs including browser logs to a local file in the ephemeral directory creates an ephemeral directory and a start/stop script that writes this info out to that dir so claude can look it up on demand. Adds all of the above info to a memory file so claude knows exactly where to look for things. Now claude can run the app in parallel with other instances in different worktrees, know which ports are relevant, and how to query the endpoints, spin up a chrome or playwright mcp, and query the database to validate results. submitted by /u/reliant-labs
Originally posted by u/reliant-labs on r/ClaudeCode