Dependency Mocking FAQs

Question 1

When should I use this skill in my development process?

Accepted Answer

You should use this skill when a required dependency or specification isn't implemented yet, when you need to unblock local development, or when creating minimal viable implementations for prototyping. It is particularly useful for handling cross-specification interactions and creating isolated testing environments.

Question 2

How does this skill help manage technical debt?

Accepted Answer

It prevents 'silent' tech debt by enforcing a strict 'Temporary and Clearly Marked' principle. Every mock generated includes standardized documentation templates, TODO markers with replacement instructions, and integration with issue tracking (like bd issues) to ensure mocks are eventually replaced with real implementations.

Question 3

What implementation patterns does this skill support?

Accepted Answer

The skill provides optimized templates for various scenarios, including Minimal Type Mocks for basic data structures, Stub Function Mocks for returning dummy data, Pass-Through Mocks for interface satisfaction, and Simplified Algorithm Mocks for basic spec-compliant behavior.

Question 4

What is the Dependency Mocking skill for Claude Code?

Accepted Answer

The Dependency Mocking skill is a specialized capability for Claude Code designed to streamline the creation of temporary, well-documented mock implementations. It allows developers to create functional stubs for unimplemented dependencies, ensuring that development work can continue without waiting for full specification implementations.

Question 5

Does the Dependency Mocking skill provide a removal workflow?

Accepted Answer

Yes. It includes a specific 'Mock Replacement Workflow' that guides you through finding mock usages, updating imports, migrating logic to the real implementation, and closing associated tracking issues to ensure a clean codebase.

Dependency Mocking

Dependency Mocking

Key Features

Use Cases

Key Features

Use Cases