Responsibility Driven Design

Apply Responsibility-Driven Design (RDD) by Rebecca Wirfs-Brock and Brian Wilkerson when designing classes, distributing behavior across objects, modeling a domain, or refactoring object-oriented code. Covers responsibilities, role stereotypes, CRC cards, collaborations, contracts, object neighborhoods, and the Tell-Don't-Ask principle.

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill responsibility-driven-design
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/responsibility-driven-design ~/.claude/skills/responsibility-driven-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Responsibility-Driven Design (Wirfs-Brock & Wilkerson)

Apply this approach whenever designing or refactoring object-oriented code, modeling a domain, deciding where behavior belongs, or reviewing class designs. RDD asks the central question: **"Who is responsible for what, and who collaborates with whom?"**

## Core Philosophy

**Objects are members of a community of cooperators.** Each object has a role and a set of responsibilities. The system's behavior emerges from objects sending messages to one another to fulfill their obligations.

**Design by responsibilities, not by data.** The classical (data-driven) question is "what data does this class hold?" The RDD question is "what is this object responsible for?" Data follows responsibility; behavior is primary.

**Anthropomorphize.** Talk about objects as if they were people with jobs. "The OrderProcessor accepts an order, asks the InventoryService to reserve stock, and tells the PaymentGateway to charge the customer." If your design doesn't read this way, the responsibilities are misplaced.

**The goal is a well-functioning community.** Each object has a clear job, knows its neighbors, and trusts them to do their jobs. No object hoards work; no object snoops on another's internals.

---

## What Is a Responsibility?

A responsibility is an obligation an object has to other objects. Three kinds:

1. **Knowing responsibilities** — what an object knows.
   - Knows its own data (`Order` knows its line items).
Read the full skill on GitHub

Details

Skill name
responsibility-driven-design
Path
plugins/engineering-practices/skills/responsibility-driven-design/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Responsibility Driven Design skill do?

Apply Responsibility-Driven Design (RDD) by Rebecca Wirfs-Brock and Brian Wilkerson when designing classes, distributing behavior across objects, modeling a domain, or refactoring object-oriented code. Covers responsibilities, role stereotypes, CRC cards, collaborations, contracts, object neighborhoods, and the Tell-Don't-Ask principle.

How do I install the Responsibility Driven Design skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Responsibility Driven Design popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Semantic Search

8

Freddy-CHEN-ux/00_claude_skills

INVOKE BEFORE writing new code to find existing implementations (DRY). Also for codebase exploration and production data search. Run: docker exec arsenal-semantic-search-cli code-search find 'query

Software Development

Repository Context Checker

8

Freddy-CHEN-ux/00_claude_skills

Verify developers are working in the right repository type (brain vs code)

Software Development

Service Atlas

5

vnovakovits/claude-skills

Survey a service's codebase and publish a Miro "atlas" of it — a Pete Hodgson tech debt wall (value × cost cards), SIG-style health scorecard, hotspot treemap (churn × size), change coupling, pay-down roadmap, code quality metrics (cyclomatic complexity risk profile, unit size, parameters, duplication), system context map and coupling matrix (Khononov strength, efferent/afferent), domain logic leaking into the application layer, a Big Picture EventStorming, and one process-level EventStorming frame per pivotal phase. Grounds every claim in the code with parallel read-only agents, measures with

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.