best▌

Multi-tenant organization setup with member management, role-based access control, and team support via Better Auth. \n \n Configure organizations with customizable creation rules, membership limits, and ownership constraints; creators automatically receive the owner role \n Manage members and invitations with email delivery, expiration windows, and shareable invitation URLs; support multiple roles per member \n Define custom roles and permissions with dynamic access control; check permissions s

Comprehensive SEO and AEO optimization guidance covering metadata, structured data, EEAT, and AI-readiness. \n \n Covers both traditional search engine optimization (SEO) and AI answer engine optimization (AEO) across Google, ChatGPT, Perplexity, and similar platforms \n Includes technical SEO essentials: metadata, Open Graph tags, sitemaps, robots.txt, hreflang, and international SEO configuration \n Provides JSON-LD structured data patterns for Article, FAQ, Breadcrumb, and Product schemas \n

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

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

Structured logging pattern using wide events for comprehensive request-level debugging and analytics. \n \n Consolidates all request context into a single JSON event per service, emitted at completion, rather than scattering log lines throughout handlers \n Emphasizes high cardinality fields (user IDs, request IDs) and high dimensionality (many fields per event) to enable flexible querying and correlation across services \n Requires business context in every event: subscription tier, cart value,

Standard Vue 3 workflow with Composition API, <script setup> , and TypeScript as the default approach. \n \n Requires confirming project architecture upfront and reading core references on reactivity, SFCs, component data flow, and composables before implementation \n Enforces minimal source state with ref / reactive , deriving everything possible with computed , and keeping templates declarative \n Mandates component splitting when responsibilities exceed one clear purpose, with entry/root

better-auth-security-best-practices

Email verification, password reset flows, and customizable password policies for Better Auth. \n \n Supports email verification with optional enforcement to block sign-in until verified, plus configurable token expiration and single-use reset tokens \n Password reset flows with built-in security: background email sending, timing attack prevention, dummy operations on invalid requests, and optional session revocation on reset \n Configurable password length limits (default 8–256 characters) and c

Vue Pinia state management patterns, store setup guidance, and reactivity best practices. \n \n Covers store initialization, DevTools integration, and SSR considerations for setup stores \n Addresses common reactivity pitfalls including destructuring breaks and method binding issues in templates \n Provides patterns for ephemeral state like filters, URL synchronization, and production app conventions \n References specific error scenarios with linked solutions for quick troubleshooting \n

Postgres performance optimization rules across 8 priority categories, from query tuning to advanced features. \n \n Organized into 8 rule categories prioritized by impact: query performance and connection management (critical), security and RLS, schema design, concurrency, data access patterns, monitoring, and advanced features \n Each rule includes detailed explanations, incorrect vs. correct SQL examples, EXPLAIN output analysis, and performance metrics to guide optimization decisions \n Cover