Verify anything the client will see in a browser

The API can only prove a record is correct, not that the screen looks right, and
a Studio-modified form, a portal page or a report PDF can be wrong while every
API read passes. Adds a "Look at the screen" step: prefer Claude in Chrome (uses
the user's own Odoo session), fall back to a Playwright MCP, and where neither is
installed offer the choice once and accept screenshots rather than blocking the
build on a tool install.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -41,6 +41,9 @@ same-named fork silently shadows upstream depending on install order.
   - On **Odoo.sh**: create the project + enter any partner trial code first (web-only), then come back with the DB URL + API key.
 - Optional: **Knowcap** with its MCP connected, as one possible discovery source → [knowcap.ai](https://knowcap.ai).
 - Optional: the **Perplexity MCP** for the native-vs-custom research step (web search works too).
+- Optional but recommended for UI/website work: a browser tool for visual checks — **Claude in
+  Chrome** (uses your existing Odoo session) or a **Playwright MCP**. Without one, the skill
+  asks you for screenshots instead.
 
 ## Quickstart