tailwind最佳實踐 是做什麼的？
Mastra Playground UI的Tailwind CSS樣式指南。在撰寫、審查或重構packages/playground-ui和packages/playground中的樣式程式碼時應使用此技能，以確保設計系統的一致性。會在使用Tailwind類別、元件樣式或設計標記的任務上觸發。
用於Mastra Playground UI的Tailwind CSS樣式指南。在撰寫、審查或重構packages/playground-ui和packages/playground中的樣式程式碼時應使用此技能，以確保設計系統的一致性。會在使用Tailwind類別、元件樣式或設計標記的任務上觸發。
本技能為Mastra Playground UI提供了一組Tailwind CSS樣式指南。當使用者處理`packages/playground-ui`和`packages/playground`套件中的樣式相關任務（例如撰寫、審查或重構Tailwind類別、元件樣式或設計標記）時，它會自動觸發，確保整個專案的設計系統保持一致。此技能的目標是減少樣式差異，強制遵循統一的CSS架構，並確保元件符合共同視覺語言。它作為開發者的即時參考，協助他們在特定專案目錄內應用正確的Tailwind慣例、設計階層和標記使用方式。透過與Mastra Playground的現有模式保持一致，它簡化了樣式審查流程，並在專案擴展時防止樣式偏離。
npx skills add https://github.com/mastra-ai/mastra/tree/main/skills/tailwind-best-practicesMastra Playground UI的Tailwind CSS樣式指南。在撰寫、審查或重構packages/playground-ui和packages/playground中的樣式程式碼時應使用此技能，以確保設計系統的一致性。會在使用Tailwind類別、元件樣式或設計標記的任務上觸發。
This repo contains 4 individual skills — each has its own dedicated page.
REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.
Interactive planning assistant that helps create focused, well-structured ralph-loop commands through collaborative conversation
React performance optimization guidelines from Mastra Engineering. This skill should be used when writing, reviewing, or refactoring React code to ensure optimal performance patterns. Triggers on tasks involving React components, data fetching, bundle optimization, or performance improvements.
Create a Mastra project using create-mastra and smoke test the studio in Chrome using Chrome MCP server
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".