From 95531a39c0d7038f21391ee667c7f4ed96c16481 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Mon, 11 May 2026 15:45:36 +0200 Subject: [PATCH] How to evolve features that require input and interaction --- AGENTS.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index e2137999..617ef28d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -97,6 +97,10 @@ Exceptions are allowed for bootstrap, preflight, migration, and package-helper s When making visual changes, such as Waybar styles or desktop appearance, always take and analyze a screenshot after applying the change to verify the result. Use `omarchy capture screenshot fullscreen save` for fullscreen screenshots. +For interactive UI work, use `wtype` to simulate keyboard input when available. Example: start the UI in the background, wait briefly for focus, then run `wtype -k Right -k Return` to exercise keyboard selection and confirm the resulting command output or state change. Prefer this over manual-only verification when a UI returns a selected value or changes a symlink/config. + +When testing layer-shell UI, capture the reference and candidate states as separate screenshots, then compare them visually before further edits. If a launched UI would otherwise remain open, keep track of its PID and stop it after the screenshot; avoid broad process kills unless checking with `ps` first. + # Refresh Pattern To copy a default config to user config with automatic backup: