Repository navigation
docs: add frontend ui stability guidelines - #173
Merged
nunomaduro merged 1 commit intoOct 16, 2026
Merged
Conversation
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.
Problem
Agents keep shipping UI that flashes, jumps or clips. #156 fixed a long list of these across the app, and the same kinds of problems came straight back in new feature PRs:
Nothing in the agent guidelines told anyone to watch for this, or how to check for it.
What changes
.ai/guidelines/resources.js.blade.phpadds a short "Frontend UI stability" section, written from what fix: remove layout jumps, flashes and clipped ui across the app #156 and the follow-up polish actually fixed:Inertia::defer(...)->once(), and polling uses partial reloads.tabular-nums, buttons whose label changes get amin-w, and conditional UI reserves its space. Removed rows collapse instead of jumping, and the control under the cursor doesn't flip to a destructive state right after an action.scrollbar-gutter: stable. Long text truncates, textareas areoverflow-x-hidden, and inputs use at least 16px on mobile. Toasts sit above the bottom nav.productionusing the same demo data.AGENTS.md/CLAUDE.md: regenerated withphp artisan boost:update --no-discover --ignore-skills, not edited by hand.DESIGN.md: one "Do" line pointing to the new rules.Regenerating also picked up the Laravel Octane core rules, which were missing because the guidelines hadn't been regenerated since Octane was added in 8ffa0b3. They're Boost's own output, so I left them in. Those rules mention an
octane-developmentskill that isn't installed here; installing it is a separate change.Validation
php artisan boost:updateregeneratedAGENTS.mdandCLAUDE.md. Both contain the new section and are identical to each other.