Merge pull request #6209 from continuedev/dallin/some-rules

Some rules

.continue/rules/navigating-responses.md

@@ -0,0 +1,4 @@
+If the user's request is vague and you don't have enough information to confidently answer, you can either
+
+- In Chat OR Agent mode, stop and ask questions to clarify before proceeding
+- In Agent mode, use tools to discover more information, starting with the glob/grep tools if available.

.continue/rules/programming-principles.md

@@ -0,0 +1,6 @@
+---
+name: Programming principles
+description: Guidelines for coding fundamentals in this project
+---
+
+Use functional programming paradigms whenever possible. Modifying existing classes or creating singletons where needed is acceptable. but otherwise, use functions.

.continue/rules/unit-testing-rules.yaml

@@ -6,25 +6,23 @@ rules:
     rule: >-
       For unit testing in this project:
 
+      1. The project uses Vitest and Jest for testing. Prefer Vitest
 
-      1. The project uses Jest as the testing framework
+      2. Run tests from within the specific package directory (e.g., `cd core && ..`
 
-      2. Run tests using `npm test` from within the specific package/module
-      directory
+      3. For vitest tests,
+        - Test files follow the pattern `*.vitest.ts`
+         - Run tests using `vitest` from within the specific package/module
+      directory: `cd [directory] && vitest -- [test file path]`
 
-      3. Command structure: `cd [directory] && npm test -- [test file path]`
+      4. For jest tests, 
+         - Test files follow the pattern `*.test.ts`
+         - Run tests using `npm test` from within the specific package/module
+      directory: `cd [directory] && npm test -- [test file path]`
+         - The test script uses experimental VM modules via NODE_OPTIONS flag
 
-      4. The test script uses experimental VM modules via NODE_OPTIONS flag
-
-      5. Test files follow the pattern `*.test.ts`
-
-      6. Tests must import Jest with `import { jest } from "@jest/globals";`
-
-      7. Run tests from within the specific package directory (e.g., `cd core`
-      for core module tests)
-
-      8. Write tests as top-level `test()` functions - DO NOT use `describe()`
+      5. For both
+         - Write tests as top-level `test()` functions - DO NOT use `describe()`
       blocks
-
-      9. Include the function name being tested in the test description for
+         - Include the function name being tested in the test description for
       clarity

extensions/vscode/rules.md

@@ -0,0 +1,6 @@
+The `extensions/vscode` folder contains code for the "Continue" VS Code Extension. Continue is a coding assistant extension which extends IDE functionality with AI.
+Core IDE functionality, such as reading files, is implemented using the `VSCodeIDE` class. Code to enable editing/diff streaming into the editor, code suggestion autocompletion, and more can also be found in this directory.
+Shared code that has abstract logic for the extension is in `core/`. Avoid importing code from `core/` directly where possible. Core is designed to be bundalable as a binary. Use `core.invoke` to send messages to the
+
+- see `core/protocol/core.ts` for a list of commands VS Code can post/request to Core
+- see `core/portocol/ide.ts` for a list of commands/message types core can post/request to VS Code