practices▌
172 indexed skills · max 10 per page
frontend-react-best-practices
sergiodxa/agent-skills · Frontend
33 React performance and composition rules across bundle optimization, re-rendering, rendering, hooks, and component patterns. \n \n Covers 6 rule categories: bundle size optimization (barrel imports, conditional loading, preloading), re-render prevention (functional setState, derived state, memoization), rendering performance (content-visibility, hydration, transitions), client patterns (passive listeners, localStorage versioning), hooks best practices (limiting useEffect, named functions), and
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
home-assistant-best-practices
homeassistant-ai/skills · Productivity
Native Home Assistant constructs for automations, helpers, scripts, and Lovelace dashboards. \n \n Prioritizes built-in conditions, triggers, and helpers over Jinja2 templates; includes decision workflow for choosing between native state conditions, numeric_state, time triggers, and template helpers \n Covers automation modes (single, restart, queued, parallel) with scenarios, entity_id vs device_id usage, and Zigbee button/remote patterns for ZHA and Zigbee2MQTT \n Provides safe refactoring wor
react-native-best-practices
software-mansion-labs/skills · Frontend
Software Mansion's production patterns for React Native apps on the New Architecture.
tanstack-integration-best-practices
deckardger/tanstack-agent-skills · Productivity
Architectural patterns for coordinating TanStack Query, Router, and Start across full-stack applications. \n \n Covers setup, data flow, caching, and SSR integration with 13 rules organized by priority and category \n Emphasizes loader-based data fetching with ensureQueryData, suspense queries in components, and server functions as query sources \n Provides unified caching and invalidation strategies to prevent duplication and ensure single source of truth \n Includes automatic SSR dehydration/h
logging-best-practices
aj-geddes/useful-ai-prompts · Productivity
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.
next-best-practices
vercel/nextjs-skills · Frontend
Apply these rules when writing or reviewing Next.js code.
python-best-practices
0xbigboss/claude-code · Backend
Type-first Python development using dataclasses, discriminated unions, NewType, and Protocol to make illegal states unrepresentable. \n \n Define data models and function signatures before implementation; use frozen dataclasses, Literal-based discriminated unions, and NewType for domain primitives to prevent invalid states at type-check time \n Leverage Protocol for structural typing, TypedDict for external data shapes, and exhaustive pattern matching with match statements to catch incomplete lo
docker-best-practices
josiahsiegel/claude-plugin-marketplace · Cloud
Comprehensive Docker best practices for images, containers, and production deployments. \n \n Covers base image selection (Wolfi/Chainguard, Alpine, Distroless), Dockerfile structure with optimal layer ordering, multi-stage builds, and layer optimization techniques to minimize image size and build time \n Includes container runtime security patterns: running as non-root, dropping capabilities, read-only filesystems, resource limits, health checks, and logging configuration \n Provides Docker Com
frontend-testing-best-practices
sergiodxa/agent-skills · Frontend
End-to-end testing focused on real user behavior, minimal mocking, and avoiding component unit tests. \n \n Prioritizes E2E tests over unit tests; reserves unit tests for pure functions only \n Emphasizes accessible selectors (role-based, label-based) over CSS selectors and test IDs in E2E tests \n Recommends writing E2E tests instead of heavily mocked unit tests; suggests 3+ mocks as a signal to switch approaches \n Includes rules for test structure, selector strategy, and when to apply each te