- Home
- /
- Categories
- /
- Caching
Caching
Caching strategies and implementation
wayback-check
by Mearman
Check if a URL is archived in the Wayback Machine. Use when the user asks to check archive status, verify if a page is saved, or find archived versions of a URL.
swift-development
by ProjAnvil
提供 Swift 6+ 核心语言开发能力,涵盖并发编程、宏、数据模型设计和业务逻辑实现。
wayback-cache
by Mearman
Manage Wayback Machine API cache. Use when clearing cached data, checking cache status, or bypassing cache for fresh API responses. Applies to all wayback operations (check, list, screenshot).
gravatar-check
by Mearman
Check if a Gravatar exists for an email address. Use when the user wants to verify if someone has a Gravatar, check avatar availability, or validate email addresses against Gravatar's database.
npm-downloads
by Mearman
Get download statistics for an npm package over time. Use when the user asks for package download counts, popularity metrics, or usage statistics.
runbook
by thoreinstein
Generate operational runbooks for services, procedures, or incident response with step-by-step procedures, troubleshooting guides, and escalation paths
SiteGround Cache Buster Skill
by CrazySwami
visual-qa - Screenshot testing after changes
pdf-to-markdown
by aliceisjustplaying
Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.
sqldown
by mbailey
Bidirectional markdown ↔ SQLite conversion with column limit protection and smart section extraction. Import with Python, query with sqlite3.
depot-container-builds
by depot
Configures and runs Depot remote container builds using depot build and depot bake. Use when building Docker images, creating Dockerfiles with Depot, pushing images to registries, building multi-platform/multi-arch images (linux/amd64, linux/arm64), debugging container build failures, optimizing Dockerfile layer caching, using docker-bake.hcl or docker-compose builds, or migrating from docker build / docker buildx build to Depot. Also use when the user mentions depot build, depot bake, container builds, image builds, or asks about Depot's build cache, build parallelism, or ephemeral registry.
keyvhq
by microlinkhq
Build and operate Keyv-based caching and key-value storage using @keyvhq/core and official adapters. Use when the user mentions Keyv, keyvhq, TTL cache, namespaces, storage adapters (Redis, Mongo, MySQL, PostgreSQL, SQLite, file), or adding cache support to a Node.js module.
turborepo
by rockcookies
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
@tank/system-design
by tankpkg
Practical system design for production distributed systems. Covers scalability patterns (load balancing, horizontal scaling, CDN, auto-scaling), data layer design (database selection, replication, sharding, consistency models, CAP theorem applied), caching strategies (cache-aside, write-through, invalidation, stampede prevention), messaging and async patterns (queues vs streams, event-driven architecture, CQRS, saga pattern, delivery guarantees), reliability (circuit breakers, bulkheads, retries, rate limiting, timeouts, chaos engineering), service architecture (monolith vs microservices, API gateway, service mesh, distributed transactions), and capacity planning (back-of-envelope estimation, SLOs/SLIs, monitoring, distributed tracing). Synthesizes Kleppmann (Designing Data-Intensive Applications), Vitillo (Understanding Distributed Systems), Newman (Building Microservices), Ford et al. (Software Architecture: The Hard Parts), Nygard (Release It!), Petrov (Database Internals), Richards & Ford (Fundamentals of Software Architecture), and Beyer et al. (Site Reliability Engineering). Trigger phrases: "system design", "distributed systems", "scalability", "load balancing", "horizontal scaling", "vertical scaling", "database sharding", "database replication", "caching strategy", "cache invalidation", "message queue", "event-driven", "Kafka", "RabbitMQ", "pub/sub", "circuit breaker", "rate limiting", "bulkhead", "retry strategy", "microservices", "monolith", "API gateway", "service mesh", "CAP theorem", "eventual consistency", "strong consistency", "CQRS", "event sourcing", "saga pattern", "back-of-envelope", "SLO", "SLI", "capacity planning", "distributed tracing", "back pressure", "cache stampede", "thundering herd", "how should I scale", "which database", "when to use microservices"
@tank/nextjs
by tankpkg
"Expert Next.js App Router execution guide for server-first rendering, caching, routing, and deployment. Triggers: nextjs, next.js, app router, server component, client component, server action, route handler, middleware, SSR, SSG, ISR, caching, revalidation, streaming, suspense, parallel routes, intercepting routes, next/image, metadata, layout."
depot-github-runners
by depot
Configures Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners. Use when setting up or migrating GitHub Actions workflows to use Depot runners, choosing runner sizes (CPU/RAM), configuring runs-on labels, setting up ARM or Windows or macOS runners, troubleshooting GitHub Actions runner issues, configuring egress filtering, using Depot Cache with GitHub Actions, or running Dagger/Dependabot on Depot runners. Also use when the user mentions depot-ubuntu, depot-windows, depot-macos runner labels, or asks about faster/cheaper GitHub Actions runners.
gcp-batch-inference
by viktor-ferenczi
Running batch inference on Google Cloud (also known as Vertex AI)
moai-baas-vercel-ext
by AJBcoding
Enterprise Vercel Edge Platform with AI-powered modern deployment, Context7 integration, and intelligent edge orchestration for scalable web applications
moai-context7-integration
by AJBcoding
"Enhanced context7 integration with AI-powered features"
turborepo-caching
by EngineerWithAI
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
data-fetching
by pluginagentmarketplace
"Next.js data fetching - Server actions, caching, revalidation"
redis-daemon
by fast-gateway-protocol
Fast Redis operations via FGP daemon - 15-50x faster than spawning redis-cli per command. Use when user needs to get/set cache values, manage keys, pub/sub, or work with Redis data structures. Triggers on "redis get", "redis set", "cache", "redis-cli", "get key", "set key".
buffer-overflow
by tangjunyi23
Buffer overflow vulnerability hunting in IoT embedded binaries. Use when reverse-engineering ARM/MIPS/x86 binaries for stack-based or heap-based overflow vulnerabilities, analyzing unsafe memory operations (strcpy, sprintf, gets, memcpy), checking binary protections (NX, ASLR, canary), or building overflow PoCs for embedded targets.
web-performance
by AlexanderStephenThompson
Performance patterns for Apollo caching, Redis, and CloudFront optimization
state-management
by mrsknetwork
Designs and implements state management architecture for both frontend (global client state, server cache, URL state) and backend (Redis caching, session management, distributed locks). Use when a user needs to share data across components without prop drilling, cache expensive API responses, sync state to the URL, manage Redis, or prevent race conditions in concurrent server operations. Trigger when user mentions "global state", "Zustand", "Redux", "React Query", "caching", "Redis", "session", "why does my data disappear on page refresh", or "how do I share state across pages".