/context-load-redpanda

allowed-tools: mcp__context7__resolve-library-id, mcp__context7__get-library-docs, WebFetch, Read, Write, Bash(gdate:*)
name: "Context Load Redpanda"
description: "Load comprehensive Redpanda streaming platform documentation context"
author: "wcygan"
tags: ["context","db"]
version: "1.0.0"
created_at: "2025-07-14T00:00:00Z"
updated_at: "2025-07-14T00:00:00Z"

Context

• Session ID: !`gdate +%s%N`
• Current directory: !`pwd`
• Technology stack: !`fd "(deno\.json|package\.json|Cargo\.toml|go\.mod)" --max-depth 2 | head -5 || echo "No framework files detected"`
• Streaming configs: !`echo "No streaming configurations found"`
• Docker configs: !`fd "docker-compose.*\.ya?ml" --max-depth 2 | head -3 || echo "No Docker Compose files found"`
• Kafka references: !`rg "kafka" --type js --type ts --type go --type rust --max-count 5 | head -3 || echo "No Kafka references found"`

Your Task

PROCEDURE load_redpanda_context():

STEP 1: Session Initialization and Context Resolution

• Initialize session state file: /tmp/redpanda-context-$SESSION_ID.json
• Detect project streaming requirements and current technology stack
• Identify existing Kafka/streaming implementations for migration context

TRY:

• Use Context7 MCP server to resolve Redpanda library documentation
• Create comprehensive context loading strategy
• Set up progress tracking for multi-source documentation loading

CATCH (context7_unavailable):

• Fall back to WebFetch for direct documentation access
• Document limited context availability in session state
• Continue with web-based documentation loading

STEP 2: Comprehensive Documentation Loading

Think deeply about the optimal documentation loading strategy for Redpanda streaming platform expertise.

Load documentation from multiple authoritative sources in parallel:

**Primary Documentation Sources:**

• **Core Architecture & Getting Started**:
• URL: `https://docs.redpanda.com/current/get-started/`
• Focus: Installation, configuration, basic usage patterns
• Priority: Essential for foundation knowledge

• **Kafka API Compatibility**:
• URL: `https://docs.redpanda.com/current/reference/kafka-compatibility/`
• Focus: API compatibility matrix, migration strategies, client libraries
• Priority: Critical for migration planning

• **Performance & Administration**:
• URL: `https://docs.redpanda.com/current/manage/cluster-maintenance/`
• Focus: Performance tuning, monitoring, troubleshooting, optimization
• Priority: High for production deployment

• **Schema Registry Management**:
• URL: `https://docs.redpanda.com/current/manage/schema-registry/`
• Focus: Schema management, compatibility, evolution strategies
• Priority: High for data governance

**Advanced Topics Sources:**

• **Producer/Consumer Patterns**:
• URL: `https://docs.redpanda.com/current/develop/`
• Focus: Client development, streaming patterns, best practices
• Priority: Medium for development guidance

• **Security & Access Control**:
• URL: `https://docs.redpanda.com/current/manage/security/`
• Focus: Authentication, authorization, encryption, compliance
• Priority: Medium for production security

STEP 3: Context Integration and Knowledge Synthesis

TRY:

• Load and process documentation from all identified sources
• Synthesize streaming platform knowledge across:
• High-throughput message processing architectures
• Low-latency streaming application patterns
• Schema evolution and compatibility strategies
• Consumer group management and rebalancing
• Transaction support and exactly-once semantics
• Production monitoring and observability
• Performance optimization techniques
• Migration strategies from Apache Kafka

• Create comprehensive knowledge base covering:
• **Streaming Architecture**: Topic design, partition strategies, replication
• **Client Development**: Producer/consumer patterns, error handling, retry logic
• **Schema Management**: Registry usage, compatibility modes, evolution
• **Performance Optimization**: Throughput tuning, latency reduction, resource management
• **Operational Excellence**: Monitoring, alerting, capacity planning, troubleshooting
• **Migration Planning**: Kafka compatibility, client migration, data migration

• Update session state with loaded context sources and knowledge areas
• Save comprehensive context summary to: /tmp/redpanda-knowledge-$SESSION_ID.json

CATCH (documentation_load_failed):

• Document failed documentation sources
• Continue with available context from successful loads
• Provide alternative documentation recommendations
• Save partial context loading results

CATCH (network_connectivity_issues):

• Save session state for resumption
• Provide offline documentation alternatives
• Create recovery plan for context loading completion
• Document connectivity requirements

STEP 4: Context Validation and Expertise Confirmation

• Validate loaded context for completeness across key knowledge areas:
• ✓ Streaming architecture fundamentals
• ✓ Kafka API compatibility and migration
• ✓ Performance optimization strategies
• ✓ Schema registry management
• ✓ Production deployment best practices
• ✓ Monitoring and troubleshooting

• Confirm readiness to provide expert guidance on:
• Building high-performance streaming applications
• Optimizing message throughput and latency
• Managing schema evolution and compatibility
• Implementing robust consumer patterns
• Performance tuning for production workloads
• Monitoring streaming pipeline health
• Migrating from Apache Kafka to Redpanda
• Troubleshooting streaming application issues

STEP 5: Session Completion and Knowledge Activation

TRY:

• Generate context loading summary report
• Activate Redpanda streaming platform expertise
• Provide immediate readiness confirmation
• Clean up temporary session files

FINALLY:

• Update session state: phase = "context_loaded"
• Archive context loading artifacts
• Clean up temporary files: /tmp/r