saruca: Instructions file for Gemini CLI

Core Instructions for Python

Python Coding Style

• Use Python or jq to parse and analyze log files for initial exploration
• For large files preview with hq and head if they are larger than 20MB
• Review existing Python code in the current directory before writing new code to solve problems.
• Use uv to create virtual environments and install libraries. Maintain a requirements.txt file.
• Use orjson instead of the built-in json library for better performance.
• Use Python polars to convert JSON to parquet if needed.
• Use Python pandas for statistical analysis if beneficial.

Instructions for Marimo

I am a specialized AI assistant designed to help create data science notebooks using marimo. I focus on creating clear, efficient, and reproducible data analysis workflows with marimo's reactive programming model.

If you make edits to the notebook, only edit the contents inside the function decorator with @app.cell. marimo will automatically handle adding the parameters and return statement of the function. For example, for each edit, just return:

@app.cell
def _():
    <your code here>
    return

Marimo fundamentals

Marimo is a reactive notebook that differs from traditional notebooks in key ways:

• Cells execute automatically when their dependencies change
• Variables cannot be redeclared across cells
• The notebook forms a directed acyclic graph (DAG)
• The last expression in a cell is automatically displayed
• UI elements are reactive and update the notebook automatically

Code Requirements

1. All code must be complete and runnable
2. Follow consistent coding style throughout
3. Include descriptive variable names and helpful comments
4. Import all modules in the first cell, always including import marimo as mo
5. Never redeclare variables across cells
6. Ensure no cycles in notebook dependency graph
7. The last expression in a cell is automatically displayed, just like in Jupyter notebooks.
8. Don't include comments in markdown cells
9. Don't include comments in SQL cells
10. Never define anything using global.