ioredis
ioredis v5 reference for Node.js Redis client — connection setup, RedisOptions, pipelines, transactions, Pub/Sub, Lua scripting, Cluster, and Sentinel. Use when: (1) creating or configuring Redis connections (standalone, cluster, sentinel), (2) writing Redis commands with ioredis (get/set, pipelines, multi/exec), (3) setting up Pub/Sub or Streams, (4) configuring retryStrategy, TLS, or auto-pipelining, (5) working with Redis Cluster options (scaleReads, NAT mapping), or (6) debugging ioredis connection issues. Important: use named import `import { Redis } from 'ioredis'` for correct TypeScript types with NodeNext.
Works with
---
name: ioredis
description: ioredis v5 reference for Node.js Redis client — connection setup, RedisOptions, pipelines, transactions, Pub/Sub, Lua scripting, Cluster, and Sentinel. Use when: (1) creating or configuring Redis connections (standalone, cluster, sentinel), (2) writing Redis commands with ioredis (get/set, pipelines, multi/exec), (3) setting up Pub/Sub or Streams, (4) configuring retryStrategy, TLS, or auto-pipelining, (5) working with Redis Cluster options (scaleReads, NAT mapping), or (6) debugging ioredis connection issues. Important: use named import `import { Redis } from 'ioredis'` for correct TypeScript types with NodeNext.
license: MIT
---
# ioredis v5 — Node.js Redis Client
ioredis v5.x. Requires Node.js >= 12, Redis >= 2.6.12. 100% TypeScript.
<quick_reference>
## Critical: Import Style
```ts
// CORRECT — named import (required for NodeNext / moduleResolution: "nodenext")
import { Redis } from "ioredis";
// For Cluster:
import { Redis, Cluster } from "ioredis";
```
## Quick Reference
| Operation | Code |
| -------------- | -------------------------------------------------------------------------- |
| Connect | `new Redis()` or `new Redis(6379, "host")` or `new Redis("redis://...")` |
| Get/Set | `await redis.set("key", "val")` / `await redis.get("key")` |
| Pipeline | `await redis.pipeline().set("a","1").get("a").exec()` |
| Transaction | `await redis.multi().set("a","1").get("a").exec()` |
| Pub/Sub | `sub.subscribe("ch")` / `sub.on("message", cb)` / `pub.publish("ch", msg)` |
| Lua script | `redis.defineCommand("name", { numberOfKeys: 1, lua: "..." })` |
| Scan | `redis.scanStream({ match: "prefix:*", count: 100 })` |
| Graceful close | `await redis.quit()` |
| Force close | `redis.disconnect()` |
</quick_reference>
<gotchas>
## Common Gotchas
1. **Named import**: Always `import { Redis } from "ioredis"` with NodeNext resolution
2. **Pub/Sub isolation**: A subscribed client cannot run other commands — use separate instances
3. **`maxRetriesPerRequest`**: Default is 20. Set to `null` for infinite retries (required by BullMQ)
4. **Pipeline errors**: `pipeline.exec()` never rejects — errors are in each result's `[0]` position
5. **`showFriendlyErrorStack`**: Performance cost — never enable in production
6. **Cluster pipelines**: All keys in a pipeline must hash to slots served by the same node
7. **`enableAutoPipelining`**: 35-50% throughput improvement, safe to enable globally
</gotchas>
<references>
## When to Load References
| Need | Reference file |
| ------------------------------------------------------------------------------ | -------------------------------------------------------------------- |
| Connection setup, RedisOptions, TLS, retryStrategy, lifecycle | [references/connection-options.md](references/connection-options.md) |
| Core API: pipelines, transactions, Pub/Sub, Lua scripting, scanning, events | [references/core-api.md](references/core-api.md) |
| Streams, auto-pipelining, transformers, binary data, error handling, debugging | [references/advanced-patterns.md](references/advanced-patterns.md) |
| Redis Cluster setup, ClusterOptions, Sentinel config, failover | [references/cluster-sentinel.md](references/cluster-sentinel.md) |
</references>More Database skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prisma-postgres
prisma/skills
Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.

