Skip to main content
skill CX Codex

dspy-custom-module-design — Claude Code skill: how to install

Guides the creation of custom DSPy modules extending dspy.Module with state caching, input validation, and program serialization.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OmidZamani/dspy-skills --skill dspy-custom-module-design -a claude-code
Open on GitHub

What dspy-custom-module-design does

This skill provides reference patterns for writing custom classes on top of dspy.Module. It covers standard forward() execution, sub-module declaration, and integration with predictors such as dspy.Predict and dspy.ChainOfThought.

It also details state management inside modules. You get implementation patterns for query caching with eviction limits and execution tracking. Input guards check for empty text, while exception handlers return structured dspy.Prediction objects containing error descriptions instead of failing mid-pipeline.

Full program persistence via dspy.load() requires DSPy 2.6.0 or later. For standard module state, save() and load() write to JSON files after instantiating the class.

What it helps with

  • Build custom modules by subclassing dspy.Module
  • Implement query caching with cache size limits
  • Handle empty inputs and catch exceptions using dspy.Prediction
  • Serialize and restore module parameters using JSON files

Example prompts for the agent

  • Create a custom dspy.Module classifier that validates labels and catches runtime exceptions
  • Build a stateful DSPy RAG module with query caching and a maximum cache size
  • Show how to serialize a DSPy pipeline and restore it from disk

How to install dspy-custom-module-design

1Skills CLI (Vercel)

npx skills add OmidZamani/dspy-skills --skill dspy-custom-module-design -a claude-code

2Manually: put the files in place

~/.claude/skills/dspy-custom-module-design/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/dspy-custom-module-design/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about dspy-custom-module-design

How do I install dspy-custom-module-design in Claude Code?

Run npx skills add OmidZamani/dspy-skills --skill dspy-custom-module-design -a claude-code in your terminal. This saves the skill file into ~/.claude/skills/dspy-custom-module-design/SKILL.md.

What does the dspy-custom-module-design skill provide?

It supplies architecture patterns and code examples for creating custom dspy.Module classes, handling cache state, catching errors, and serializing models.

Which DSPy versions are supported by this skill?

The skill metadata targets DSPy 3.2.1. Note that saving full programs with save_program=True and loading via dspy.load() requires at least DSPy 2.6.0.

Source text

SKILL.md · MIT
---
name: dspy-custom-module-design
version: "1.0.0"
dspy-compatibility: "3.2.1"
tags: ["production", "reasoning"]
requires-extras: []
description: Use for creating custom DSPy modules, extending dspy.Module, reusable components, stateful modules, serialization, and module testing.
allowed-tools:
  - Read
  - Write
  - Glob
  - Grep
---

# DSPy Custom Module Design

## Goal

Design production-quality custom DSPy modules with proper architecture, state management, serialization, and testing patterns.

## When to Use

- Building reusable DSPy components
- Complex logic beyond built-in modules
- Need custom state management
- Sharing modules across projects
- Production deployment requirements

## Related Skills

- Module composition: [dspy-advanced-module-composition](../dspy-advanced-module-composition/SKILL.md)
- Signature design: [dspy-signature-designer](../dspy-signature-designer/SKILL.md)
- Optimization: [dspy-miprov2-optimizer](../dspy-miprov2-optimizer/SKILL.md)

## Inputs

| Input | Type | Description |
|-------|------|-------------|
| `task_description` | `str` | What the module should do |
| `components` | `list` | Sub-modules or predictors |
| `state` | `dict` | Stateful attributes |

## Outputs

| Output | Type | Description |
|--------|------|-------------|
| `custom_module` | `dspy.Module` | Production-ready module |

## Workflow

### Phase 1: Basic Module Structure

All custom modules inherit from `dspy.Module`:

```python
import dspy

class BasicQA(dspy.Module):
    """Simple question answering module."""

    def __init__(self):
        super().__init__()
        self.predictor = dspy.Predict("question -> answer")

    def forward(self, question):
        """Entry point for module execution."""
        return self.predictor(question=question)

# Usage
dspy.configure(lm=dspy.LM("openai/gpt-4o-mini"))
qa = BasicQA()
result = qa(question="What is Python?")
print(result.answer)
```

### Phase 2: Stateful Modules

Modules can maintain state across calls:

```python
import dspy
import logging

logger = logging.getLogger(__name__)

class StatefulRAG(dspy.Module):
    """RAG with query caching."""

    def __init__(self, cache_size=100):
        super().__init__()
        self.retrieve = dspy.Retrieve(k=3)
        self.generate = dspy.ChainOfThought("context, question -> answer")
        self.cache = {}
        self.cache_size = cache_size

    def forward(self, question):
        # Check cache
        if question in self.cache:
            return self.cache[question]

        # Retrieve and generate
        passages = self.retrieve(question).passages
        result = self.generate(context=passages, question=question)

        # Update cache with size limit
        if len(self.cache) >= self.cache_size:
            self.cache.pop(next(iter(self.cache)))
        self.cache[question] = result

        return result
```

### Phase 3: Error Handling and Validation

Production modules need robust error handling:

