**Claude How To**

[](https://github.com/luongnv89/claude-howto/stargazers) [](https://github.com/luongnv89/claude-howto/network/members) [](LICENSE) [](CHANGELOG.md) [](https://code.claude.com)

🌐 **Language / Ngôn ngữ / 语言 / Мова:** [English](README.md) | [Tiếng Việt](vi/README.md) | [中文](zh/README.md) | [Українська](uk/README.md)

Master Claude Code in a Weekend

Go from typing `claude` to orchestrating agents, hooks, skills, and MCP servers — with visual tutorials, copy-paste templates, and a guided learning path.

**[Get Started in 15 Minutes](#get-started-in-15-minutes)** | **[Find Your Level](#not-sure-where-to-start)** | **[Browse the Feature Catalog](CATALOG.md)**

---

Table of Contents

• The Problem
• How Claude How To Fixes This
• How It Works
• Not Sure Where to Start?
• Get Started in 15 Minutes
• What Can You Build With This?
• FAQ
• Contributing
• License

---

The Problem

You installed Claude Code. You ran a few prompts. Now what?

• The official docs describe features — but don't show you how to combine them. You know slash commands exist, but not how to chain them with hooks, memory, and subagents into a workflow that actually saves hours.
• There's no clear learning path. Should you learn MCP before hooks? Skills before subagents? You end up skimming everything and mastering nothing.
• Examples are too basic. A "hello world" slash command doesn't help you build a production code review pipeline that uses memory, delegates to specialized agents, and runs security scans automatically.

You're leaving 90% of Claude Code's power on the table — and you don't know what you don't know.

---

How Claude How To Fixes This

...