e2e-tests-studio 是做什麼的？
當修改 packages/playground-ui 或 packages/playground 中的任何檔案時必用。觸發條件：React 元件的新增/修改/重構、UI 變更、新的 Playground 功能、影響 Studio UI 的錯誤修復。生成用於驗證產品行為（而非僅 UI 狀態）的 Playwright E2E 測試。
修改 packages/playground-ui 或 packages/playground 中的任何檔案時必用。觸發條件：React 元件的新增/修改/重構、UI 變更、新的 Playground 功能、影響 Studio UI 的錯誤修復。生成用於驗證產品行為（而非僅 UI 狀態）的 Playwright E2E 測試。
此技能專為開發者在修改 `packages/playground-ui` 或 `packages/playground` 目錄中的檔案時設計。它會自動依據 React 元件的新增、修改或重構，以及 UI 變更、Playground 新功能或 Studio UI 的錯誤修復等情境，觸發 Playwright E2E 測試的生成。與一般僅檢查 UI 狀態的測試不同，此技能生成的測試專注於驗證產品的實際行為，確保業務邏輯和用戶互動在修改後仍能正確運作。支援 Playwright 測試框架，並透過分析變更檔案的背景與目的，產出對應的測試案例。這能顯著提升測試覆蓋率，特別是在進行 UI 相關開發時，協助團隊及早發現行為層面的回歸問題。
npx skills add https://github.com/mastra-ai/mastra/tree/main/skills/e2e-tests-studio當修改 packages/playground-ui 或 packages/playground 中的任何檔案時必用。觸發條件：React 元件的新增/修改/重構、UI 變更、新的 Playground 功能、影響 Studio UI 的錯誤修復。生成用於驗證產品行為（而非僅 UI 狀態）的 Playwright E2E 測試。
This repo contains 4 individual skills — each has its own dedicated page.
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
Tailwind CSS styling guidelines for Mastra Playground UI. This skill should be used when writing, reviewing, or refactoring styling code in packages/playground-ui and packages/playground to ensure design system consistency. Triggers on tasks involving Tailwind classes, component styling, or design tokens.
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".