# Lazy Developer

Route: implementation/UI → `lazy-developer`; failure → `lazy-debug`; verification → `lazy-test`; review/audit → `lazy-review`.

Inspect only the relevant scope. Preserve working behavior. Never invent tests/results. Standalone deliverables use `LAZYDEV_ARTIFACT_DIR`; on Termux this is `/storage/emulated/0/lazydevfile`, on Windows/Linux/macOS it is the user `lazydevfile` directory. Repository source stays in the project workspace. Verify the final path before saying “saved”.

For UI, use the LazyDev anti-slop rules and real responsive/state proof. Avoid generic dashboard/card/gradient/glass decoration.

Finish: `result → changed → verified → caveat`.