Blog

Capture workflows for Claude.

Short, honest guides on keeping what matters from your AI conversations. Written by someone who builds with Claude every week.

Building a business a week with AI, in public

The SideRoad method: one week per business, AI as the team, every revenue number published. The week's structure and the honest math.

Productivity prompts for Claude worth stealing

Eight briefs that survived daily use: meeting structurer, end-of-session capture, weekly review, task triage, and more. Copy them as written.

What is Claude Cowork? A plain-English guide

Chat answers questions; Cowork completes work on your real files. What it is, how it differs from chat and Claude Code, and what it's genuinely good at.

The honest guide to AI note-taking

Recorder bots, AI inside note apps, and capture at source are three different products wearing one label. What each is for, and how to buy only what you need.

Claude Code tips from 30+ weekly builds

Nine habits that survived a business-a-week pace: plan mode first, a one-page CLAUDE.md, a capture file in every repo, and the end-of-session ritual.

How to write a Claude Skill, start to finish

A folder, a SKILL.md, and twenty minutes. The full tutorial, why the description decides everything, and when a script earns its place.

The best Claude Skills in 2026, by use case

The picks for developers, marketing, writing, business, and research, with GitHub links for every one, plus where the community actually finds them.

Claude Skills vs MCP: which one do you need?

A skill changes how Claude behaves; MCP changes what it can reach. The decision test, with real examples.

How to export Claude conversations

How to export your data, how to save one chat well, and the capture habit that makes exports boring.

How to take meeting notes with Claude

Two workflows that need no recorder bot, the structuring prompt to steal, and where the outputs live.

Why plain text notes outlast every app

Portable, diffable, committable, and now AI-native. The honest case for Markdown as your notes layer.

Does Claude remember previous conversations?

Memory, chat search, and Projects each solve part of the problem. What each actually does, and the one job none of them do.

How to use Claude Projects to organize your work

How to split projects, what belongs in project knowledge, and the one file habit that makes a project compound instead of sprawl.

Can Claude be your task manager?

Yes for capture, triage, and breakdown; no as a system of record, until you give it one Markdown checklist it can read and write.

You don't need an AI second brain.

Second-brain systems fail at capture, every time. The honest alternative: a two-second habit and one plain file you own.

How to save notes and tasks from Claude conversations

Three ways to capture the good stuff before it scrolls away: manual copying, an end-of-session summary prompt you can steal, and a one-command capture skill.

What are Claude Skills? A plain-English guide

What skills are, how they differ from custom instructions and GPTs, how to install one, and what a good one looks like inside, using a real shipped skill as the example.