feat: add redis development plugin

[saoudrizwan]

Redis Development

Adds a Redis development plugin for Cline that helps with practical Redis application and operations work: data modeling, key naming, Redis Query Engine, vector search, connection tuning, clustering, ACL/TLS/network security, observability, Redis LangCache, and Redis Agent Memory.

The plugin is intentionally offline at install time. It does not start Redis, connect to Redis Cloud, register an MCP server, or run third-party code just to become available.

Cline Primitives

This plugin uses bundled skills and a safety rule.

The bundled skills cover Redis Core, Redis Query Engine, Redis vector search, Redis connections, Redis clustering, Redis security, Redis observability, Redis LangCache, and Redis Agent Memory. They include focused reference files so Cline can pull in deeper guidance when a task needs it without making every Redis interaction heavy.

The rule adds live-data guardrails for Redis work. It tells Cline to confirm environment, host, database, key pattern, cache or memory-store identity, tenant or user scope, and mutation risk before using live Redis commands or Redis Cloud SDK/REST operations. It also calls out destructive, broad, blocking, or administrative operations such as flushes, broad deletes, FT.DROPINDEX, ACL changes, slowlog resets, production smoke tests, and Agent Memory or LangCache writes.

Requirements

There are no install-time requirements beyond installing the plugin.

Actual Redis workflows may require the user to provide their own Redis CLI/client libraries, Redis Insight, Redis Cloud account access, or application credentials in the normal workspace/runtime environment. The plugin does not store or inject Redis passwords, Redis Cloud API keys, Agent Memory keys, LangCache keys, connection strings, customer prompts, session history, or memory records.

Safety and Design

This is a skills/rules-only plugin because the valuable Cline shape is guidance and guardrails, not a generic automatic Redis connection. Redis deployments vary widely, and auto-registering a server or running commands during setup would create surprising access and credential behavior.

The plugin prefers bounded scans, read-only inspection, staging environments, explicit key prefixes, synthetic test stores/caches, and user-confirmed production actions. Destructive or sensitive operations are kept as explicit user choices rather than plugin side effects.

[saoudrizwan]

Closing this plugin PR for now because this cleanup pass is limiting plugin marketplace PRs to plugins that only bundle MCP servers and/or skills. This PR includes additional plugin primitive(s): rules.

Those primitives may still be useful, but we are keeping this batch scoped to MCP and skill distribution.