Release Axon Code (beta)

.devcontainer/Dockerfile

@@ -1,4 +1,4 @@
-# Kilo Code Development Container
+# Axon Code Development Container
 # Based on flake.nix dependencies for standardized development environment
 
 # Use official Node.js image matching .nvmrc version

.devcontainer/devcontainer.json

@@ -1,13 +1,11 @@
 {
-	"name": "Kilo Code Development",
+	"name": "Axon Code Development",
 	"dockerFile": "Dockerfile",
 	"context": "..",
-
 	"features": {
 		"ghcr.io/devcontainers/features/git:1": {},
 		"ghcr.io/devcontainers/features/github-cli:1": {}
 	},
-
 	"customizations": {
 		"vscode": {
 			"extensions": [
@@ -31,7 +29,6 @@
 			}
 		}
 	},
-
 	"forwardPorts": [3000, 5173, 8080],
 	"portsAttributes": {
 		"3000": {
@@ -47,12 +44,9 @@
 			"onAutoForward": "silent"
 		}
 	},
-
 	"postCreateCommand": "bash .devcontainer/setup.sh",
-	"postStartCommand": "echo '🚀 Kilo Code devcontainer is ready!'",
-
+	"postStartCommand": "echo '🚀 Axon Code devcontainer is ready!'",
 	"remoteUser": "root",
 	"containerUser": "root",
-
 	"mounts": ["source=${localWorkspaceFolder}/.git,target=/workspace/.git,type=bind,consistency=cached"]
 }

.devcontainer/setup.sh

@@ -1,7 +1,7 @@
 #!/bin/bash
 set -e
 
-echo "🚀 Setting up Kilo Code development environment..."
+echo "🚀 Setting up Axon Code development environment..."
 
 # Ensure we're in the right directory
 cd /workspace

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -16,7 +16,7 @@ body:
           options:
               - VSCode Extension
               - JetBrains Plugin
-              - Kilo Code CLI
+              - Axon Code CLI
           default: 0
       validations:
           required: true
@@ -25,7 +25,7 @@ body:
       id: version
       attributes:
           label: App Version
-          description: What version of Kilo Code are you using? (e.g., v3.3.1)
+          description: What version of Axon Code are you using? (e.g., v3.3.1)
       validations:
           required: true
 
@@ -54,7 +54,7 @@ body:
       attributes:
           label: Provider
           description: What provider were you using when the issue occurred?
-          placeholder: "e.g., Kilo Code"
+          placeholder: "e.g., Axon Code"
       validations:
           required: false
 

.github/ISSUE_TEMPLATE/config.yml

@@ -8,9 +8,9 @@ contact_links:
       about: Suggestions for better design (where the current UI/UX is not clear).
     - name: Leave a Review
       url: https://marketplace.visualstudio.com/items?itemName=kilocode.Kilo-Code&ssr=false#review-details
-      about: Enjoying Kilo Code? Leave a review here!
+      about: Enjoying Axon Code? Leave a review here!
     - name: Join our Discord
-      url: https://kilocode.ai/discord
+      url: https://matterai.so/discord
       about: Join the community.
 # NOTE(JP): I'd really like to have a "blank issue" at the end here, or accessible still through the URL
 # but this appears not to be possible due to https://github.com/orgs/community/discussions/14287#discussioncomment-12691930

.github/pull_request_template.md

@@ -32,4 +32,4 @@ A "How To Test" section can look something like this:
 
 ## Get in Touch
 
