Example Structure
```markdown
The toolkit provides the following benefits:
- Easy installation and setup
- Comprehensive documentation
- Active community support
- Regular updates and improvements
```
### Numbered Lists (Ordered)
**Use when**: Order matters (sequential
globs: **/*.md
alwaysApply: false
---
# Numbers and Dates Guidelines
Be consistent with number usage throughout documentation. When documenting examples or UI elements, duplicate numbers exactly as they appear in the interface
Avoid**: "information is written to/stored in" (use "and" instead)
## Punctuation to Avoid in Technical Documentation
### Don't Use These
- **Ellipses (...)**: Creates uncertainty
- **Exclamation points (!)**: Too informal for most technical content
tell me what you think."
**Usage**: Use declarative language most frequently in technical documentation, with imperative language when giving direct instructions.
### Welcoming to All Audiences
Consider accessibility and usability
Writing Process Guidelines
Follow the structured 8-step writing process when creating or updating documentation.
## The 8-Step Writing Process
### 1. Understand Your Audience
- Identify who will read the documentation
Follow these rules when the user's request involves integrating or selecting ReAct, Tool-Calling, Reasoning, or ReWOO agents within NeMo Agent Toolkit workflows
Follow these rules when the user's request involves NeMo Agent Toolkit installation, setup, environment configuration, or getting started with the toolkit
Overview
This Hydrogen project is based on React Router, not Remix. When working with documentation or code examples, you should always use imports from the appropriate React Router packages instead
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.