.clinerules Best Practices

# .clinerules Best Practices

This document outlines best practices for using `.clinerules` files to maintain project standards and improve team consistency when using Cline.

## Key Benefits of .clinerules

- **Version Controlled**: The `.clinerules` file becomes part of your project's source code, allowing for version tracking and collaboration.
- **Team Consistency**: Ensures consistent behavior of Cline across all team members working on the project.
- **Project-Specific**: Allows for rules and standards to be tailored to the specific needs of each project.
- **Institutional Knowledge**: Helps maintain project standards and development practices directly within the codebase, serving as living documentation.

## Example .clinerules Structure

A well-structured `.clinerules` file can include sections for project guidelines, documentation, architecture decisions, code style, and testing standards.

```markdown
# Project Guidelines

## Documentation Requirements

- Update relevant documentation in `/docs` when modifying features
- Keep `README.md` in sync with new capabilities
- Maintain changelog entries in `CHANGELOG.md`

## Architecture Decision Records