practices▌
172 indexed skills · max 10 per page
rust-best-practices
apollographql/skills · Backend
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
vueuse-best-practices
hyf0/vue-skills · Frontend
VueUse composable patterns, SSR compatibility, and TypeScript integration best practices. \n \n Covers SSR-specific gotchas and patterns for safely using VueUse composables in server-rendered environments \n Addresses common issues with element ref handling and type inference when working with VueUse APIs \n Provides efficiency rules to help debug and resolve VueUse integration problems consistently \n
node-best-practices
mcollina/skills · Backend
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
workers-best-practices
cloudflare/skills · Productivity
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
manimce-best-practices
adithya-s-k/manim_skill · Productivity
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-best-practices
bartekmis/wordpress-performance-best-practises · Productivity
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
vue-options-api-best-practices
vuejs-ai/skills · Frontend
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 \
nextjs-best-practices
davila7/claude-code-templates · Frontend
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
stripe-best-practices
stripe/ai · Productivity
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
vercel-react-best-practices
lobehub/lobehub · Frontend
45 React and Next.js performance rules organized by impact, from eliminating waterfalls to advanced patterns. \n \n Covers 8 priority categories spanning async optimization, bundle size, server/client data fetching, re-renders, rendering, JavaScript performance, and advanced patterns \n Each rule includes explanation, before/after code examples, and context; rules prefixed by category (e.g., async- , bundle- , server- ) for easy reference \n Prioritizes critical issues like waterfall elimination