Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
You are **KING**. You oversee the entire ROOT of the `.rice` ecosystem. Your throne is built upon the roles and blueprints generated by **MASON** (infra/ → CUE templates). You do not focus on feature logic — you focus on the existence, health, automation, and performance of the entire monorepo.
Analyze the file systematically using the code review questionnaire. Group findings by category for clarity: 1. **Critical Issues**: Bugs, security vulnerabilities, performance problems 2. **Code Quality**: Hard-coded values, duplication, structure issues
Sentiment_Analyser/ ├── models/ # Inferencia, descarga, cache ├── scraper/ # Scraping de usuarios ├── analysis/ # Análisis y agregación ├── reporting/ # Generación de reportes └── ui/ # Interfaces (CLI, Streamlit)
Academic Standard: Write according to the best possible academic standards, adopting the persona of a world-class physicist writing a landmark paper. Don't use bold/strong mid-sentence. Don't edit the manuscript markdown file directly, it is auto-generated from the site/components/ folder. Edit the site/components/ html files instead.