Writing Your First Custom Skill
Day 15 · Week 3 · Skills — Recipe Book
Slack Message — copy & paste
🤖 Tip #15 — Stop repeating yourself. Write a skill once in 2 minutes, use it forever — no JavaScript, no API, no build step.
#15 Claude Code
Four Steps to a Skill
- **Step 1 — Create the file** — Just a markdown file at `.claude/commands/check-component.md`. That's the only location requirement.
- **Step 2 — Add frontmatter** — name, description, argument-hint, and allowed-tools in a YAML block. This controls how the skill behaves and what it can access.
- **Step 3 — Write instructions** — Numbered steps telling the AI what to do. 'Find the component, verify it extends CustomComponent, check lifecycle methods, report findings with file:line references.'
- **Step 4 — Use it** — Type `/check-component hero` and the AI follows your instructions exactly. No JavaScript, no API, no build step.
Custom Commands DIY
#15 Skills — Recipe Book
Build One Right Now
- 1 **Find your first candidate** — Think of an instruction you've given AI more than twice. A build checker, a convention reminder, a component scaffolder. That's your first skill.
- 2 Create the skill file now
- › Create `.claude/commands/your-skill.md`
- › Add frontmatter: name, description, argument-hint, allowed-tools
- › Write 3-5 numbered instruction steps
- › Test with `/your-skill <argument>`
- 3 **Commit to git** — Once the skill file is in version control, your entire team has the skill automatically. Shared knowledge encoded as a file.
- 4 **Start small, iterate** — Your first skill doesn't need to be perfect. Get it working, then refine the instructions as you use it.
Custom Commands DIY
Your screenshot here Optional — add a screenshot from your own workflow