Tastegate

Overview

Two skills in one, plus the part both leave to the model: proof.

1. Taste decides what the page should be, before any code.
2. The craft floor holds the mechanics every page must meet.
3. The gate renders the page in a real browser at phone and desktop width and refuses "done" while any hard finding is open.

A model that wrote the CSS cannot see that its hero overlaps its nav at 390px. The browser can. Work through the four steps in order, and apply the checklists rather than announcing them.

When to Use

• Use for any UI build: landing page, marketing site, dashboard, app screen, component
• Use for a redesign, a polish pass, or a "make it look better" request
• Use when a page needs to stop looking AI-generated
• Use before calling any frontend work done, as the proof step