Imperative → Declarative (Flet Python)
SkillMonitoring & opsConvert an imperative Flet Python app in which controls are mutated and then page.update is called to declarative style using flet.component, flet.observable and state hooks.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Imperative → Declarative (Flet Python) skill
What this skill tells your AI
The instructions your AI receives, as published by flet-dev/flet in .agents/skills/imperative-to-declarative-flet/SKILL.md and read by ahel’s review.
Port an existing imperative Flet app to “components mode” with @ft.component, hooks, and (optionally) @ft.observable models.
Outcomes
- Original folder unchanged; new sibling folder created.
- Entry point uses
page.render(App)(components mode). - UI is derived from state; minimal/zero manual
page.update()for normal UI updates.
Choose a state strategy
- Use
@ft.observablefor nested app data you mutate in place (boards/lists/cards, drag+drop reorder). - Use
ft.use_statefor local ephemeral UI state (hover flags, input text, dialog selection). - Avoid storing live
Control/component objects in state; store ids/enums and create controls during render.
Workflow
1) Create a new declarative copy
- Copy the existing app folder to a new one (e.g.
trolli→trolli-declarative-*). - Keep
assets/with the new folder.
2) Switch to components mode entrypoint
- Create a root component
@ft.component def App(): .... - Run with:
ft.run(lambda page: page.render(App), assets_dir=...)
- Set page globals either:
- in a
main(page)function beforepage.render(App), or - in
ft.on_mounted(...)(works, but ordering can be less obvious).
- in a
3) Centralize routing in App
- Keep
app.route: stras source of truth. - In one place, define:
route_change(e)to normalize/redirect/validate routes and setapp.route- a render-time
match app.route(or a derivedactive_screen) to pickcontent
- Prefer:
route_changemutates route state;App()render chooses UI based on that state.
4) Componentize UI
- Move UI chunks into
src/components/*.py. - Each component:
- takes only the model(s) it needs
- uses hooks for local UI state
- mutates observable models for app data changes
5) Dialogs: reduce page.update() usage
If a dialog mutates existing controls and calls page.update(), convert it to:
@ft.componentdialog content withft.use_stateforerror,selected_color, etc.- event handlers call setters (no explicit updates)
- show it via
page.show_dialog(ft.AlertDialog(content=DialogContent(...)))
6) Assets/fonts checklist
- Prefer an absolute
assets_dirderived from__file__. - If running via
flet run, be aware it can setFLET_ASSETS_DIRand overrideassets_dir=. - Font registration uses the dict key as the font family name:
page.fonts = {"Pacifico": "Pacifico-Regular.ttf"}- use
font_family="Pacifico".
Common pitfalls (and fixes)
- Event handler typing is invariant (
Event[Sub]≠Event[Base]):- If
on_clickis declared onButton, annotateeasft.Event[ft.Button](or usedef handler(): ...).
- If
TemplateRouteparams are dynamic:raw = getattr(troute, "id", None)thenisinstance(raw, str)beforeint(raw).
controls=[*[...], ...]can confuse type checkers with components:- build lists in two steps and annotate/cast, or return raw controls from non-component factories.
Signals
- GitHub stars
- 17k
- Forks
- 691
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
imperative-to-declarative-flet- Source
- github.com/flet-dev/flet