Skip to content
Patterson Academy

Assemble your own setup

You now have the full map. The capstone exercise: design the .claude/ setup for a real project of yours, applying the triggers from Lesson 16.

  1. Write a CLAUDE.md under 200 lines: commands, stack, rules.
  2. Add one path-scoped rule for your test files.
  3. Allow your test command in settings.json permissions; deny one dangerous pattern.
  4. Create one skill for a workflow you repeat (use the templates in the Prompt Library).
  5. Add a PostToolUse hook that formats on save.
  6. Wire one MCP server your team actually needs, secrets via ${VAR}.
  7. If a second repo needs the same setup — package it as a plugin.

Then verify what actually loaded with the four inspection commands: /context (window usage), /doctor (installation), /hooks (registered hooks), /mcp (server status and cost).

Check your understanding

Section titled “Check your understanding”

Question 1Which command shows whether your hooks actually registered?

Question 2The healthiest default posture for always-on context is…