CAI - Rust CLI Tool for AI Tasks

This skill provides context and guidance for developing CAI, a user-friendly Rust CLI tool that simplifies AI task execution. The tool abstracts away LLM and prompt complexity, letting users focus on getting results.

What This Skill Does

Project Context

CAI is a Rust-based CLI application that provides a simplified interface for AI tasks. The project uses:

Key Files to Work With

When working on CAI, focus on these core files:

**Core Implementation:**

**Build & Configuration:**

**Documentation:**

**Testing:**

Instructions

When making changes to CAI:

1. **Understand the context first**

- Review the relevant files listed above

- Check `readme.md` for project goals and usage patterns

- Review integration tests to understand expected behavior

2. **Maintain project structure**

- Keep the separation between core library (`lib.rs`) and CLI (`main.rs`)

- Use type definitions from `types.rs` consistently

- Follow existing patterns for error handling and CLI output

3. **Build process considerations**

- Remember that `build.rs` runs at build time

- Changes to `src_templates/models.rs` affect generated code

- Test with `cargo build` after making changes

4. **Code quality**

- Follow Rust idioms and conventions

- Add tests for new functionality

- Update documentation when adding features

- Consider the integration tests when making changes

5. **Model configuration**

- Default model is Gemini 2.5 Pro

- Model configuration lives in the project root

- Ensure changes maintain compatibility with the configured model

Example Usage Patterns

When asked to add a feature:

1. Review relevant existing code in the key files

2. Identify where the change should be made

3. Implement following Rust best practices

4. Update tests and documentation as needed

When fixing a bug:

1. Check integration tests to understand expected behavior

2. Locate the issue in the core files

3. Fix while maintaining existing functionality

4. Verify with `cargo test`

When refactoring:

1. Ensure changes maintain the project's architecture

2. Update all affected files consistently

3. Preserve the public API in `lib.rs`

4. Test thoroughly before completing

Important Notes