DSPy Core

Environment Setup

uv

uv

# Create and activate a uv virtual environment
uv venv
source .venv/bin/activate

# Install dspy
uv pip install dspy

Rule: Never use raw

pip

or

python -m pip

. Always use

uv pip

for package installation and

uv run

for script execution.

Quick Start

Creating a new signature

import dspy

class MySignature(dspy.Signature):
    """Input and output fields with descriptions."""
    input_field = dspy.InputField(desc="Description of input")
    output_field = dspy.OutputField(desc="Description of output")

Compiling a program

# Use the compile-dspy script for safe compilation
uv run scripts/compile-dspy.py --module my_module --teleprompter teleprompter_name

When to Use This Skill

• Creating or modifying DSPy signatures
• Building new DSPy programs or modules
• Running DSPy compilation
• Testing DSPy signatures and programs
• Learning DSPy fundamentals

Core Concepts

Signatures

• Signature design patterns
• InputField vs OutputField usage
• Type hints and validation
• Hint and description best practices

Programs & Modules

• Building DSPy programs
• Module composition
• Compilation workflows
• Chain-of-thought and other patterns

Scripts

• compile-dspy.py: Compile DSPy modules with proper caching
• test-signature.py: Validate signature structure and types
• clear-cache.py: Clear DSPy cache safely

Templates

assets/templates/

• signature-template.py: Starting point for new signatures
• program-template.py: Starting point for new programs

Critical Rules

1. Always use

   uv

   : Use

   uv venv

   for environment creation,

   uv pip

   for installs, and

   uv run

   for script execution
2. Compilation is offline-only: Never compile at runtime in production
3. Clear cache after changes: Run

   clear-cache.py

   after modifying DSPy modules

Related Skills

• dspy-optimization: Optimization, metrics, evaluation, and teleprompters
• dspy-fleet-rlm: fleet-rlm-specific DSPy patterns, debugging, and integration

Progressive Disclosure

1. SKILL.md (this file): Quick reference and navigation
2. references/: Detailed technical docs loaded as needed
3. scripts/: Executable tools (can be run without reading)
4. assets/: Templates for new work