feat: add rule for running multiple Harper dev instances in worktrees#26
Open
stephengoldberg wants to merge 1 commit into
Open
feat: add rule for running multiple Harper dev instances in worktrees#26stephengoldberg wants to merge 1 commit into
stephengoldberg wants to merge 1 commit into
Conversation
Documents the pattern for running parallel Harper dev instances from git worktrees with isolated data roots, loopback addresses, and lock files — covering the failure modes (hot-reload loop, LMDB lock contention, EADDRINUSE) and the wrapper-script architecture that solves them. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
kriszyp
approved these changes
May 1, 2026
Member
kriszyp
left a comment
There was a problem hiding this comment.
This is great. Giving the AI all the hard-earned battle-won tips, and clear direction of the goal.
dawsontoth
requested changes
May 5, 2026
Contributor
dawsontoth
left a comment
There was a problem hiding this comment.
- I think we should put this under a different root skill -- instead of harper-best-practices, something like harper-local-dev. Keeping the two separate will help the downstream places where we utilize these skills.
- The AGENTS.md and SKILL.md needs to reference this rule too.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the pattern for running parallel Harper dev instances from git worktrees with isolated data roots, loopback addresses, and lock files — covering the failure modes (hot-reload loop, LMDB lock contention, EADDRINUSE) and the wrapper-script architecture that solves them.