You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+25-18Lines changed: 25 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,34 +156,41 @@ Since `listRoles` is wrapped in `createServerFn`, TanStack Start will properly h
156
156
157
157
## Development & Build Commands
158
158
159
-
### Use `build` for Testing Build Output
159
+
### Don't Build After Every Change
160
160
161
-
**The `dev` command does not end - it runs indefinitely in watch mode.**
161
+
**Do not run builds after every change, especially for visual changes.**
162
162
163
-
When agents need to test build output or verify that the project builds successfully, use the `build` command instead of `dev`. The `build` command will complete and exit, making it suitable for automated testing and verification.
163
+
This is a visual website, not a library. Assume changes work unless the user reports otherwise. Running builds after every change wastes time and context.
164
164
165
-
### Testing Limitations
165
+
### Debugging Visual Issues
166
166
167
-
**Agents cannot run end-to-end tests without a headless browser.**
167
+
When the user reports something doesn't work or look right:
168
168
169
-
This is a TanStack Start application that requires a browser environment to fully test. Agents can:
169
+
1. Use the Playwright MCP to view the page and debug visually
170
+
2. Use builds (`pnpm build`) only when investigating build/bundler issues
171
+
3. Use TypeScript compilation (`pnpm tsc --noEmit`) for type errors
170
172
171
-
- ✅ Run TypeScript compilation (`pnpm tsc --noEmit`) to check for type errors
172
-
- ✅ Run the build command (`pnpm build`) to verify the project builds successfully
173
-
- ✅ Inspect build output and generated files
173
+
### Use `build` for Build-Specific Issues
174
174
175
-
Agents cannot:
175
+
**The `dev` command does not end, it runs indefinitely in watch mode.**
176
176
177
-
- ❌ Start the dev server and interact with the application (no headless browser)
178
-
- ❌ Test UI functionality or user interactions
179
-
- ❌ Verify runtime behavior in the browser
180
-
- ❌ Test API endpoints that require browser context
177
+
Only use `build` when:
181
178
182
-
For runtime testing and verification, developers should:
179
+
- Investigating bundler or build-time errors
180
+
- Verifying production output
181
+
- The user specifically asks to verify the build
183
182
184
-
1. Review the code changes
185
-
2. Start the dev server manually (`pnpm dev`)
186
-
3. Test the functionality in a browser
183
+
### Testing with Playwright
184
+
185
+
**Use the Playwright MCP for visual debugging and verification.**
186
+
187
+
When debugging issues or verifying visual changes work correctly:
188
+
189
+
- Navigate to the relevant page using Playwright
190
+
- Take snapshots or screenshots to verify the UI
191
+
- Interact with elements to test functionality
192
+
193
+
This is the preferred method for verifying visual changes since this is a visual site.
0 commit comments