Repository navigation
[autopilot] skills: ui-design anti-patterns for template look and single-platform targets - #164
Merged
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.
Adds two anti-patterns to designing-interfaces. Motivating patterns: (1) reviewers repeatedly rejected UIs that stacked individually-common choices (indigo/purple primary, identical rounded card grids with tinted icon tiles, pastel chips, window-dot mockups, floating badges, colored headline words) as reading as generated; the skill now names the combination and gives a concrete alternative identity. (2) Design targets drawn for only one platform were rejected when the product ships on several; the skill now requires targets and screenshots per shipped platform. Readers get sharper audit criteria for 'looks generic' feedback.