best▌

Follows type-first, functional, and error handling patterns from CLAUDE.md. This skill covers Zig-specific idioms only.

Native TypeScript support in Node.js with type stripping, async patterns, error handling, and production best practices. \n \n Covers type stripping (Node.js 22.6+) for running .ts files directly without build tools; includes tsconfig.json setup and import extension rules \n Provides patterns for error handling, graceful shutdown, async/await, streams, and module resolution across the full Node.js stack \n Includes diagnostic workflows for flaky tests, profiling slow paths, and performance optim

Cloudflare Workers code review and authoring against production best practices. \n \n Retrieves latest Workers APIs, types, and wrangler configuration schema before reviewing or writing code; biases towards live documentation over pre-trained knowledge \n Covers 40+ best practice rules across configuration, request/response handling, architecture, observability, code patterns, and security \n Flags 15+ common anti-patterns including unbounded streaming, floating promises, global request state, h

Best practices and patterns for Manim Community Edition, the Python animation engine for mathematical visualizations. \n \n Covers Scene structure, mobject types, 15+ animation classes, and LaTeX/MathTex rendering with color control \n Includes 3D support via ThreeDScene, camera manipulation, updaters with ValueTracker, and coordinate systems (Axes, NumberPlane) \n Provides organized rule files for core concepts, text/math, styling, positioning, timing, and CLI usage with quality flags \n Includ

WordPress performance optimization guidelines across database, caching, assets, and plugin architecture. \n \n 34 rules organized by impact across 8 categories: database optimization, caching strategies, asset management, theme performance, plugin architecture, media optimization, API/AJAX, and advanced patterns \n Covers critical areas including WP_Query optimization, transient and object cache usage, proper asset enqueueing, and REST API caching \n Designed for code review and generation workf

51 rules for writing clean, type-safe, modern PHP 8.x code aligned with PSR standards and SOLID principles. \n \n Covers 7 rule categories: type system, modern PHP features (8.0–8.5), PSR standards, SOLID principles, error handling, performance, and security \n Version-aware guidance that detects PHP version from composer.json and runtime, recommending only features available in the target version \n Organized by priority: type safety and security are critical; modern features and SOLID principl

Vue 3 Options API patterns, TypeScript integration strategies, and context-binding gotchas. \n \n Covers TypeScript type safety for component properties, this context, prop validators, event handlers, complex types, provide/inject, and computed return types \n Addresses common method and lifecycle hook pitfalls: arrow function binding issues, context loss, and stateful method state leakage across instances \n Organized as a reference guide with linked examples for each pattern and anti-pattern \

Server Components by default, client interactivity on demand, with structured data fetching and caching strategies. \n \n Server Components handle data fetching and static content; Client Components ('use client') manage forms, state, and event handlers. Split responsibilities when both are needed. \n Data fetching uses static caching by default, with ISR (time-based revalidation) and dynamic (no-store) options for different freshness requirements. \n Routing relies on file conventions (page.tsx

Node.js architecture and framework selection guidance based on deployment context and project requirements. \n \n Framework decision tree covers Hono (edge/serverless), Fastify (performance), NestJS (enterprise), and Express (legacy), with selection criteria tied to cold start time, ecosystem size, and team experience \n Covers layered architecture principles (controller, service, repository), async patterns (async/await vs Promise.all/allSettled), and centralized error handling with appropriate

Decision guide for Stripe API selection, Connect setup, billing, and integration patterns. \n \n Routes integration decisions across six domains: one-time payments (Checkout Sessions), custom payment forms (Payment Element), saved payment methods (Setup Intents), marketplaces (Accounts v2), subscriptions (Billing APIs), and embedded financial accounts (Treasury) \n Provides reference documentation for each integration type, including API version guidance (latest: 2026-02-25.clover) and pre-launc