Simple explanation
Welcome to Day 16. Yesterday you used a pre-built Skill. Today you build your own. This is the moment Claude Code stops feeling like a tool you use and starts feeling like a tool that knows you. Why build your own Skill? Pre-built Skills are designed for everyone. They are general. Your Skill is designed for your project, your style, your rules, and your specific way of working. The most powerful Skill you can build as a non-developer is your own prompt formula — saved as a single command so you never have to type it out again. The Skill every non-developer should build first Your personal new-lesson Skill. Right now — every time you want to add a new lesson to your site you type out a long prompt with all the formatting details, category rules, style requirements, and structure. With a Skill — you type /new-lesson and Claude Code already knows everything. You just fill in the content. How Skills are stored Personal Skills go in .claude/skills/ inside your project. They are just text files with instructions. You can open them, read them, and edit them any time. They are backed up automatically when you push to GitHub.
What to do
How to create your own Skill Open Claude Code and type this exact prompt: "Create a personal Skill called new-lesson that I can trigger with /new-lesson. When triggered it should ask me for: the lesson title, category, summary, and full content. Then it should format and add the lesson to my Latest Lessons page following all existing design patterns, matching the card style of every existing lesson exactly. Save this Skill to .claude/skills/new-lesson.md" Claude Code creates the Skill file. Test it immediately by typing /new-lesson and following the prompts. Three more Skills worth building for your specific site: /new-page — creates any new page matching your existing design with one command. You provide the page name and content. Claude Code handles all the structure. /seo-check — runs a quick SEO review of any page. Checks title tags, meta descriptions, heading structure, and image alt tags. Flags anything missing. /weekly-review — a weekly checklist that checks for broken links, missing content, slow pages, and any obvious design inconsistencies across the whole site. Today's practical task 1. Create the /new-lesson Skill using the prompt above. 2. Test it by adding one new short lesson using only the Skill — no manual prompt. 3. Compare the time it takes versus writing the full prompt manually. 4. Then create one more Skill of your choice from the three suggestions above. 5. Open .claude/skills/ in your file browser and confirm the Skill files are there. Today's result: You now have personal shortcuts built specifically for your project. Every future session is faster because of what you built today.
Copy-paste prompt
Create a personal Skill called session-start that I can trigger with /session-start. When triggered it should: ask me for today's one-task brief in one sentence, remind me to update CLAUDE.md with that goal, confirm I have created a GitHub branch for today's work, ask which mode I want to use (normal, plan, or auto), and then confirm it is ready to start. Save this Skill to .claude/skills/session-start.md
Course note
Key takeaway
Your own Skill knows your project, your style, and your rules. A general Skill is useful. A personal Skill is powerful. Build the /new-lesson Skill first — it is the one that saves the most time in every single future session.