marimo-notebook

Marimo notebooks use reactive cells where outputs automatically update when dependencies change. Build them by defining cells with clear input-output relationships, using UI controls bound directly to variables, and avoiding mutable global state. This ensures transparent data flow and predictable behavior across your notebook.

Marimo provides code patterns for UI elements, reactive dependencies, and data flow. Structure dashboards by connecting controls to downstream cells, organizing data-loading cells separately, and using utility functions for common visualizations. The Skill guides you through proven patterns for responsive layouts and control binding.

Conversion requires refactoring cells to remove hidden state, restructuring data dependencies, and replacing static visualizations with reactive UI. The Skill provides debugging guidance and pattern libraries to identify conversion bottlenecks, rewrite control logic, and validate that reactivity works correctly in your migrated notebook.

Yes. The Skill generates notebook scaffolds with proper imports, app structure, and foundational cells for data loading and UI setup. Starting with a template prevents common architectural mistakes and ensures your notebook follows best practices for reactive design from the beginning.

Debugging reactive issues involves checking cell dependencies, verifying controls are bound to variables correctly, and ensuring no cells have side effects that block propagation. The Skill provides error-handling patterns and validation techniques to diagnose and fix common reactivity failures.

Yes. Marimo supports SQL integration and database workflows within reactive notebooks. The Skill includes patterns for loading data from databases, parameterizing queries with UI controls, and displaying results reactively as inputs change.