Cursor rule

1---
2description:
3globs:
4alwaysApply: false
5---
6# Script Kit App Debugging Workflow
7 
8## Log System Overview
9Script Kit app has a comprehensive logging system defined in [logs.ts](mdc:src/main/logs.ts). Logs are written to `~/Library/Logs/ScriptKit/` and organized by component type.
10 
11## Available Log Files
12- `main.log` - Main application logs
13- `term.log` - Terminal/PTY related logs (useful for invoke-pty debugging)
14- `process.log` - Process management logs
15- `script.log` - Script execution logs
16- `error.log` - Error logs across all components
17- `prompt.log` - Prompt-related logs
18- `ipc.log` - Inter-process communication logs
19- And many others (see [logs.ts](mdc:src/main/logs.ts) for the full list)
20 
21## Debugging Process
221. **Ask User to Run Application**: Always ask user to run Script Kit app first
232. **Wait for Confirmation**: User must confirm app is running and they've reproduced the issue
243. **Check Relevant Logs**: Use appropriate log files based on issue type:
25```bash
26   # For terminal/PTY issues
27   tail -n 100 ~/Library/Logs/ScriptKit/term.log
28 
29   # For general application issues
30   tail -n 100 ~/Library/Logs/ScriptKit/main.log
31 
32   # For errors
33   tail -n 100 ~/Library/Logs/ScriptKit/error.log
34```
35 
36## Log Analysis
37Look for:
38- Error messages and stack traces
39- Performance timing information
40- Component-specific debug output
41- PTY pool behavior (for terminal issues)
42 
43## Console Statement Debugging
44- Console statements in fallback logger use stored variables to prevent Biome removal
45- Check [logs.ts](mdc:src/main/logs.ts) fallback logger section for console functionality
46