This is the third project of the course. You'll take everything from Units 5, 6, and 7 and wire Claude into the project itself: connect a server it can use, teach it a skill, give it a command, and...
概览
This is the third project of the course. You'll take everything from Units 5, 6, and 7 and wire Claude into the project itself: connect a server it can use, teach it a skill, give it a command, and set a hook that holds a standard — the way you'd set a project up so everyone's Claude works the same. This builds on the same repository from the first two projects. Each level's project adds to it, all the way to a shareable plugin at the end — and the wiring you commit here is what that plugin will eventually bundle. You'll work on the course repo — the small Express API you set up in the first project and shipped a change to in the second. The platform connects the repo for you; you'll do your work on a branch and submit that branch for review. This time you're not changing what the app does — you're setting up how Claude works on it. Everything you add lives in the repo and gets committed, so it travels to every teammate who clones it.
README
以下为原文 README 节选，完整内容请查看原文。
Wire Claude into your stack
This is the third project of the course. You’ll take everything from Units 5, 6, and 7 and wire Claude into the project itself: connect a server it can use, teach it a skill, give it a command, and set a hook that holds a standard — the way you’d set a project up so everyone’s Claude works the same.
This builds on the same repository from the first two projects. Each level’s project adds to it, all the way to a shareable plugin at the end — and the wiring you commit here is what that plugin will eventually bundle.
The repository
You’ll work on the course repo — the small Express API you set up in the first project and shipped a change to in the second. The platform connects the repo for you; you’ll do your work on a branch and submit that branch for review. This time you’re not changing what the app does — you’re setting up how Claude works on it. Everything you add lives in the repo and gets committed, so it travels to every teammate who clones it.
What you’ll wire in
Four integrations, one for each tool you met in this level:
- A server (MCP) — something useful Claude can reach on this project, connected so the whole team gets it.
- A skill — a way of working this project repeats, written down once so Claude applies it on its own.
- A command — a prompt you run often, saved behind a
/name. - A hook — a standard that has to hold every time, enforced automatically. The point isn’t four clever tricks. It’s a repo where Claude is set up the way the project needs, ready to hand to the next person.
What you’ll deliver
On your branch of the repo:
- a committed
.mcp.jsonwith a server at project scope, plus a permission rule in.claude/settings.json(permissions.allow) scoping what it may do - a project skill in
.claude/skills//SKILL.mdthat fires on the right request - a custom command in
.claude/commands/.md - a hook in
.claude/settings.json - one task run headless with a scoped
--allowedTools - a short
NOTES.mdexplaining your choices
Before you start
- Finish Units 5, 6, and 7.
- Have Claude Code installed and signed in (
claude --version), andgh auth logindone so Claude can open the pull request. - Get the repo onto your machine (clone it, or open it from the platform) and open a terminal in the project folder.
Tasks
1. Connect a server the project can use
推荐工具
换一个关键词，或者移除筛选条件。
安装
npx skillfish add mate-academy/claude-wire-into-your-stack