Claude Code, Practically

Pick your 30-minute tour

New to Claude CodeNever touched it, or just poked at it once. We'll get you from zero to comfortable.30 min · 6 stopsAlready using it dailyYou know the basics. Let's get more out of every session.30 min · 6 stopsEvaluating for my teamDeciding whether and how to roll this out. Here's what actually matters for that call.30 min · 6 stops

Watch it actually work

Not sure this is worth your 30 minutes? Here’s a real shape of what a session looks like — press play.

claude

▶ Play demo

The one idea that matters most

Everything else in this guide is detail. This is the thesis:

Vibe coding

• Go with the flow, no code-specific instructions
• No real code review of what gets generated
• Fast to start, expensive to maintain

Agentic engineering (this guide)

• You stay in control — you steer the AI
• You give specific instructions: libraries, patterns, conventions
• Code review is part of the loop, not an afterthought

Claude Code is a very capable assistant. It is not a replacement for engineering judgment. Every section in this guide assumes you’re the one steering.

Prefer to browse instead?

No quiz, no tour — just the whole map.

Getting Started

Install it, start your first session, understand the three config tiers, and get the keyboard shortcuts under your fingers.

Core Workflow

Context, memory, CLAUDE.md, and the prompt-engineering habits that separate a good session from a frustrating one.

Extending Claude

MCP, subagents, Agent Skills, custom commands, hooks, and plugins — how to teach Claude Code about your project specifically.

Automation & Feedback Loops

Tests, browser-driven verification, and the “Ralph loop” — running Claude Code toward a goal instead of babysitting every step.

Beyond the Terminal

The Desktop app, mobile dispatch, Remote Control, cloud sessions, and scheduling recurring tasks.

Team Playbook

The part the course didn’t cover: Claude Code for Flutter teams, handling client data safely, a shared CLAUDE.md template, and an onboarding checklist for new teammates.

Why this guide exists

I lead a Flutter team at LinkDev. This guide’s first seed came from a Claude Code course that my teammate Ismail Elmogy took and generously shared with the rest of us — the notes were good, but scattered across slide decks and written for a general audience rather than for a team shipping real client apps under real deadlines. This guide is what came out of turning that material into something we actually use day to day: fewer slides, more “here’s exactly what to type and why.”

It’s public and free. If you’re not on my team and you find it useful anyway — welcome, that’s the point. Consider it a small giving-back project from LinkDev to the wider dev community.

Who wrote this

Abdallah Gaber — Flutter team lead at LinkDev. Corrections and suggestions are welcome; this guide will keep evolving as Claude Code does.

Thanks to Ismail Elmogy for the course material that started it all.