The Pattern Room

The Pattern Room

A workshop on using AI in real work — without losing clarity, ownership, or quality.

For

Developers • Students • Product Teams

What You’ll Learn

A practical workflow for using AI with clear steps, checks, and ownership.

Format

In-person • Small Groups • Runs as One-day or Ongoing (Team Sessions)

WHAT IT IS

A practical workshop for working with AI, clearly and with control.

AI is powerful, but real work needs structure. We teach a simple way to break work down, guide the model, review outputs, and ship changes safely. So teams move faster — without losing ownership or quality.

WHO IT"S FOR

Built for real code, taught in a way you can grow into.

Developers who want AI to hold up in real codebases — not just quick demos. Students who want modern workflows and stronger habits early. Product teams who want a shared way of working with AI across people and projects. FOR INDIVIDUALS Curated repos and guided briefs. Learn the workflow without needing a live production codebase. FOR TEAMS Bring your codebase (recommended). Apply the patterns to real work, and align on a shared process.

OUTCOMES

Leave with a way to work with AI and trust the result.

By the end, you can: • Break work into agent-ready tasks with clear checks • Run a simple “plan → do → review” loop reliably • Catch wrong turns early and recover quickly • Make safe changes in an existing repo without chaos • Keep decisions, ownership, and change history visible

WHAT WE COVER

How to work with AI, without the mess.

How AI behaves What it’s strong at, what it guesses, and where it breaks. How to guide it Clear prompts, clear constraints, clear checks. How to work at repo scale Right context, small changes, reliable verification. How to move fast safely Review points, tests, checkpoints, clean handoffs.

For Teams

We can run The Pattern Room as a private team workshop. We recommend using your codebase so the patterns map directly to your work. If needed, we can scope a safe slice in advance. Optional follow-up: weekly or bi-weekly office-hours where participants bring PRs, bugs, refactors, or research. We refine workflows and capture repeatable patterns so the whole team improves over time. Useful when agent adoption is uneven, PR quality is inconsistent, or speed is creating risk. Teams leave aligned on a shared way of working with agents.

HANDS ON WORK

Practice the patterns through three drills — define, build, change.

You’ll work through three practical drills: Define Turn a request into steps, constraints, and checks. Build Ship a small feature with verification. Change Make one safe change in an existing codebase — and prove it works.

LEVEL

Comfortable with code. The rest is taught.

Best for developers who can read and modify code. Students should know one language and basic Git.

BEFORE YOU BOOK

FAQs

The basics, answered.

Is this prompt engineering?

No. It’s about directing: breaking work down, setting constraints, managing context, and verifying outputs.

Who is this for, really?

Developers, students who can follow code, and engineering-led product teams.

Is this for non-engineers?

Yes, if you’re comfortable reading code and want the workflow patterns.

Will we write real code?

Yes. It’s hands-on.

Can this be run on our codebase?

Yes. Recommended for teams. We’ll scope a safe slice in advance so it’s useful and low-risk.

Do we need a specific tool?

No. We’ll align on a short tool list based on your stack. The operating patterns transfer across tools.

What should I bring?

A laptop with standard dev tooling. We’ll share a short setup checklist in advance.

How many people can attend?

Up to 10 per run, to keep it hands-on and properly reviewed.

Is it only one day?

Public runs are usually a full-day workshop. Team runs can also be split into multiple sessions or followed by office-hours.

Why in-person?

Because it’s discussion and practice-heavy. You get attention, feedback, and guided practice.

Why no recording?

To protect proprietary work and keep discussion candid.

What do I leave with?

A repeatable way of working: clear task framing, constraints, context habits, and verification loops you can use immediately. Teams can optionally continue via office-hours.

Is this prompt engineering?

No. It’s about directing: breaking work down, setting constraints, managing context, and verifying outputs.

Who is this for, really?

Developers, students who can follow code, and engineering-led product teams.

Is this for non-engineers?

Yes, if you’re comfortable reading code and want the workflow patterns.

Will we write real code?

Yes. It’s hands-on.

Can this be run on our codebase?

Yes. Recommended for teams. We’ll scope a safe slice in advance so it’s useful and low-risk.

Do we need a specific tool?

No. We’ll align on a short tool list based on your stack. The operating patterns transfer across tools.

What should I bring?

A laptop with standard dev tooling. We’ll share a short setup checklist in advance.

How many people can attend?

Up to 10 per run, to keep it hands-on and properly reviewed.

Is it only one day?

Public runs are usually a full-day workshop. Team runs can also be split into multiple sessions or followed by office-hours.

Why in-person?

Because it’s discussion and practice-heavy. You get attention, feedback, and guided practice.

Why no recording?

To protect proprietary work and keep discussion candid.

What do I leave with?

A repeatable way of working: clear task framing, constraints, context habits, and verification loops you can use immediately. Teams can optionally continue via office-hours.

Design that supports people.

Working with organisations that value clarity, wherever they are.

© Common Pattern 2026 | All Rights Reserved.

Design that supports people.

Working with organisations that value clarity, wherever they are.

instagram
linkedin icon

© Common Pattern 2026 | All Rights Reserved.

Design that supports people.

Working with organisations that value clarity, wherever they are.

© Common Pattern 2026 | All Rights Reserved.