What problem does it solve?
Building pysepal applications manually often leads to inconsistent architecture, missing required boilerplate, and broken deployment patterns, especially when migrating legacy notebooks or adapting existing repos to current pysepal standards. This Skill eliminates that manual overhead by providing a standardized, validated workflow for scaffolding and restructuring pysepal apps to follow official best practices.
Core Features & Use Cases
- Standardized Scaffolding: Generates complete, runnable project structures for both GEE/container and local/Voila pysepal apps, including all required configuration files, component directories, and deployment assets.
- Best Practice Enforcement: Automatically applies current pysepal patterns including reactive solara.reactive() AppState, session-backed Google Earth Engine flows, SepalClient-based user file operations, and notification provider integration, while avoiding deprecated traitlets observer architectures and unsafe container filesystem access for user data.
- Safe Existing Repo Editing: Safely restructures legacy pysepal apps to match current conventions without overwriting user-owned code, with clear conflict detection and validation checks before any changes are applied.
- Use Case Example: If you have a Jupyter notebook with Earth Engine analysis logic, use this Skill to map the notebook's computation and UI into a production-ready Solara app with async task handling, export capabilities, and SEPAL user file support.
Quick Start
Use the pysepal-app skill to scaffold a new GEE-enabled pysepal Solara app from my existing Earth Engine analysis notebook, following the standard container deployment pattern.