practices▌

Language and framework-specific security reviews with actionable vulnerability detection and fix guidance. \n \n Supports Python, JavaScript/TypeScript, and Go with framework-specific best practices loaded from a references directory \n Operates in three modes: secure-by-default code generation, passive vulnerability detection during development, and full security audit reports with severity prioritization \n Generates detailed markdown reports with line-number references, impact statements, and

Comprehensive Vue.js testing guidance covering unit, component, and end-to-end testing strategies. \n \n Addresses 11 common testing challenges including async handling, composable testing, Pinia store setup, Suspense components, and Teleport queries \n Recommends Vitest for unit and component testing infrastructure, with Playwright as the preferred E2E framework \n Covers black-box component testing patterns to reduce brittleness during refactoring, async/await synchronization, and snapshot tes

45 performance optimization rules for React and Next.js, organized by impact and category. \n \n Covers 8 rule categories from eliminating waterfalls and bundle optimization (critical) through JavaScript performance and advanced patterns (low priority) \n Each rule includes explanation, before/after code examples, and context to guide automated refactoring and code generation \n Prioritized by impact: waterfalls and bundle size are critical; server-side performance and re-render optimization are

Comprehensive Vue.js testing guidance covering unit, component, and end-to-end testing strategies. \n \n Addresses 11 common testing challenges including async handling, composable testing, Pinia store setup, Suspense components, and Teleport queries \n Recommends Vitest for unit and component testing infrastructure, with Playwright as the preferred E2E framework \n Covers black-box component testing patterns to prevent brittle tests during refactoring, async/await patterns to eliminate race con

Authoritative guidance for implementing Stripe payment integrations across all use cases. \n \n Prioritizes Checkout Sessions API for on-session payments and subscriptions; recommends Stripe-hosted or embedded Checkout as the primary web integration surface \n Covers payment flows, subscription models, webhooks, Connect platforms, and fund management with explicit guidance on modern APIs versus deprecated endpoints \n Includes pre-launch checklist requirements, PCI compliance considerations, and

React and Next.js performance optimization guidelines across 45 rules in 8 priority categories. \n \n Covers critical waterfalls elimination, bundle size optimization, and server-side performance with specific patterns like Promise.all, dynamic imports, and React.cache() \n Includes medium-priority rules for re-render optimization, rendering performance, and JavaScript efficiency with concrete code examples \n Organized by impact level with prefixed rule names (async-, bundle-, server-, client-,

Comprehensive best practices and integration guides for Sanity CMS development across frameworks and topics. \n \n Covers 10+ framework integrations including Next.js, Nuxt, Astro, Remix, SvelteKit, and Angular with framework-specific patterns and setup guidance \n Includes topic guides for schema design, GROQ query optimization, Visual Editing, Portable Text, images, TypeGen, localization, and content migrations \n Provides quick-reference structure for loading only relevant guides based on tas

45 performance rules for React and Next.js, organized by impact from waterfalls and bundle optimization down to advanced patterns. \n \n Covers 8 rule categories prioritized by impact: eliminating waterfalls (Promise.all, Suspense), bundle size (direct imports, dynamic loading), server-side caching, client-side deduplication, re-render optimization, rendering performance, JavaScript efficiency, and advanced patterns \n Each rule includes explanation, incorrect and correct code examples, and cont

Comprehensive guide to implementing structured, secure, and performant logging across applications. Covers log levels, structured logging formats, contextual information, PII protection, and centralized logging systems.

Idiomatic Rust coding standards based on Apollo GraphQL's best practices handbook. \n \n Covers nine core areas: coding styles and idioms, clippy linting, performance optimization, error handling, testing patterns, generics and dispatch, type state pattern, documentation, and pointer safety \n Emphasizes borrowing over cloning, Result-based error handling with thiserror/anyhow, and performance profiling with release builds \n Includes quick reference guidance on ownership patterns, panic avoidan