Skip to content

Commit f9f18be

Browse files
committed
Update AGENTS.md to avoid running the dev server to prevent conflicts
1 parent cfe4466 commit f9f18be

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

AGENTS.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,39 @@ pnpm lint
7272

7373
This ensures all code follows the project's formatting standards, type safety requirements, and linting rules, preventing issues in pull requests.
7474

75+
### CRITICAL: Never Run Dev Servers
76+
77+
**DO NOT run development servers (e.g., `npm run dev`, `pnpm dev`, `next dev`) as they will conflict with other running instances.**
78+
79+
#### Why This Rule Exists:
80+
- Dev servers run indefinitely and block the terminal session
81+
- Multiple instances on the same port cause conflicts
82+
- The application may already be running in the user's environment
83+
- Long-running processes make the conversation hang for the user
84+
85+
#### Commands to AVOID:
86+
```bash
87+
# DO NOT RUN THESE:
88+
npm run dev
89+
pnpm dev
90+
next dev
91+
npm start
92+
pnpm start
93+
yarn dev
94+
node --watch
95+
nodemon
96+
```
97+
98+
#### What to Do Instead:
99+
1. **Testing changes**: Use `pnpm build` to verify the production build works
100+
2. **Type checking**: Use `pnpm type-check` to verify types
101+
3. **Linting**: Use `pnpm lint` to check code quality
102+
4. **Running tests**: Use `pnpm test` if tests are available
103+
5. **If the user needs to test**: Let the user run the dev server themselves
104+
105+
#### Exception:
106+
If the user explicitly asks you to start a dev server, politely explain why you cannot do this and suggest they run it themselves instead.
107+
75108
### Logging Best Practices
76109

77110
1. **Use descriptive static messages**

0 commit comments

Comments
 (0)