prog-expert-marimo

Marimo notebooks require cells defined with @app.cell decorators, each maintaining a unique variable scope to enforce reactivity. Proper cell structure ensures variables flow correctly between cells and the notebook executes reliably.

Testing Marimo notebooks uses a Lint-Export-Assert protocol for end-to-end validation. This workflow checks cell structure, exports the notebook, and runs assertions to verify reactivity rules and self-checks pass.

Marimo enforces unique variable scope across all cells, so defining the same variable in multiple cells causes reactivity conflicts. Each variable must be defined in exactly one cell to maintain consistent reactive dependencies.

Yes, Marimo notebooks support complex projects with automated self-verification through pattern-based guidance and structured testing workflows. The included scripts enable version tracking and recipe-based development for reliable validation.

Yes, frontmatter metadata is required when authoring Marimo notebooks with this development workflow. It provides context for notebook tracking, recipe-based guidance, and structured project management across knowledge domains.

Version tracking and research prompts in Marimo notebook projects are managed through included scripts that enable knowledge management. These scripts provide recipe-based guidance and pattern tracking to accelerate development across domains.