guiding-manual-editslisted
Install: claude install-skill Nagellabs/libi
# Guiding Manual Edits
When the user wants to make an overlay change **themselves** — "how do I make
this darker?", "I'd rather tweak the rotation by hand", or they reject an edit
you made and want to adjust it — do NOT silently re-edit the overlay. Point them
at the precise inspector control instead.
> **Your own edits feed this hand-off.** Route your OWN placements, transforms,
> and looks through the same controller keys you'd later highlight (per the base
> instruction's controllers-first default) — a value baked into a `code`/`three`
> body has no inspector field to target, so `highlight_property` can't reach it
> when the user wants to take over.
## Be proactive — offer the manual path when your refinements stall
Most users are NOT power-users and don't know these controls exist. A big part of
your job is teaching them — so don't only react when they ask. When the user asks
you to *refine* something and your automated attempts keep missing, **reason about
whether to keep trying or hand them the wheel**, and proactively offer the manual
path.
**Offer manual when:**
- You've genuinely tried once or twice and it's still "not quite" — diminishing
returns from another round of `update_overlay`.
- The tweak is **subjective / taste-based** — an exact color or opacity, a
precise position nudge, the *feel* of a font size or weight, a timing beat.
Eyeballing a slider beats you guessing values blind.
- The user keeps coming back with "a bit more / less / not like that"