Cindy Zhu.
Free guides
Getting started Claude

The best AI tool for each job (one brain + specialists)

Hey, it's Cindy 🌱 This guide gives you the current best pick for each job as of July 2026, and what it is actually good at.
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)
start here

Writing: Claude with a loaded Project

What it is: Claude Projects give Claude a persistent memory for one job. You upload 3 to 5 of your own writing samples plus past work into Project Knowledge, and Claude references them automatically in every chat inside that project, so drafts come out in your voice instead of generic AI tone.

When to use it: Any repeat writing where sounding like YOU matters, captions, emails, newsletters, scripts, landing pages.

Heads-up: Thin setup gives thin results. Add real samples and a short instructions block (aim for a couple of hundred words describing your voice), not one paragraph. Custom Styles are migrating into Skills through 2026, but both still work.

Try this prompt inside the project:

✍️ Make it sound like you
You have my writing samples in this project's knowledge. First, in 5 bullet points, describe my voice: sentence length, tone, what I do and don't do (emojis, slang, structure). Then write [the thing] in that exact voice. Flag any line that sounds more like generic AI than like me.

πŸ”— Source: Claude Projects


when being wrong is expensive

Research: Claude's Research mode

What it is: Research is Claude's agentic web mode. Instead of one search, it runs multiple searches that build on each other, decides what to dig into next, and returns a thorough answer with inline citations you can click and check.

When to use it: Anything where being wrong is expensive, competitor teardowns, pricing comparisons, "what actually changed in X this month," market or claim checking.

Heads-up: Research sits on the paid plans (Max, Team, Enterprise, and Pro), not the free tier, so if the toggle is missing that is why. Always open a couple of the cited links yourself, agentic search is strong but citations are there so you verify, not so you trust blindly.
πŸ“š A research brief that cites itself
Research [topic] for me. I want the current state as of this month, at least 6 sources, and a short section on what most people get wrong about it. Give me inline citations I can click, and flag anything where the sources disagree.

πŸ”— Source: Claude Research


for visuals

Image generation: Nano Banana Pro or Midjourney

What it is: Two current ceilings. Google's Nano Banana (the Gemini image model, with Nano Banana Pro and Nano Banana 2 as the 2026 versions) is the strongest for readable text inside images, real-world knowledge, and clean edits. Midjourney V8.1 (default since June 2026) is the strongest for style, mood, and cinematic look.

When to use it: Nano Banana for anything with words in it (thumbnails, ads, infographics, product shots). Midjourney when you want a specific aesthetic or vibe.

Heads-up: Do not settle for the default generator baked into whatever app you happen to be in, those are usually a generation behind. Every Nano Banana image carries an invisible SynthID watermark, worth knowing for client work.

πŸ”— Sources: Nano Banana Pro Β· Midjourney


Video generation: Veo 3.1 or Kling 3.0 πŸ“Ή

What it is: The two safest top picks right now. Google Veo 3.1 is the technical leader, true 4K with synchronized audio (dialogue, ambient sound, effects) generated in one pass. Kling 3.0 matches it on cinematic motion (hair, liquid, fabric) and adds a multi-shot storyboard mode, and tends to be the better value.

When to use it: Veo when you need the highest quality and native audio. Kling when you want strong motion and multiple shots without paying enterprise pricing.

Heads-up: Skip Sora for now. OpenAI is shutting Sora down in stages, the consumer app already closed and the API sunsets in September 2026, so do not build a workflow on it.

πŸ”— Source: AI video model comparison 2026


actually build it

Building apps and websites: Claude Code

What it is: This is where Claude runs away with it. Claude Code is Anthropic's agent that lives in your terminal, you describe what you want in plain English and it writes the real files, runs commands, and builds a working app or site, not a mock-up.

When to use it: Landing pages, internal tools, scrapers, small apps, automations, anything you would normally pay a developer or a no-code tool for.

Heads-up: It is genuinely capable but it is not magic, review what it builds and keep your asks scoped. Start with one page or one feature, not "build me a whole SaaS."

πŸ”— Source: Claude Code


stop typing notes

Meetings: Granola or Fathom, then Claude

What it is: Stop typing notes. Granola listens and writes a clean summary (it enhances your own notes rather than dumping a raw transcript). Fathom records and summarises calls. Then you paste the summary or transcript into Claude and ask it to pull out the decisions and action items.

When to use it: Any call where you would otherwise scramble to remember what was agreed, sales calls, client calls, team syncs.

Heads-up: Both have real free tiers. Granola's free Basic tier includes AI notes but caps how much history stays accessible. Fathom's free tier gives unlimited recordings but only about 5 AI summaries a month, so save those for the calls that matter.
πŸ“ Turn a transcript into decisions
Here is a meeting transcript. Give me: 1) the decisions made, 2) every action item with who owns it and any due date mentioned, 3) open questions nobody answered, 4) a 3-line summary I can paste into Slack.

πŸ”— Sources: Granola Β· Fathom


set it and forget it

Automating tasks: Claude writes the spec, n8n runs it ♾️

What it is: The combo that replaces most paid automation tools. Claude writes the automation spec (the trigger, the steps, the logic, the edge cases) as clear instructions, and n8n is the open-source tool that actually runs that workflow on a schedule.

When to use it: Anything repetitive and rule-based, saved posts to a content database, form replies, lead routing, daily reports, cross-posting.

Heads-up: n8n's self-hosted Community Edition is free with no execution limits (you just need a cheap server, roughly $5 to $7 a month). n8n Cloud removed its old free tier and now starts around $20 to $24 a month, so if budget is tight, self-host. One execution counts as one workflow run no matter how many steps, which is why it beats Zapier on cost for complex flows.
♾️ Spec it before you build it
I want to automate [task]. Write me an n8n automation spec: the trigger, each node/step in order, what data moves between them, and 3 edge cases I should handle. Keep it plain enough that I can build it in n8n's visual editor.

πŸ”— Source: n8n pricing


go further

3 bonus prompts to run next

1. Audit your own stack πŸ”Ž

πŸ”Ž Find what you can cancel
Here are the AI tools I currently pay for: [list them]. For each one, tell me if there's a better or cheaper current tool for that specific job as of this month, and which subscriptions I could cancel without losing capability.

2. Find your highest-leverage upgrade ⚑

⚑ Pick the one thing to fix first
Here's how I spend my work week: [rough breakdown]. Which single task is eating the most time AND has the best AI tool to fix it? Give me the one upgrade to make first and exactly how to set it up.

3. Build a handoff workflow πŸ”—

πŸ”— Wire the brain to the specialist
Design a workflow where Claude is the brain and one specialist tool does the output, for [my use case, e.g. turning meetings into content]. List each step, which tool does it, and the exact prompt I'd give Claude at each handoff.

use it well

How to get the most out of it

If you're just starting: Do not try to adopt all seven at once. Pick the single job that eats the most of your week, set up only that tool this week, and let it become a habit before you add the next one.
If you're already deep in AI: Treat Claude as the orchestrator and everything else as a callable specialist. The real leverage is the handoff, Claude writes the spec, brief, or transcript-to-actions, and the specialist tool executes. Standardise those handoffs (saved prompts, a Project per job) and your whole stack starts to feel like one system instead of ten tabs.

One honest note

The "best" tool moves fast, this stack is accurate as of July 2026 and some of it will shift within months (video models especially are turning over quickly). The part that does not change is the pattern: one brain plus specialists beats one tool trying to do everything. Re-check the specialists a couple of times a year, keep the structure.

the waitlist is now open

AI System Club is launching soon

Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.

btw this list gets first dibs
the moment doors open :)