Clear Workflows

What it is

Clear Workflows is a learning library, not a blog. Everything on it is meant to be worked through. Plain-language explanations sit alongside quizzes, hands-on workshops, and templates you can take straight into your own work.

What ties it together is judgment. It starts with how these models actually work, what they are genuinely good at and where they fall apart, so you can decide for yourself where AI is worth using and where it is not. It is written for developers, analysts, managers, and anyone whose work is shifting because of AI.

How it came together

Clear Workflows took months, and most of that time went into the thinking, not the code. I read widely, drafted explanations, and rewrote the ones that only sounded clear until they actually were.

It was shaped by people as much as by reading. I talked with developers, analysts, and managers who use these tools every day, and with people who understand the underlying subjects far better than I do. Their questions, pushback, and blind spots decided what made it in and how each piece is explained.

The bar stayed the same throughout. Every guide should hold up in front of someone who actually knows the topic.

The shape of the library

It opens with three foundational presentations, meant to be read in order: how AI actually works, how to prompt it well, and what changes once you give a model tools and a goal. Each one comes with a quiz, and the core decks have audio narration on every slide.

From there it opens up. There are hands-on workshops for building with AI, covering planning, debugging, refactoring, documenting, and shipping code without taking the output on faith. Others take the same thinking to everyday work: process flows, handoffs, decisions, and getting a team ready for change.

There is also a growing set of reusable playbooks and templates, things like an AI use-case canvas or a prompt checklist, that you can drop straight into your own work.

How it is built

Under the hood it is a React and TypeScript app, built with Vite and server-rendered through Express so pages arrive fast and fully formed. It runs in both English and French.

All the content is stored as plain typed data, one file per piece in each language, kept separate from the code that displays it. Adding a guide, quiz, or workshop is mostly just writing it; the rest is wired up once and reused.

The decks, quizzes, and workshops all run on the same set of components, so they behave consistently. The same keyboard shortcuts and deep links for jumping around, an instructor view for presenting a deck live, scoring on the quizzes, and workshop progress that saves as you go.

Bilingual by design

The whole site is bilingual. I write the marketing copy by hand in both English and French, so neither version reads like a translation of the other.

There is far more guide and workshop material than I could retranslate by hand every time I change a line, so the French for those runs through a translation step I tuned to my own voice and regenerate whenever the English changes. Getting it to read naturally is harder than it sounds when the source is technical writing.