Cline rules

1# Technical Documentation Style Guide
2 
3## General Principles
4 
5* **Clarity and Conciseness:** Write clearly and directly. Avoid jargon where simpler terms suffice. Get straight to the point, focusing on desired outcomes.
6* **Accuracy:** Ensure all technical details, code examples, and instructions are correct and up-to-date. Regularly review and update documentation.
7* **Consistency:** Maintain consistent terminology, formatting, and structure across all documentation. Use established naming conventions.
8* **Audience:** Tailor the language and level of detail to the intended audience (e.g., developers, end-users, other AI agents).
9* **Focus on Outcomes:** Describe the results you want, not just the specific steps.
10 
11## Formatting
12 
13* **Headings:** Use Markdown headings (`#`, `##`, `###`, etc.) logically to structure content. Follow a consistent hierarchy.
14* **Code Blocks:** Use fenced code blocks (```) for all code examples, configuration files, and terminal commands. Always specify the language for syntax highlighting (e.g.,```typescript, ```json,```bash).
15* **Inline Code:** Use backticks (`) for inline code, file names, directory names, and technical terms (e.g.,`npm install`,`package.json`,`AgentState`).
16* **Lists:** Use bullet points (`*` or `-`) for unordered lists and numbers (`1.`, `2.`) for ordered lists.
17* **Bold and Italic:** Use bold (`**text**`) for emphasis and italic (`*text*`) for terms being introduced or for titles of books/articles.
18 
19## Content Guidelines
20 
21* **Introduction:** Every document should start with a brief introduction outlining its purpose and what it covers.
22* **Examples:** Provide practical code examples or usage scenarios where applicable. Ensure examples are runnable and demonstrate the concept clearly.
23* **Diagrams:** Use diagrams (e.g., Mermaid diagrams) to illustrate complex flows, architectures, or relationships. This is crucial for visualizing LangGraph workflows.
24* **Cross-referencing:** Link to related documentation within the project or to external resources (e.g., LangChain.js docs, LangGraph.js tutorials) where appropriate.
25* **Version Control:** Document changes and updates, potentially via `CHANGELOG.md` or similar versioning mechanisms.
26* **Prerequisites:** Clearly list any prerequisites or dependencies required for understanding or implementing the documented content.
27