Add UIZZE anti-UI-slop skill - #518
Closed
samuelbushi wants to merge 2 commits into
Closed
Conversation
Author
|
Superseded by the current canonical submission in #598; closing the older duplicate so the maintainer has one active UIZZE entry. |
Author
|
Superseded by #598. |
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
1 participant
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.
What changed
Why
UIZZE gives coding-agent users a concrete way to stop generic UI slop: reference real web and iOS patterns, make the design decisions explicit, then verify the rendered result before shipping. The public repository includes an instruction-only skill with no scripts, executables, dependencies, or secret requirements.
Disclosure: I maintain UIZZE.