docs: add in-browser UI verification convention to AGENTS.md#75
Open
alchemydc wants to merge 1 commit into
Open
docs: add in-browser UI verification convention to AGENTS.md#75alchemydc wants to merge 1 commit into
alchemydc wants to merge 1 commit into
Conversation
Require confirming UI root causes in-browser before fixing, and verifying at mobile + desktop breakpoints after — targets redo cycles from breakpoint/root-cause assumptions. Co-Authored-By: Claude Fable 5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a short
## UI changessection to AGENTS.md: confirm UI root causes in-browser (chrome-devtools MCP) before implementing a fix, and verify at both mobile and desktop breakpoints after.Why
A /insights review of recent sessions found three UI fixes (loading skeletons, mobile overflow, back button) that each needed a second pass because the first implementation rested on an unverified assumption about the breakpoint or the responsible element. This makes in-browser verification an explicit agent convention.
🤖 Generated with Claude Code