docs(ux-ui): clarify when custom CSS is appropriate - #348
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
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.
Before. The ux-ui skill restricted custom CSS to styles utilities cannot express, encouraging awkward utility expressions even when CSS would be clearer.
Now. Keep Tailwind for component styling and components with variants for repeated UI. Allow custom CSS for generated content, document-level rules, and complex effects where utilities would obscure the implementation.
Verification
Completed checks
quick_validate.py .agents/skills/ux-ui— passed.git diff --check— passed.