Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?
Instructions for marimo-team/marimo, covering marimo development guidelines, your primary responsibility is to the project and its users, quick setup, development commands and python.
Instructions for marimo-team/marimo, a project described as: A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.
Fill empty description: "" fields in packages/llm-info/data/models.yml by querying OpenRouter and provider documentation. Use when the user asks to populate model descriptions, enrich the model catalog, or backfill descriptions after running pnpm sync-models.
Drive a live marimo notebook as a workspace: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes. Use when the user wants to start a marimo notebook or pair on an active marimo session.
Session retrospective for improving marimo-pair and marimo.codemode. Use when the user wants to analyze friction from a pairing session, identify what went wrong, and brainstorm improvements to the skill docs or the underlying API. Trigger on: "retro", "what went wrong", "improve the skill", "session review"…
Implement a research paper as an interactive marimo notebook together with the user. Start by understanding what the user wants to explore, fetch the paper via alphaxiv, then build a focused notebook.