Claude Power User – Hacks, Shortcuts, and Hidden Features By the end of this lesson, students should be able to: Knowing a technique and using it consistently are different things. You have learned more than twenty Claude features and techniques across this course. Some you will remember because they immediately changed how you work. Others will fade within a week without a record. A personal playbook solves this. It is not a comprehensive manual – it is your personal shortlist of the techniques that actually work for your work, in one place you will check. What goes in a playbook – five sections. Section 1 – Mode-to-Task Mapping: A short table of your most common recurring tasks and which Claude mode they belong in. Three to five entries to start. Update when you discover a task belongs in a different mode than you assumed. Section 2 – Saved Prompt Patterns: The patterns that have produced reliably good results for your most common task types. For each: the task type, the prompt pattern, and a note on why it works well. Eight to twelve curated entries is a healthy size. Section 3 – Cowork Skills Reference: A list of your active Skills – name, what it does, customizations you have made. Type Section 4 – Code Mode Context: Which projects have CLAUDE.md files, where those files are, and when last updated. Prevents the "does this project have a CLAUDE.md?" confusion across multiple projects. Section 5 – Custom Instructions: A copy of your current Custom Instructions with the date last updated. Serves as a backup and a record of how your standing brief to Claude has evolved. The capture habit. The best time to add something is the moment you discover it works. Keep your playbook open during Claude sessions. When a prompt produces exceptional output, copy it into Section 2 immediately. When a Skill works better than expected, add it to Section 3. Thirty seconds per entry. Eliminates the frustration of "what was that prompt that worked perfectly for this?" The weekly review – five minutes that compound. Once a week: Did any prompt stop working? Remove or update it. Did you discover a new technique? Add it. Is your mode-to-task table still accurate? Is any Custom Instruction outdated? Five minutes that separate a useful playbook from one that becomes stale and gets ignored. Sharing with colleagues. Your playbook is a team asset. Curate a one-page "team Claude guide" from your mode mappings, prompt patterns, and Skill descriptions. What took you weeks to discover can save a colleague days. A communications manager built her playbook over three weeks. By week three: a mode-to-task table with six entries, nine saved prompt patterns each tied to a specific task type, four Cowork Skills documented with customization notes, two CLAUDE.md file locations, and her Custom Instructions with a last-updated date. Three pages, completely current. She opens it at the start of each Claude session – mode check first, prompt patterns on hand. She shared a condensed version with two colleagues; one said it was the most useful Claude onboarding material she had encountered. Format your playbook as a markdown file. In Code mode, use Your playbook will naturally contain context about your work and workflows. Do not include client names, confidential project details, or sensitive organizational information in saved prompt patterns – the playbook is designed to be shareable, so write it with that audience in mind from the start. Create your personal Claude playbook file now. Set up the five section headers in a notes app or markdown file. Fill in at least one entry in each of the first three sections – one mode-to-task mapping, one saved prompt pattern from this course, and one Cowork Skill if configured. Set a calendar reminder for seven days from now to spend five minutes on the weekly review. You should be able to describe the five sections of a personal playbook, explain the capture habit and why timing matters, describe the weekly review process, and have created a starter playbook with section headers and initial entries. Log in and enroll to access lesson quizzes.
Lesson 5: Building Your Personal Power-User Playbook
Lesson Objectives
Lesson Content
/ in Cowork to see them, then document the ones you use regularly.Practical Example
Lesser-Known Tip
@playbook.md to pull your reference document into context and ask Claude to help refine prompt patterns or suggest improvements to your approach. Using Claude to improve your Claude workflow is one of the most effective recursive uses of the tool.Safety Notes
Practice Task
Completion Check