docs(ux-ui): require Tailwind utilities and component reuse - #347
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. UI guidance did not require Tailwind, and the frontend-design skill advised on custom CSS selectors. Agents could therefore style interfaces with plain CSS or share styling through custom classes.
Now. The ux-ui skill requires Tailwind utilities and reusable components with variants, reserving CSS files for Tailwind setup, theme tokens, and styles utilities cannot express. Remove the competing selector-specificity advice from frontend-design, keeping the rule out of AGENTS.md and unrelated sessions.
Verification
Completed checks
quick_validate.py .agents/skills/ux-ui— passed.quick_validate.py .agents/skills/frontend-design— passed.git diff --check— passed.