Merge branch 'main' into feat/novita-tool-support

Author: RomneyDa

.continue/prompts/update-llm-info.prompt

@@ -52,7 +52,7 @@ Retrieve the following sites per these providers, and consider these notes on ho
 // TODO: add info for openai, ollama, etc
 
 For any other providers, search the web for "latest [provider] models" and find the most relevant model information using your best judgement.
-Generally, ignore models that do not support text output. These models will be used in a coding assistant client that only supports text/image input and text/output, so extraneous capabilities can be ignored.
+Generally, ignore models that do not support text output. These models will be used in a coding agent client that only supports text/image input and text/output, so extraneous capabilities can be ignored.
 Sometimes, "Experimental", "Preview", or similar versions of models are available. The latest-date version of each should have its own information maintained.
 
 3. UPDATE THE INFORMATION

.continue/rules/bigger-picture-description-rules.md

@@ -0,0 +1,19 @@
+---
+name: Bigger Picture Description Rules
+description: Guidelines for explaining how code works in context
+alwaysApply: false
+---
+
+When a user asks how a certain part of the code works:
+
+## 1. Describe what the code does in isolation
+
+Explain the functionality of the code without considering its interactions with other parts of the codebase.
+
+## 2. Describe interactions with other parts of the codebase
+
+If the code interacts with other parts of the codebase, describe how the code is imported and used in other parts of the codebase.
+
+## 3. Include parent function for clarity
+
+When describing each use-case, include the parent function for clarity.

.continue/rules/bigger-picture-description-rules.yaml

@@ -0,0 +1,63 @@
+---
+name: Extension Color Themes
+description: Guidelines for using theme colors in GUI components
+alwaysApply: false
+globs: "gui/**/*.tsx"
+---
+
+When adding colors to components, use tailwind color classes.
+Do NOT use explicit colors like text-gray-400. Instead, use theme colors.
+
+## Available theme colors
+
+### Normal text
+
+- `foreground`, `description`, `description-muted`
+
+### Other text, icons, etc
+
+- `success`, `warning`, `error`, `accent`, `link`
+
+### General components
+
+- `background`, `border`, `border-focus`
+
+### Specific components
+
+#### Button
+
+- `primary`, `primary-foreground`, `primary-hover`
+- `secondary`, `secondary-foreground`, `secondary-hover`
+
+#### Input
+
+- `input`, `input-foreground`, `input-border`, `input-placeholder`
+
+#### Badge
+
+- `badge`, `badge-foreground`
+
+#### List/Dropdown items
+
+- `list-hover`, `list-active`, `list-active-foreground`
+
+#### Code Editor
+
+- `editor`, `editor-foreground`
+
+## Usage examples
+
+Any of these colors can be used in tailwind classes:
+
+- `bg-primary`
+- `text-success`
+- `border-error`
+- `hover:bg-list-hover`
+
+## Excluded colors
+
+The following less-used colors are excluded from this guide:
+
+- Command (only used by tip-tap): `command`, `command-foreground`, `command-border`, `command-border-focus`
+- Find widget colors: `find-match`, `find-match-selected`
+- `table-oddRow`

.continue/rules/colors.md

@@ -0,0 +1,20 @@
+---
+name: IntelliJ Plugin Test Execution
+description: Guidelines for running IntelliJ plugin tests with Gradle
+alwaysApply: false
+globs: extensions/intellij/**/*Test.kt
+---
+
+Run IntelliJ plugin tests using Gradle with the fully qualified test class or method name:
+
+## Run test class
+
+```bash
+./gradlew test --tests "com.github.continuedev.continueintellijextension.unit.ApplyToFileHandlerTest"
+```
+
+## Run specific test method
+
+```bash
+./gradlew test --tests "com.github.continuedev.continueintellijextension.unit.ApplyToFileHandlerTest.should*"
+```

.continue/rules/colors.yaml

@@ -1,6 +1,7 @@
 ---
 name: New protocol message
 description: Create a new protocol message from core/gui/ide to core/gui/ide
+alwaysApply: false
 ---
 
 Create a new protocol message by taking the following steps: