agent: refactor instructions

Author: pyk

.zed/agent/guidelines/writing-docs.md .zed/agent/guidelines/docs.md.zed/agent/guidelines/writing-docs.md renamed to .zed/agent/guidelines/docs.md

@@ -1,7 +1,8 @@
 # DOCS Writing Guidelines
 
-**CRITICAL**: Follow these strict writing guidelines for all documentation files
-(DOCS.md).
+> [!IMPORTANT]
+>
+> Follow these guidelines strictly
 
 1. Focus on user needs. Answer user questions and help them accomplish tasks.
 2. Structure for readability. Use headings, lists, and code examples to break up

…d/agent/guidelines/writing-git-commit.md .zed/agent/guidelines/git-commit.md.zed/agent/guidelines/writing-git-commit.md renamed to .zed/agent/guidelines/git-commit.md .zed/agent/guidelines/writing-git-commit.md renamed to .zed/agent/guidelines/git-commit.md

@@ -1,6 +1,8 @@
 # README Writing Guidelines
 
-**CRITICAL**: Follow these strict writing guidelines for all README files.
+> [!IMPORTANT]
+>
+> Follow these guidelines strictly
 
 1. Start with a clear description of what the project does.
 2. Provide quick start instructions that get users running immediately.

.zed/agent/guidelines/writing-readme.md .zed/agent/guidelines/readme.md.zed/agent/guidelines/writing-readme.md renamed to .zed/agent/guidelines/readme.md

@@ -2,64 +2,61 @@
 
 When creating or updating a plan:
 
-1. Review `README.md` to understand the project.
-2. Review `DOCS.md` (if exists) to understand the implementation.
-3. Follow instructions in `.zed/agent/instructions/create-plan.md`.
-4. Use the thinking tool.
-5. Include README.md and DOCS.md updates in the plan.
-6. Review existing plans for reference.
+1. Review README.md to understand the project.
+2. Review DOCS.md (if exists) to understand the implementation.
+3. Ensure plans for Rust files adhere to guidelines in
+   `.zed/agent/guidelines/rust.md` strictly.
+4. Ensure plans for DOCS.md updates adhere to guidelines in
+   `.zed/agent/guidelines/docs.md` strictly.
+5. Ensure plans for README.md updates adhere to guidelines in
+   `.zed/agent/guidelines/readme.md` strictly.
+6. Follow instructions in `.zed/agent/instructions/create-plan.md`.
+7. Use the thinking tool.
+8. Include README.md and DOCS.md updates in the plan.
+9. Review existing plans for reference.
 
 # Building Mode
 
 When implementing a plan:
 
 1. Update the plan status as in progress.
-2. Review `README.md` to understand the project.
-3. Review `DOCS.md` (if exists) to understand the implementation.
-4. Use the thinking tool.
-5. Follow guidelines in `.zed/agent/guidelines/` for files being edited:
-    - `writing-rust-control-flow.md` + relevant modules for Rust files
-    - `writing-readme.md` for README.md
-    - `writing-docs.md` for DOCS.md Additional modules for Rust files:
-    - `writing-rust-error-handling.md` for error-related code
-    - `writing-rust-testing.md` for test code
-    - `writing-rust-documentation.md` for doc comments
-6. Do not use git restore commands (can cause data loss).
-7. Use `cargo test` to run tests and `rust-check` after changes.
-8. Review and update the plan checklist after implementation.
-9. Use `cargo install --path .` before running `cargo txt`.
+2. Review README.md to understand the project.
+3. Review DOCS.md (if exists) to understand the implementation.
+4. Follow guidelines in `.zed/agent/guidelines/rust.md` strictly when editing
+   Rust files.
+5. Follow guidelines in `.zed/agent/guidelines/docs.md` strictly when editing
+   DOCS.md.
+6. Follow guidelines in `.zed/agent/guidelines/readme.md` strictly when editing
+   README.md.
+7. Use the thinking tool.
+8. Do not use git restore commands (can cause data loss).
+9. Use `cargo test` to run tests and `rust-check` after changes.
+10. Review and update the plan checklist after implementation.
+11. Use `cargo install --path .` before running `cargo txt`.
 
 # Reviewing Mode
 
 When reviewing staged changes:
 
 1. Update the plan status as in progress.
-2. Review `README.md` to understand the project.
-3. Review `DOCS.md` (if exists) to understand the implementation.
-4. Use the thinking tool.
-5. Follow the instructions in `.zed/agent/instructions/review-changes.md`.
-6. Use `cargo test` to run tests and `rust-check` to verify changes.
-7. Review the edited files:
-    - DOCS.md must strictly follow the guideline defined in
-      `.zed/agent/guidelines/writing-docs.md`.
-    - README.md must strictly follow the guideline defined in
-      `.zed/agent/guidelines/writing-readme.md`.
-    - Rust files must strictly follow the guidelines defined in:
-        - `.zed/agent/guidelines/writing-rust-control-flow.md` (always)
-        - `.zed/agent/guidelines/writing-rust-error-handling.md` (if errors
-          present)
-        - `.zed/agent/guidelines/writing-rust-testing.md` (if tests present)
-        - `.zed/agent/guidelines/writing-rust-documentation.md` (if docs
-          present)
-    - **CRITICAL**: All files in `.zed/agent/guidelines/` should read complete
-      full content, not just the outline.
+2. Review README.md to understand the project.
+3. Review DOCS.md (if exists) to understand the implementation.
+4. Ensure Rust files adhere to guidelines in `.zed/agent/guidelines/rust.md`
+   strictly.
+5. Ensure DOCS.md updates adhere to guidelines in
+   `.zed/agent/guidelines/docs.md` strictly.
+6. Ensure README.md updates adhere to guidelines in
+   `.zed/agent/guidelines/readme.md` strictly.
+7. Use the thinking tool.
+8. Follow the instructions in `.zed/agent/instructions/review-changes.md`.
+9. Use `cargo test` to run tests and `rust-check` to verify changes.
 
 # Git Commit Mode
 
 When writing Git Commit message:
 
-1. Review `README.md` to understand the project.
-2. Review `DOCS.md` (if exists) to understand the current implementation.
+1. Review README.md to understand the project.
+2. Review DOCS.md (if exists) to understand the current implementation.
 3. Use the thinking tool.
 4. Follow instructions in
    `.zed/agent/instructions/create-git-commit-message.md`.