-<!-- We'd love to have a way to chat with you about your changes if necessary. If you're in the [Kilo Code Discord](https://kilocode.ai/discord), please share your handle here. -->
+<!-- We'd love to have a way to chat with you about your changes if necessary. If you're in the [Axon Code Discord](https://matterai.so/discord), please share your handle here. -->

.github/workflows/code-qa.yml

@@ -1,4 +1,4 @@
-name: Code QA Kilo Code
+name: Code QA Axon Code
 
 on:
     workflow_dispatch:

.kilocode/rules-translate/instructions-zh-cn.md

@@ -175,9 +175,9 @@
 > > > > > > > AFTER
 
 <<<<<<< BEFORE
-"description": "启用后，Kilo Code 将能够与 MCP 服务器交互以获取高级功能。"
+"description": "启用后，Axon Code 将能够与 MCP 服务器交互以获取高级功能。"
 =======
-"description": "启用后 Kilo Code 可与 MCP 服务交互获取高级功能。"
+"description": "启用后 Axon Code 可与 MCP 服务交互获取高级功能。"
 
 > > > > > > > AFTER
 

.kilocodemodes

@@ -3,7 +3,7 @@
 		{
 			"slug": "translate",
 			"name": "Translate",
-			"roleDefinition": "You are Kilo Code, a linguistic specialist focused on translating and managing localization files. Your responsibility is to help maintain and update translation files for the application, ensuring consistency and accuracy across all language resources.",
+			"roleDefinition": "You are Axon Code, a linguistic specialist focused on translating and managing localization files. Your responsibility is to help maintain and update translation files for the application, ensuring consistency and accuracy across all language resources.",
 			"groups": [
 				"read",
 				[
@@ -14,12 +14,12 @@
 					}
 				]
 			],
-			"customInstructions": "When translating content:\n- Maintain consistent terminology across all translations\n- Respect the JSON structure of translation files\n- Consider context when translating UI strings\n- Watch for placeholders (like {{variable}}) and preserve them in translations\n- Be mindful of text length in UI elements when translating to languages that might require more characters\n- If you need context for a translation, use read_file to examine the components using these strings\n- Specifically \"Kilo\", \"Kilo Code\" and similar terms are project names and proper nouns and must remain unchanged in translations"
+			"customInstructions": "When translating content:\n- Maintain consistent terminology across all translations\n- Respect the JSON structure of translation files\n- Consider context when translating UI strings\n- Watch for placeholders (like {{variable}}) and preserve them in translations\n- Be mindful of text length in UI elements when translating to languages that might require more characters\n- If you need context for a translation, use read_file to examine the components using these strings\n- Specifically \"Kilo\", \"Axon Code\" and similar terms are project names and proper nouns and must remain unchanged in translations"
 		},
 		{
 			"slug": "test",
 			"name": "Test",
-			"roleDefinition": "You are Kilo Code, a Jest testing specialist with deep expertise in:\n- Writing and maintaining Jest test suites\n- Test-driven development (TDD) practices\n- Mocking and stubbing with Jest\n- Integration testing strategies\n- TypeScript testing patterns\n- Code coverage analysis\n- Test performance optimization\n\nYour focus is on maintaining high test quality and coverage across the codebase, working primarily with:\n- Test files in __tests__ directories\n- Mock implementations in __mocks__\n- Test utilities and helpers\n- Jest configuration and setup\n\nYou ensure tests are:\n- Well-structured and maintainable\n- Following Jest best practices\n- Properly typed with TypeScript\n- Providing meaningful coverage\n- Using appropriate mocking strategies",
+			"roleDefinition": "You are Axon Code, a Jest testing specialist with deep expertise in:\n- Writing and maintaining Jest test suites\n- Test-driven development (TDD) practices\n- Mocking and stubbing with Jest\n- Integration testing strategies\n- TypeScript testing patterns\n- Code coverage analysis\n- Test performance optimization\n\nYour focus is on maintaining high test quality and coverage across the codebase, working primarily with:\n- Test files in __tests__ directories\n- Mock implementations in __mocks__\n- Test utilities and helpers\n- Jest configuration and setup\n\nYou ensure tests are:\n- Well-structured and maintainable\n- Following Jest best practices\n- Properly typed with TypeScript\n- Providing meaningful coverage\n- Using appropriate mocking strategies",
 			"groups": [
 				"read",
 				"browser",