Styling guidelines for the Mastra Playground UI, containing 5 rules across 3 categories. Rules are prioritized by impact to guide automated refactoring and code generation. These rules ensure design system consistency, prevent token drift, and maintain component library integrity.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontailwind-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
Fetches tailwind-best-practices from mastra-ai/mastra and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tailwind-best-practices. Access via /tailwind-best-practices in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
22.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
22.7K
stars
Styling guidelines for the Mastra Playground UI, containing 5 rules across 3 categories. Rules are prioritized by impact to guide automated refactoring and code generation. These rules ensure design system consistency, prevent token drift, and maintain component library integrity.
packages/playground-uipackages/playgroundReference these guidelines when:
Rules are prioritized by impact:
| Priority | Category | Impact |
|---|---|---|
| 1 | Component Usage | CRITICAL |
| 2 | Design Tokens | CRITICAL |
| 3 | ClassName Usage | HIGH |
Component Usage:
@playground-ui/ds/components/ (component-use-existing)ds/ folderDesign Tokens:
tailwind.config.ts in @playground-ui (tokens-use-existing)tailwind.config.ts (tokens-no-modification)ClassName Usage:
height and width (classname-no-arbitrary)className prop on DS components except h-/w- on DialogContent and Popover (classname-no-ds-override)Full documentation with code examples is available in:
references/tailwind-best-practices-reference.md - Complete guide with all patternsreferences/rules/ - Individual rule files organized by categoryTo look up a specific pattern, grep the rules directory:
grep -l "component" references/rules/
grep -l "token" references/rules/
grep -l "className" references/rules/
references/rules/component-* - Component usage rules (1 rule)tokens-* - Design token rules (2 rules)classname-* - ClassName usage rules (2 rules)Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
asyrafhussin/agent-skills
jwynia/agent-skills
kadajett/agent-nestjs-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
tailwind-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
tailwind-best-practices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend tailwind-best-practices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
tailwind-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in tailwind-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
tailwind-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: tailwind-best-practices is focused, and the summary matches what you get after install.
tailwind-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend tailwind-best-practices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: tailwind-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 40