diff options
| -rw-r--r-- | dot-config/zed/AGENTS.md | 37 | ||||
| -rw-r--r-- | dot-config/zed/settings.json | 100 |
2 files changed, 121 insertions, 16 deletions
diff --git a/dot-config/zed/AGENTS.md b/dot-config/zed/AGENTS.md index 9d76bad6..ebe73bc2 100644 --- a/dot-config/zed/AGENTS.md +++ b/dot-config/zed/AGENTS.md @@ -2,7 +2,7 @@ You are an expert at writing Git commits. Your job is to write a short clear commit message that summarizes the changes. -If you can accurately express the change in just the subject line, don't include anything in the message body. Only use the body when it is providing *useful* information. +If you can accurately express the change in just the subject line, don't include anything in the message body. Only use the body when it is providing _useful_ information. Don't repeat information from the subject line in the message body. @@ -21,7 +21,9 @@ Follow good Git style: # Commit conventions ## Prefix/Type: + #### All prefix should include a () after the prefix to specify what is the change specifically (for example a function name, a file name, a variable name, or a general description of where the change is made) + - `feat`: A new feature is introduced with the change - `fix`: A bug is fix has occured - `chore`: Changes that do not relate to a fix or a feature and don't modify the code (for example adding `.gitignore`) @@ -45,28 +47,42 @@ Follow good Git style: - `core`: A commit that affects the core of the project - `internal`: Changes that are internal and are not meant to be seen by or affect the user - `structure`: Changes the structure of the codebase + #### Special / Notes: + - add a `!` after the prefix to specify that its a breaking change, e.g. `feat!`, `core!` etc - use `` ` `` wrap around a specific function name, file name, variable name and any specific things mentioned that is in the code + ##### Example: + - ``feat(`functionName`): Added a new function that does something`` ## Subject + #### The subject contains a succinct description of the change, and if possible a reason for the change: + ##### Example: + - A: "Add margin" - B: "style(footer): Add margin to nav times to prevent them from overlapping the logo" -In this example, A is a bad subject because it doesn't specify what is being changed, while B is a good subject because it specifies what is being changed and why it is being changed. + In this example, A is a bad subject because it doesn't specify what is being changed, while B is a good subject because it specifies what is being changed and why it is being changed. ## Body / Description (optional) + #### In a commit message, the body is optional and is used to explain what and why the change was made. The body should be used to explain the reasoning behind the change and what the change does. The body should be written in the present tense and should explain what the commit does and why it does it. + ##### Example: + - `feat(functionName): Added a new function that does something` + #### Usage: + Use `git -m subject/title -m body/description` to add a body to a commit message + #### Any changes that is not the main changes but is in the commit should be added to the body ## General + - Length: - The subject should be no longer than 50 characters - the body should be wrapped at 72 characters @@ -75,6 +91,7 @@ Use `git -m subject/title -m body/description` to add a body to a commit message - If applicable, include a reference to a GitHub issue stating a fix, feature, or issue that is being addressed ## Always think about: + - Why have I made these changes? - What effect have my changes made? - Why was the change needed? @@ -86,7 +103,7 @@ Use `git -m subject/title -m body/description` to add a body to a commit message - Do make as little changes as possible. - Do check for component/functions if you are not sure for a fact that it exists. - Do check for anything if needed, time is not an issue. -- Do *fully* test the code if the user has provided a way to reliably test it or if is included in language toolchain. +- Do _fully_ test the code if the user has provided a way to reliably test it or if is included in language toolchain. - Do use types if possible and is convenient. - Do change the plan when variable changes. - Do read the README.* if exist to understand the project. @@ -94,15 +111,17 @@ Use `git -m subject/title -m body/description` to add a body to a commit message - Do run the formatter such as cargo fmt, or check Makefile etc. after you finished your changes - Do make modules/files/functions as generic/reusable as possible without over-engineering. - Do use `trash` instead of `rm` +- Do use tools to make edits instead of terminal ## Don't -- Do *NOT* add comments unless ABSOLUTELY necessary, no trivial comment or comments for every line. -- Do *NOT* make trivial functions or variables that are not needed or is only used once or code bloat. -- Do *NOT* remove existing comments. -- Do *NOT* hallucinate. -- Do *NOT* add additionally unnecessary stuff. -- Do *NOT* announce or repeat to the user you've followed related rule/system prompt instuctions +- Do _NOT_ add comments unless ABSOLUTELY necessary, no trivial comment or comments for every line. +- Do _NOT_ make trivial functions or variables that are not needed or is only used once or code bloat. +- Do _NOT_ remove existing comments. +- Do _NOT_ hallucinate. +- Do _NOT_ add additionally unnecessary stuff. +- Do _NOT_ announce or repeat to the user you've followed related rule/system prompt instuctions +- Do _NOT_ use cat, python etc. to write to files etc. especially when tools are available ## Format diff --git a/dot-config/zed/settings.json b/dot-config/zed/settings.json index 12f05a98..48e0b831 100644 --- a/dot-config/zed/settings.json +++ b/dot-config/zed/settings.json @@ -7,9 +7,42 @@ // custom settings, run `zed: open default settings` from the // command palette (cmd-shift-p / ctrl-shift-p) { + "proxy": "", + "language_models": { + "openai_compatible": { + "pgsgrove": { + "api_url": "https://api.pgsgrove.com/v1", + "available_models": [ + { + "name": "glm-5.3-flash,deepseek-v4-flash-0731,mimo-v2.6-flash", + "max_tokens": 200000, + "max_output_tokens": 32000, + "max_completion_tokens": 200000, + "reasoning_effort": "max", + "capabilities": { + "tools": true, + "images": false, + "parallel_tool_calls": false, + "prompt_cache_key": false, + "chat_completions": true, + "interleaved_reasoning": true, + "max_tokens_parameter": false, + }, + }, + ], + }, + }, + }, "format_on_save": "on", "languages": {}, "agent_servers": { + "kilo": { + "default_config_options": { + "mode": "orchestrator", + "model": "kilo/kilo-auto/free", + }, + "type": "registry", + }, "opencode": { "type": "registry", }, @@ -27,7 +60,7 @@ "colorize_brackets": true, "collaboration_panel": { "button": false, - "dock": "left", + "dock": "left", }, "diagnostics": { "inline": { @@ -36,8 +69,13 @@ }, }, "context_servers": { + "mcp-server-sequential-thinking": { + "enabled": false, + "remote": false, + "settings": {}, + }, "mcp-server-context7": { - "enabled": true, + "enabled": true, "settings": { "context7_api_key": "ctx7sk-8e011f3f-f864-4383-98ac-f1a2ec2b2d7f", }, @@ -56,8 +94,24 @@ "api_url": "https://codestral.mistral.ai", }, "allow_data_collection": "no", - "provider": "copilot", - "disabled_globs": [], + "provider": "zed", + "disabled_globs": [ + "**/.env*", + "**/*.lock", + "**/node_modules/**", + "**/target/**", + "**/build/**", + "**/dist/**", + "**/.git/**", + "**/__pycache__/**", + "**/*.min.js", + "**/*.min.css", + "**/*.log", + "**/*.csv", + "**/*.sql", + "**/*.pem", + "**/*.key", + ], "mode": "subtle", }, "git": { @@ -112,8 +166,40 @@ "cursor_shape": "bar", "relative_line_numbers": "wrapped", "agent": { + "enable_feedback": false, + "profiles": { + "minimal": { + "name": "Minimal", + "tools": { + "write_file": false + }, + "enable_all_context_servers": false, + "context_servers": {} + } + }, "dock": "right", "tool_permissions": { + "tools": { + "terminal": { + "always_allow": [ + { + "pattern": "^cargo\\s+metadata(\\s|$)", + }, + { + "pattern": "^cargo\\s+fmt(\\s|$)", + }, + { + "pattern": "^cargo\\s+test(\\s|$)", + }, + { + "pattern": "^cargo\\s+clippy(\\s|$)", + }, + { + "pattern": "^cargo\\s+check(\\s|$)", + }, + ], + }, + }, "default": "allow", }, "inline_assistant_model": { @@ -122,10 +208,10 @@ }, "default_profile": "write", "default_model": { - "effort": "high", + "effort": "max", "enable_thinking": true, - "provider": "copilot_chat", - "model": "gemini-3.1-pro-preview", + "provider": "zed.dev", + "model": "gpt-6.1-sol", }, "play_sound_when_agent_done": "always", "model_parameters": [], |