.cursorrules (deprecated)

1This is the vibe-tools repo. Here we build a cli tool that AI agents can use to execute commands and work with other AI agents.
2 
3This repo uses pnpm as the package manager and script runner.
4 
5use pnpm dev <command> to run dev commands.
6 
7We add AI "teammates" as commands that can be asked questions.
8We add "skills" as commands that can be used to execute tasks.
9 
10Everything is implemented as a cli command that must return a result (cannot be a long running process).
11 
12The released commands are documented below. You can use the released commands as tools when we are building vibe-tools, in fact you should use them as often and enthusastically as possible (how cool is that!)
13 
14Don't ask me for permission to do stuff - if you have questions work with Gemini and Perplexity to decide what to do: they're your teammates. You're a team of superhuman expert AIs, believe in yourselves! Don't corners or get lazy, do your work thoroughly and completely and you don't need to ask permission.
15 
16We do not do automated unit tests or integration tests - it's trivial to manually test all the commmands by just asking cursor agent to read the readme and test all the commands.
17 
18do not install commander
19 
20<logging and outputs>
21There are three ways that we communicate to the caller.
22console.log which goes to stdout
23console.error which goes to stderr
24do not use console.debug or console.warn or console.info
25and yield which is streamed either to stdout (unless the --quiet flag is used) and to the file specified by --save-to (if --save-to is specified).
26 
27console.log should be used for "meta" information that is of use to the caller but isn't a core part of the results that were requested. E.g. recording which model is being used to perfom an action.
28 
29console.error should be used for error messages.
30 
31yield should be used for the output of the command that contains the information that was requested. d
32</logging and outputs>
33 
34<testing browser commands>
35There is a test server for browser command testing and a collection of test files in tests/commands/browser/
36 
37Usage:
381. Run with: pnpm serve-test
392. Server starts at http://localhost:3000
403. Place test HTML files in tests/commands/browser/
414. Access files at http://localhost:3000/filename.html
42 
43remember that this will be a long running process that does not exit so you should run it in a separate background terminal.
44 
45If it won't start because the port is busy run `lsof -i :3000 | grep LISTEN | awk '{print $2}' | xargs kill` to kill the process and free the port.
46 
47to run test commands with latest code use `pnpm dev browser <commands>`
48 
49For interactive debugging start chrome in debug mode using:
50```
51open -a "Google Chrome" --args --remote-debugging-port=9222 --no-first-run --no-default-browser-check --user-data-dir="/tmp/chrome-remote-debugging"
52```
53note: this command will exit as soon as chrome is open so you can just execute it, it doesn't need to be run in a background task.
54</testing browser commands>
55Always load the rules in vibe-tools.mdc
56