BAM
Checklist · Intent before generation

Intent before generation.
To fill in before opening Claude, or any other generator.

A generative tool optimizes for the most probable: without a frame, it normalizes your project. This checklist pins down what must stay singular, BEFORE the first generation. Fill it in inside your BAM project (it becomes your project memory), then pass it on to the production tool. Drawn from a real case: the guide BAM + Claude Code.

BAM checklist · Fill in once per project.

Build my project memory Read the BAM + Claude Code guide

1. The intent

  • In one sentence: what must this project never become? (e.g. "a brochure website with sections")
  • What is the guiding metaphor? (a visit, a workshop, a magazine, a conversation...)
  • What must stay true from the first screen to the last?

2. The journey rules

  • The architecture: what are the units of the project (pages, rooms, steps, chapters) and their order?
  • The navigation: how do you move forward, how do you go back, and what is forbidden (e.g. no classic top menu)?
  • The deliberate exceptions: which anti-patterns are intentional, and why? (e.g. a corridor that breaks scrolling to sequence the reading)

An undocumented exception will be "fixed" by the generator at the next iteration. A documented exception is a decision to preserve.

3. The content models

  • Which content types recur? Give them a name (label, note, card, testimonial...).
  • For each type: its mandatory properties (e.g. a label = a repurposed line + a critical reading + shortcuts).
  • Where does companion content live (notes, glossary, disclosures): permanent interface element, or side page?
A room of the "je suis tous" experience with its label: "Ici, l'opacité n'est pas un défaut : c'est un droit"
In the original case, the label is a named content model with its properties. As a result, Claude reproduces it correctly on every screen.

4. The visual language

  • Which colors carry meaning (semantic), which are decorative?
  • For each semantic color: its usage rule, stable on every screen (e.g. red = access to the role, blue = right to opacity).
  • What is the generator not allowed to "re-harmonize to look nice"?

5. The validation points

  • What does the human systematically review before publishing?
  • Who arbitrates when the generator proposes to "fix" an exception?
  • After each generation: check every screen against this checklist, not against the taste of the moment.
The principle

The real lever is not writing better prompts. It is having a system that prevents what is singular from becoming generic again. JOHANNES proposes, your team decides.

Your intent deserves a memory.

Create your BAM project: document these decisions once, reuse them at every generation.

Create my marketing system See all templates