Master Tailwind CSS v4 with its CSS-first configuration paradigm. Use when writing utility classes, configuring design tokens via @theme, implementing dark mode, migrating from v3, or integrating with React/Vue/Svelte. Triggers on "Tailwind", "utility CSS", "Tailwind v4", "@theme", "dark mode classes", "responsive…
Skill "trpc" from neverinfamous/memory-journal-mcp, covering trpc guidelines, 1. routers and procedures, 2. context and middleware and 3. client integration.
Comprehensive enterprise-grade TypeScript operational guide. Use when configuring TS projects, writing complex generics, or enforcing strict type safety. Triggers on "TypeScript", "tsconfig.json", "generics", "type errors", "strict mode". SECURITY: Do not bypass type checks with 'any' or '@ts-ignore'.
Vercel AI SDK best practices and patterns. Use when building AI applications with React/Next.js and @ai-sdk/react, @ai-sdk/core, or @ai-sdk/ui. Covers useChat, streamText, generateObject, tool calling, and streaming architectures. SECURITY: Never pass raw user inputs to executable tools without strict Zod schema…
Comprehensive unit testing expertise covering Vitest, test-driven development (TDD), mocking strategies, and production-grade best practices. Activates ONLY for unit testing scope (unit tests, integration tests, Vitest, TDD, Red-Green-Refactor, mocking, stubbing, spying, test coverage, and test architecture in…
(APPLICATION CODE ONLY) Reviews and authors Cloudflare Workers code against production best practices. Use ONLY when writing or reviewing Worker code, configuring wrangler.jsonc, or checking for anti-patterns. Do NOT use for general Cloudflare product discovery (use cloudflare instead) or CLI management (use wrangler…
(CLI OPERATIONS ONLY) Cloudflare Wrangler CLI dispatcher. Use ONLY when Cloudflare Workers or Pages is the explicitly named target platform for deployment, or when managing Cloudflare bindings using the wrangler CLI. Do NOT use for general Cloudflare product discovery (use cloudflare instead) or for writing/reviewing…
Zod schema validation standards. Use when defining schemas, parsing user input, transforming data, or integrating type-safe boundaries in API endpoints and configurations. SECURITY: Zod schemas are your primary security boundary. Ensure they are strict and handle all edge cases.
Use when working with Datadog: monitoring, dashboards, APM, logs, RUM, SLOs, downtimes, or auth via the pup CLI. Triggers on: "Datadog", "DDAPIKEY", "pup", "monitors", "APM", "RUM", "SLO", "downtime". Do NOT trigger for generic observability/tracing without Datadog explicitly mentioned (use opentelemetry instead).
Bootstrap evaluators from production traces — by default propose online LLM-judge evaluators and, after you confirm, create them in Datadog as disabled drafts (never auto-enabled); on request emit Python SDK code or a framework-agnostic JSON spec instead. Use when user says "bootstrap evaluators", "generate…
End-to-end Agent Observability pipeline for an instrumented mlapp — classify production traces, root-cause failures, bootstrap evaluators, then (optionally) sample + publish a dataset, generate + run an experiment, and analyze results. Six narrated phases with a standardized banner and a "continue" checkpoint between…
Analyze LLM experiment results. Handles single or comparative experiments, exploratory or Q&A modes. Use when user says "analyze experiment", "compare experiments", "analyze against baseline", or provides one or two experiment IDs for analysis.
Classify whether user intent was satisfied in a Datadog Agent Observability trace or session. Three modes: (1) sessionid — classify a single CMD+I assistant session with RUM; (2) traceid — classify a single Agent Observability trace without RUM; (3) mlapp — sample and classify multiple sessions or traces from a given…
Root cause analysis on production LLM traces. Diagnoses why an LLM application is failing — works from eval judge verdicts, runtime errors, or structural anomalies depending on what signals are present. Walks the span tree from symptom to root cause. Use when user says "what's wrong with my app", "why is my eval…
Install the Datadog Agent on Kubernetes using the Datadog Operator — required before enabling Single Step Instrumentation (SSI), which automatically instruments applications for APM without code changes. Only use if no Datadog Agent is deployed on the cluster yet.
Enable Single Step Instrumentation (SSI) on Kubernetes — automatically instruments applications for APM without code changes. Only use if the Datadog Agent is already running on the cluster — if not, use agent-install first.
Generate a live Single Step Instrumentation (SSI) onboarding confirmation report — verifies APM instrumentation is working end-to-end with deep links into the Datadog UI. Only use after agent-install and enable-ssi have both completed successfully.
Diagnose and fix Single Step Instrumentation (SSI) issues on Kubernetes — SSI automatically instruments applications for APM without code changes. Only use if the agent and SSI are already configured but traces are missing or instrumentation is not working.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: