A practical guide to Claude productivity workflows drawn from real production use. It covers session memory, inbox triage, task tracking, prompt patterns, and the daily habits that make Claude genuinely useful over time.

Who is this book for?

Intermediate Claude users who have used Claude enough to know the basics and are looking for a system, not a tutorial.

Session memory that survives across days, inbox triage workflows, lightweight task tracking, reusable prompt patterns, and a daily loop that makes Claude consistently useful.

// book 1

patriola.com

Book 1 · Patriola’s Guide to Claude

Productivity

Name: Patriola's Guide to Claude: Productivity
Availability: InStock
Author: Patriola

Workflows for people who want more than a chatbot.

Buy on Amazon

What this book is

A working system

A tour of the actual setups, prompts, and habits used to run real work with Claude every day — the kind of detail you only get from someone who has been using it long enough to find what breaks.

If you already use Claude regularly and want to stop reinventing the same patterns, this gives you the shape of a working system you can adapt.

What you’ll learn

Five areas, one working system

session-memory — Write memory files Claude loads before every session: anchor-formatted Markdown with priority ordering, a PROJECT: section in CLAUDE.md, and a daily-log pattern that builds context across weeks without hitting the token ceiling.
inbox-triage — Turning email and message backlogs into structured action. Pattern: paste the inbox, get a JSON list with owner, due-date, and dependency fields — then feed that list back to Claude for scheduling and delegation.
task-tracking — Lightweight task files in Markdown or JSONL that survive long projects: status (queued / claimed / done / blocked), priority integers, and a daily-brief prompt that reads the queue and surfaces only what matters now.
prompt-patterns — Reusable prompt shapes that sharpen with use: the task-brief format (context + goal + constraints), the structured-output request (JSON schema inline), and the continuation prompt (here is where we left off + here is today’s question).
daily-loop — A repeatable morning routine: CLAUDE.md pre-read, yesterday’s decisions re-surfaced, today’s tasks scoped. The full loop runs in under three minutes and makes the rest of the day measurably faster.
inbox-triage — Turning email and message backlogs into structured action.
task-tracking — Lightweight systems that survive long projects without rotting.
prompt-patterns — Reusable shapes that get sharper the more you use them.
daily-loop — A small, repeatable rhythm that makes Claude useful every day.

From the book

A preview

The point isn’t to get Claude to do impressive things in a single session. The point is to build a loop you can run tomorrow, and next month, without remembering what you did today.

You — Monday morning Here’s my task list from last week. Which items are still unresolved? Flag anything that has a dependency I might be blocking.

Claude Three items are unresolved: [1] API integration — blocked on your sign-off for the spec. [2] Content review — no response logged since Thursday. [3] Budget request — marked pending, no follow-up. You are the dependency on all three…

Once you build the habit of handing Claude your week at the start of Monday and asking what’s unresolved, you stop being the person who drops things.

Who it’s for

Intermediate users

You’ve used Claude enough to know the basics and want a complete working system. If you’re still learning what Claude is, start with the free resources at anthropic.com first — this book picks up from there.

A longer excerpt is available to newsletter subscribers.

Buy on Amazon

More from Patriola

Stay current

New books in this series

One short email per book launch.