How to use this catalog

This catalog is built for one job: shrink the time between a project landing on your desk and a credible solution outline existing on paper.

The 30-minute solutioning workflow

When a new requirement arrives, work through these steps:

1. Classify (5 minutes)

Use the decision tree on the Patterns Overview page to land on a category. Don't agonise — close-enough is fine, and you can re-classify later.

2. Match a pattern (5 minutes)

Open the category index and scan the table. Pick the pattern whose "Use this when" list matches your situation most closely. If two patterns are close, read both — the differences will sharpen your understanding of the requirement.

3. Copy the tech stack (5 minutes)

The chosen pattern's technology table is your starting baseline. Don't change anything yet — just copy it into the project document.

4. Read the ADRs (10 minutes)

Open every linked ADR. These are the trade-offs others have already debated. Most of the time they apply to your project unchanged. When they don't, that's the most valuable signal in the entire process — it tells you exactly what is unusual about this project.

5. Document the deviations (5 minutes)

For each place where your project differs from the pattern, note:

• What's different
• Why
• What new risks this introduces

If a deviation is significant, open a draft ADR for review.

What this catalog is not

• Not a substitute for thinking. The patterns are starting points. Every project has unique constraints.
• Not a guarantee. Just because a pattern is rated "Adopt" today doesn't mean it will be in 18 months. Always check the "Last reviewed" date.
• Not exhaustive. New categories and patterns are added as we encounter them. If your project doesn't fit, that's a contribution opportunity — see Contributing.