domains / families / general / tastegate

tastegate

authentic

Build or fix a frontend so it looks designed, not AI-generated, then prove it in a real browser: renders at phone and desktop width and fails on overlap, low contrast and AI-slop defaults.

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

When not to use

• The gate checks mechanics. It cannot tell you the page is boring, off-brand or wrong for the audience: step 4 is not optional.
• It needs Playwright and headless Chromium installed, and a page it can reach (a file path or a local server).
• A brief that pins fonts, colors or an era overrides the craft floor.
• Does not replace accessibility auditing by a human or real user testing.

Skill page

Source