harden

/harden

Prep a screen for production. Add the safety scaffolding most AI- generated code misses.

When to use

• Taking a prototype to production
• After /audit shows errors in code-quality category
• Before a real-user launch

Actions

1. Check design context: If .klamben.md exists in the project root, read it first. Apply the project's brand, platform targets, accessibility tier, and existing patterns to your work below.
2. Loading states: Any async button/action gets a _loading flag and disabled-while-loading UI
3. Error states: Wrap async calls in try/catch; show user-facing error (SnackBar or inline); log to debugPrint
4. Empty states: Any list screen gets a meaningful empty state
5. Mounted guards: Every setState or context use after await gets if (!mounted) return;
6. Dispose: Every *Controller field in State gets disposed in dispose()
7. Null safety: ! → explicit null check where possible
8. Swallowed errors: Empty catch (_) → logged + reported

Output

harden lib/screens/home.dart

+ late bool _loading = false;
+ try/catch around api.save() with user-facing SnackBar on error
+ if (!mounted) return; guards on 3 async methods
+ @override void dispose() { _controller.dispose(); super.dispose(); }
+ Empty state widget when items.isEmpty

8 safety additions.
Run tests before committing.

Do NOT

• Change business logic
• Add features the user didn't ask for
• Touch unrelated screens