```python
import dspy
from typing import Optional
import logging

logger = logging.getLogger(__name__)

class RobustClassifier(dspy.Module):
    """Classifier with validation."""

    def __init__(self, valid_labels: list[str]):
        super().__init__()
        self.valid_labels = set(valid_labels)
        self.classify = dspy.Predict("text -> label: str, confidence: float")

    def forward(self, text: str) -> dspy.Prediction:
        if not text or not text.strip():
            return dspy.Prediction(label="unknown", confidence=0.0, error="Empty input")

        try:
            result = self.classify(text=text)

            # Validate label
            if result.label not in self.valid_labels:
                result.label = "unknown"
                result.confidence = 0.0

            return result

        except Exception as e:
            logger.error(f"Classification failed: {e}")
            return dspy.Prediction(label="unknown", confidence=0.0, error=str(e))
```

### Phase 4: Serialization

Modules support save/load:

```python
import dspy

# Save module state
module = MyCustomModule()
module.save("my_module.json")

# Load requires creating instance first, then loading state
loaded = MyCustomModule()
loaded.load("my_module.json")

# For loading entire programs (dspy>=2.6.0)
module.save("./my_module/", save_program=True)
loaded = dspy.load("./my_module/")
```

## Production Example

```python
import dspy
from typing import List, Optional
import logging

logger = logging.getLogger(__name__)

class ProductionRAG(dspy.Module):
    """Production-ready RAG with all best practices."""

    def __init__(
        self,
        retriever_k: int = 5,
        cache_enabled: bool = True,
        cache_size: int = 1000
    ):
        super().__init__()

        # Configuration
        self.retriever_k = retriever_k
        self.cache_enabled = cache_enabled
        self.cache_size = cache_size

        # Components
        self.retrieve = dspy.Retrieve(k=retriever_k)
        self.generate = dspy.ChainOfThought("context, question -> answer")

        # State
        self.cache = {} if cache_enabled else None
        self.call_count = 0

    def forward(self, question: str) -> dspy.Prediction:
        """Execute RAG pipeline with caching."""
        self.call_count += 1

        # Validation
        if not question or not question.strip():
            return dspy.Prediction(
                answer="Please provide a valid question.",
                error="Invalid input"
            )

        # Cache check
        if self.cache_enabled and question in self.cache:
            logger.info(f"Cache hit (call #{self.call_count})")
            return self.cache[question]

        # Execute pipeline
        try:
            passages = self.retrieve(question).passages

            if not passages:
                logger.warning("No passages retrieved")
                return dspy.Prediction(
                    answer="No relevant information found.",
                    passages=[]
                )

            result = self.generate(context=passages, question=question)
            result.passages = passages

            # Update cache
            if self.cache_enabled:
                self._update_cache(question, result)

            return result

        except Exception as e:
            logger.error(f"RAG execution failed: {e}")
            return dspy.Prediction(
                answer="An error occurred while processing your question.",
                error=str(e)
            )

    def _update_cache(self, key: str, value: dspy.Prediction):
        """Manage cache with size limit."""
        if len(self.cache) >= self.cache_size:
            self.cache.pop(next(iter(self.cache)))
        self.cache[key] = value

    def clear_cache(self):
        """Clear cache."""
        if self.cache_enabled:
            self.cache.clear()
```

## Best Practices

1. **Single responsibility** - Each module does one thing well
2. **Validate inputs** - Check for None, empty strings, invalid types
3. **Handle errors** - Return Predictions with error fields, never raise
4. **Log important events** - Cache hits, errors, validation failures
5. **Test independently** - Unit test modules before composition

## Limitations

- State increases memory usage (careful with large caches)
- Serialization doesn't automatically save custom state
- Module testing requires mocking LM calls
- Deep module hierarchies can be hard to debug
- Performance overhead from validation in hot paths

## Official Documentation

- **DSPy Documentation**: https://dspy.ai/
- **DSPy GitHub**: https://github.com/stanfordnlp/dspy
- **Custom Modules Guide**: https://dspy.ai/tutorials/custom_module/
- **Module API**: https://dspy.ai/api/modules/

© OmidZamani · MIT · OmidZamani/dspy-skills

Similar skills

All skills for AI and ML →

From the same set23

dspy-finetune-bootstrap Turns a working DSPy program into fine-tuned weights for a smaller model, cutting inference cost and speeding up responses. CX Codex +1 ★ 124repo stars dspy-evaluation-suite Tests and benchmarks DSPy modules against evaluation datasets using multi-threaded execution and custom scoring functions. CX Codex +1 ★ 124repo stars dspy-embedding-retrieval Build semantic retrieval over an application-owned text corpus with DSPy embeddings, local or hosted models, and optional FAISS indexing. CX Codex +1 ★ 124repo stars dspy-debugging-observability A skill for debugging and monitoring DSPy programs: call history, MLflow tracing, and custom callbacks that track cost and errors. CX Codex +1 ★ 124repo stars dspy-bootstrap-fewshot This skill guides BootstrapFewShot setup so a teacher model can generate demonstrations for a DSPy program. Use it when you have labeled examples and want to automate demo selection. CX Codex +1 ★ 124repo stars dspy-better-together A skill that walks you through chaining DSPy prompt and weight optimizers, scoring intermediate programs and keeping the best one. CX Codex +1 ★ 124repo stars dspy-advanced-module-composition Composes complex DSPy programs using module ensembling, MultiChainComparison, sequential pipelines, and fallbacks. Useful for multi-step reasoning architectures. CX Codex +1 ★ 124repo stars dspy-adapters-multimodal This skill guides DSPy adapter choices for structured responses, function calls, and image, audio, or document inputs. Use it when building DSPy-based AI applications. CX Codex +1 ★ 124repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor