Kitchen SinkLearn Claude customizationSource
CourseFull course

LESSON 01 OF 08

Know the building blocks

Separate instructions, connections, packages, and executable behavior before choosing what to build.

In this lesson
  • Tell a workflow command from a mod hook.
  • Choose the smallest extension that fits an outcome.
Lessons in your path0 of 8 complete
Progress settings

Saved only in this browser.

Claude customization has a few overlapping names. Start by connecting each piece to the job it does.

A

Skill or command

Reusable instructions for a recurring job. Our Cowork command asks for an experiment card with four fields.

“Do this the way I like.”
B

Connector / MCP

Tools or data supplied by an external service or process. The starter doesn’t need a connected account.

“Reach this system.”
C

Plugin

The package people install. This repo ships two independent plugins through one small marketplace.

“Bundle these pieces.”
D

Mod

Code inside a Claude Code plugin that reacts to events. Our mod adds a pane and changes selected behavior.

“React when this happens.”
Two meanings of “hook.” A settings hook runs a configured command, request, or prompt. A mod hook is a JavaScript or TypeScript function inside Claude Code. The examples here use mod functions. Compare the extension types ↗

YOUR TURN

Try it, then explain it.

  1. Pick one repeated task you want to improve.
  2. Describe whether it needs instructions, external tools, or custom interface behavior.
  3. Write a one-sentence outcome before choosing a technology.
QUICK CHECK · OPTIONAL

You keep pasting the same formatting instructions. What is the smallest useful starting point?

Choose one answer

Finish at your own pace.

The next button saves completion and opens the next lesson.