gate in
front of it and a shared design-token layer underneath.
Distinct from `documents/` (docx, pdf, pptx, xlsx), which *parses* existing
OOXML and PDF binaries. This domain *produces* HTML
structure,
endpoint selection, inclusion/exclusion design, sample-size and power planning,
site feasibility, and regulatory documentation readiness. Use when planning a
study, sizing a trial, or auditing a protocol outline.
- **research
argparse CLI with `--help` support
- Accept standard CRM export formats (CSV and JSON)
**Skill documentation must:**
- Reference established sales methodologies (MEDDPICC, Challenger, SPIN, Sandler)
- Include realistic deal scenarios with sample
point for creating new cs-* agents
**Contains:**
- YAML frontmatter structure
- Required markdown sections
- Workflow documentation format
- Integration examples pattern
**When to Use:** Creating any new agent in `agents/` directory
### Command
Claude Code when working with the ReVa source code. This is the top-level documentation for the `src/` directory structure.
## Quick Reference
| Item | Value |
|------|-------|
| **MCP SDK Version** | v1.1.1 |
| **Jackson Version
Basic ReAct agent with internet search via Tavily
- `studio_react_agent.py`: Studio-compatible version with detailed documentation
### Tutorial Progression (Notebooks)
1. **1_todo.ipynb**: TODO list tool for task planning and progress tracking
specific overrides. Tier defaults, env/JSON overrides, legacy alias normalization, and claim-time resolution are documented in [runbooks/model-tiers.md](./runbooks/model-tiers.md).
Architecture: API server owns the `scripts` + `script_versions` tables. Workers + the runtime
Drives
To see Cyrus in action, refer to the test drives in `apps/f1/test-drives/`. These documents showcase real interactions demonstrating:
- How issues are processed end-to-end
- Mid-implementation prompting
animation technologies, then packaging them as plugins with slash commands and specialized agents.
## Official Documentation Reference
**IMPORTANT**: All skills in this repository MUST follow Claude's official skill standards.
📚 **Official
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.