Hey, it's Cindy 🌱 This is the whole starter pack from the carousel, with every clickable link in one place. I curated it down to the resources I actually rate, grouped into 5 simple buckets so you always know where to start. Save this. It is basically the only Claude bookmark list you need.
A quick honesty note before you dive in. I marked the official Anthropic ones (made by the people who built Claude) so you can tell them apart from community-made resources. Community tools are other people's code. They can be brilliant, but only install ones you can actually read and trust. That line matters more than any single link below.
start here
🧭 1. Start here (total beginners)
New to Claude? Do not try to learn everything at once. Pick ONE of these tonight and just start.
- 🎯 Claude Quickstart (official). The 5-minute "press these buttons" guide straight from Anthropic. Open this first. It walks you from install to your first real task without assuming you know anything.
- 🪜 Anthropic Academy (official). Free official courses with completion certificates, including Claude 101 and Claude Code 101. This is your structured ladder from absolute basics to advanced, so you always know what to learn next. Trustworthy, free, no fluff.
- ⭐ Best practices for Claude Code (official). Once the basics click, this is the single best page Anthropic has written on getting good results. Skim it now, come back to it as you grow. It is underread and very good.
the habits
🛠️ 2. Best practices (how top builders actually use Claude)
The gap between average output and great output is mostly habits, not tools. These are the ones that move the needle.
- 📘 Official best-practices docs (official). Anthropic's own guide to getting more out of Claude Code: how to prompt, how to set up your project, how to manage context. This is the source the pros quietly copy.
- 🧠 Plan first, then build (the one habit that changes everything). Ask Claude to explore and write a plan BEFORE it writes any code, and let sub-agents handle the big jobs in their own context. It is the "explore, then plan, then code" workflow inside the best-practices docs above. Do this and your output jumps.
- 👤 The creator's own setup (community). The people who build Claude Code often share how they personally configure it (their CLAUDE.md files, their favourite commands, their workflows). To find the current ones, search "how I use Claude Code" or "my Claude Code setup" from Anthropic engineers on YouTube and X, then steal the cheatsheet. These are personal blogs and videos, not one fixed link, so grab the most recent one you trust.
bookmark these
🧰 3. Tools and resources (bookmark these)
The shelf of things worth keeping a tab open for.
- 📚 Prompt library (official). A free shelf of proven, copy-paste prompts tagged by task and role. Great when you are stuck or starting from a blank page. Grab one, swap in your details, run it.
- ✨ Prompt improver (official). Paste a rough prompt and Claude rewrites it into a stronger one using real prompt-engineering techniques. It lives inside the Anthropic Console: open the prompt editor and look for the improve prompt option. Free and badly underused.
- 💻 Free slash commands on GitHub (community). A collection of one-word commands that add real power to Claude Code (review, test, refactor, and more). Browse the list and grab only the ones you need. Because it is community-made, read what a command does before you install it.
⚠️ Safety note: anything in the community bucket is other people's code running on your machine. Only install commands and skills you can read and understand. If you cannot tell what it does, do not run it.
the sleepers
💎 4. Underrated tips (most people miss these)
The sleeper features. Almost nobody has these set up, and that is exactly why they are worth your time.
- 🤝 Claude Cowork (official). A genuinely underrated way to hand Claude a whole task (organise files, build a report, pull weekly metrics) and get back a finished deliverable, not just a chat reply. Available on paid plans. Try it before you knock it.
- 🌐 Claude in Chrome (official). Lets Claude work inside your own browser: fill forms, pull data, test pages, draft inside Google Docs and Notion. You add the Claude in Chrome extension from the Chrome Web Store. Almost nobody has this set up yet, and it is very good. Sleeper hit.
- 🎚️ Use Style (in-app, free). One click in the chat box changes how Claude writes (concise, formal, explanatory, or your own custom style). Most people never touch it. Look for the style option near the message box in the Claude app. It is the fastest way to stop fighting Claude's default tone.
- 💰 Pick the cheapest model that works. Use Haiku for simple tasks and save Sonnet and Opus for the genuinely hard ones. Same result on easy jobs, lower bill. You switch models with the model picker in the Claude app, no setup needed.
what to avoid
⚠️ 5. Common mistakes (and the fix)
Fix these three and your output jumps overnight, no new tools needed.
🚫 Vague prompts. "Write me a post" gets you average. Give Claude a role, the context, and the rules instead. Specific in, specific out.
🚫 Dumping everything at once. Claude works better when you feed context step by step, or store the standing stuff in a Claude Project so it is always there. A wall of text up front buries the actual task.
🚫 No guardrails. Claude will happily ramble or over-build. Tell it what NOT to do, not just what to do. The "do not" list is half the prompt.