Build Your Design Leadership OS with Claude Cowork and Skills

Create a personal Operating System with Claude Cowork and Skills.

The advent of AI is creating a gap between designers who can structure and scale their thinking and those who can't. The ones who treat AI as thinking infrastructure, and not just a production tool, are operating at a different level. Their judgment is accessible. Their expertise doesn't disappear when they leave the room.

One day. One skill. v1 of your personal OS.

You'll choose one area of your expertise to codify. Maybe it's a critique framework, a stakeholder playbook, or a design logic library. Whatever matters most to you. Then you'll build it, step by step.

1

Set up your environment

Install Claude Desktop and configure Cowork mode. No Terminal. No code. If you can install an app on your computer, you can do this.

2

Learn how Skills work

Before building from scratch, you'll edit an existing Skill so you understand the mechanics. What a Skill is made of, how it routes logic, where your judgment fits in.

3

Codify your tacit knowledge

This is the hard part, and the most valuable. Take something you "just know" and turn it into explicit instructions an AI agent can follow. This is where 90% of people get stuck on their own.

4

Build your reference library

Structure your source material (frameworks, past work, rationale docs) into a queryable reference library that gives your Skill depth and context.

5

Build your Skill from scratch

Wire it all together. Your knowledge, your logic, your structure, now living as a working Claude Skill you can trigger from a single command.

6

Add slash commands

Create custom slash commands that trigger specific behaviors like /critique, /reframe, or /stakeholder-brief. One shortcut, one behavior.

7

Test, train, and refine

Stress-test against real scenarios. Refine the logic. Adjust the tone. You'll leave with a system you'll actually use Monday morning, not a prototype you'll never open again.

You'll build one Skill in the workshop. Here are ten you could make.

• A design logic reference library
• A repository of communication and planning templates
• A personal development tracker
• A lightweight brand and voice guide
• A critique prep tool
• A leadership learning tool for your team
• A strategy and positioning reference
• A feedback and development guide
• An executive communication encoder
• A decision-making pattern library

The hard part is the articulation, not the technology. Every one of these requires you to put your judgment into words. The tools are useful, but the real value is what happens to your own thinking when you build them.

This is what a finished Skill looks like.

Read the Room is a communication coaching Skill built from CDO School methodology. It reads emotional states, picks the right framework, and walks you through preparing for hard conversations. Here's what's inside.

---
name: communication-methods
---

# Communication Methods

This skill provides reference material for
choosing between validation (Imago Dialogue)
and analytical (SCR) approaches.

## Core Decision

Before communicating, read the room.
The person's state determines your approach.

- C-States (Calm, Curious, Clear...)
  → Analytical approach (SCR)
- T-States (Testy, Tense, Triggered...)
  → Validation approach (Imago) first

read-the-room/
├── commands/
│   ├── start.md
│   ├── readroom.md
│   ├── validate.md
│   └── analyze.md
├── skills/communication-methods/
│   ├── SKILL.md
│   └── references/
│       ├── frameworks.md
│       └── voice.md
└── read-the-room.plugin

This workshop is built for experienced design leaders.

You don't need to know how to code. You do need to have expertise worth codifying.

Common questions