Basic Memory Images
Generate repository visuals with evidence-grounded content and canonical output
paths. The file and marker names still say "infographic" for compatibility, but
PR generation is image-first: scene, poster, painting, photograph, cover,
tableau, staged artifact, or another editorial visual moment that describes the
intent of the PR. PR images are non-gating BM Bossbot artifacts; changelog and
release-summary images are manual evidence-pack workflows.
Output Contract
- Base output directory:
docs/assets/infographics/
- PR image:
docs/assets/infographics/pr-<number>.webp
- Changelog image:
docs/assets/infographics/changelog.webp
- Weekly image:
- This is always a 2-Week Retro window: previous ISO week through current ISO
week (
start-week = current-week - 1, end-week = current-week).
- Same year window:
docs/assets/infographics/<year>-w<start-week>-w<end-week>.webp
- Cross-year window:
docs/assets/infographics/<start-year>-w<start-week>-<end-year>-w<end-week>.webp
PR Mode
PR mode uses the BM Bossbot summary block as source material. Do not hand-write
claims that are not present in the PR body.
- Fetch the PR body:
gh pr view <number> --json body --jq '.body // ""' > /tmp/bm-pr-body.md
- Generate the canonical asset:
uv run --script scripts/generate_pr_infographic.py \
--pr-number <number> \
--pr-body-file /tmp/bm-pr-body.md \
--theme "<optional visual theme>" \
--provenance-output /tmp/bm-infographic-provenance.md \
--output docs/assets/infographics/pr-<number>.webp
If the PR body contains a managed image theme block, the script reads it
automatically:
<!-- BM_INFOGRAPHIC_THEME:start -->
<theme>
<!-- BM_INFOGRAPHIC_THEME:end -->
Before spending an image call, test the prompt path locally:
uv run --script scripts/generate_pr_infographic.py \
--pr-number <number> \
--pr-body-file /tmp/bm-pr-body.md \
--theme "<optional visual theme>" \
--output docs/assets/infographics/pr-<number>.webp \
--print-prompt
--dry-run is an alias for --print-prompt; both print the final prompt and
exit without calling OpenAI.
When no theme is supplied, the script selects a deterministic BM visual
direction from the style pool below based on the PR number and Bossbot summary.
This keeps repeated PR images from collapsing into the same generic visual.
When the image is generated, also write provenance with
--provenance-output <path>. BM Bossbot publishes that managed block into the
PR body with these markers:
<!-- BM_INFOGRAPHIC_PROVENANCE:start -->
...
<!-- BM_INFOGRAPHIC_PROVENANCE:end -->
The provenance block records the generated asset path, image model, size,
quality, image mode, theme source, and selected visual direction. It
intentionally does not dump the full generated prompt into the PR body. Treat
this block as debugging and creative provenance only; it is not a merge gate.
The PR image is visual support only. The authoritative merge gate is the
GitHub commit status named BM Bossbot Approval.
Changelog Mode
Build an evidence pack before writing a prompt:
- diff truth source: merged PR diffs, merge commits, or local reconstructed diffs
- changed-file orientation:
git diff --stat plus key file reads
- impact ledger: before/after outcomes tied to actual changes
- discard list: misleading titles, reverted work, rename-only churn, speculative TODOs
- chosen image form: poster, scene, tableau, cover, painting, photograph,
staged artifact, or another editorial visual moment
- chosen BM style category: exactly one category from the selection pool below
Read these references before drafting the prompt:
references/prompt-blueprint.md
references/style-balance.md
Read the current CHANGELOG.md entries and include the latest meaningful
changes.
Style And Category Selection
Select exactly one BM style category per image based on semantic fit. The
visual language should be recognizable and tasteful, while staying
business-readable.
Create an image-first visual form that communicates the change: poster, scene,
tableau, cover image, painting, photograph, staged artifact, or another
editorial visual moment. Maps, diagrams, dossiers, charts, and labels can appear
as props inside the scene, but do not make a text-heavy infographic.
BM category pool:
- computer science college textbooks: SICP-style diagrams, algorithms lectures,
compiler pipelines, automata, database systems, type theory, operating systems
- classic literature subjects: sea voyages, gothic manors, Dickensian city maps,
Austen social graphs, library marginalia, travel journals
- fantasy/D&D-inspired: quest maps, dungeon keys, guild ledgers, spellbooks,
bestiaries, tavern notice boards; no copyrighted settings
- Music: Metal, Hard Rock, Punk, techno, soul, reggae bands; no pop music, no
direct band logos, album covers, or musician likenesses
- sci-fi: Star Wars inspired knockoff, Spaceballs-adjacent space opera, fleet
routes, mission consoles, contraband manifests; avoid copyrighted characters,
logos, or named fictional universes
- Conan the barbarian-inspired sword-and-sorcery: ruined temples, desert routes,
battle standards, ancient maps; no named character likenesses
- Comic books: issue covers, splash pages, action-panel maps, caption boxes,
halftone energy, clean sound-effect typography
- French new wave movies: poster style, stark typography, city route maps,
jump-cut sequencing, high-contrast editorial photography cues
- WWII propaganda posters: home-front public-information poster language,
logistics arrows, ration charts, mobilization maps, bold simplified figures;
no real-world party symbols, hate imagery, dehumanizing slogans, or false
historical claims
- Italian movie posters: hand-painted drama, bold credits, expressive color,
route-map collage, 1960s or 1970s cinema energy; no direct film titles or
actor likenesses
- Shakespeare: stage maps, acts and scenes, dramatis personae, royal courts,
backstage cue sheets
- Greek mythology: temple diagrams, constellation routes, hero's journey maps,
oracle tablets, labyrinths, ship routes
- noir detective boards: case files, red-string maps, typed evidence labels,
precinct wall charts
- NASA mission-control dashboards: launch timelines, telemetry maps, orbital
routes, status boards
- space exploration and astronomy: celestial atlases, observatory charts,
star-field maps, orbital mechanics diagrams, planetary survey routes,
telescope annotations, mission trajectories, deep-space timelines
- paintings: abstract painting, classical landscape, Remington-inspired western
action painting, Rembrandt-inspired chiaroscuro, historical mural, stormy
seascape, allegorical editorial painting
- classic black-and-white photography: documentary field report, newsroom
archive print, editorial photo essay, street photography, high-contrast
darkroom print, contact sheet, civic infrastructure photograph
- 80's action movies: practical explosions, smoky backlit warehouses, neon city
streets, helicopter searchlights, mission dossiers, heroic silhouettes,
high-stakes countdowns, painted ensemble posters; no direct actor likenesses,
real film titles, franchise marks, or catchphrases
- alchemy manuscripts: transformation diagrams, annotated symbols, recipe-like
process maps, illuminated margins
- brutalist civic planning: transit maps, concrete signage, zoning blocks,
infrastructure diagrams
Selection rules:
- Pick one category only; do not create mixed mashups.
- Pick the most appropriate image form. Prefer an actual scene, poster,
painting, photograph, tableau, or cover over a text-heavy infographic.
- Match metaphor to content, but do not overthink it. The category is a creative
catalyst, not a semantic constraint.
- Use a polished editorial rendering direction: smooth anti-aliased
text, high contrast, clean edges, readable labels.
- Make the category drive the composition through a readable staged moment,
editorial composition, symbolic environment, route, artifact, or visual
metaphor.
- Keep the structure literal enough to aid understanding, but not so heavy that
it obscures engineering meaning.
- Give the image generator creative latitude on layout, structure, color palette,
and visual metaphors. Be precise about what content to show, loose about how
to show it.
- Do not use copyrighted characters, logos, or named fictional universes. Use
genre cues, knockoffs, and original compositions instead.
Content-First Aesthetic Contract
The meaning must be readable and clearly hierarchical. Everything else is
creative territory: image form, layout, visual metaphors, decorative elements,
color choices, and category-specific visual language.
Hierarchy:
- Meaning: what shipped, what changed, and why it matters must be clear.
- If the image uses text, labels, sections, or evidence bullets, they must be
legible.
- The selected category's visual DNA should drive the composition as a poster,
scene, painting, photograph, tableau, cover, or symbolic object arrangement.
- Do not play it safe. A visually striking image that someone wants to look at
beats a correct but boring one.
Hard rules:
- Content sections and labels must be readable when present. Text cannot be
obscured by decorations.
- Do not use lore-heavy copy that competes with engineering or business meaning.
- Every prompt must include a clear image-first composition cue: a staged scene,
poster composition, painting, photograph, symbolic tableau, hero object,
mission room, dossier, artifact, route, or visual metaphor.
- Do not over-prescribe exact coordinates or panel geometry; give a composition
backbone and let the model compose around it.
Generation
- Write the final prompt to a temporary markdown file.
- Generate with the shared image helper:
uv run --script scripts/generate_infographic.py \
--prompt-file /tmp/bm-infographic-prompt.md \
--output docs/assets/infographics/<name>.webp
- Verify the image exists and is readable before reporting success.
Quality Bar
- Tell a concrete before/after value story, not vague improvement claims.
- Stay understandable for both engineers and non-technical stakeholders.
- Use plain-language section titles and labels when text is present.
- Include clear visual hierarchy: title, staged focal point, symbolic scene,
evidence props, or hero object.
- Avoid invented facts; only use provided source material.
- Favor shipped outcomes over intermediate or reverted work.
- Preserve readability with high contrast, non-tiny labels, and uncluttered
layout.
1---
2name: infographics
3description: Use when generating Basic Memory PR, changelog, release, or weekly images from Codex.
4metadata:
5 source: https://skillmd.com/skills/basicmachines-co-basic-memory/infographics
6---
7
8# Basic Memory Images
9
10Generate repository visuals with evidence-grounded content and canonical output
11paths. The file and marker names still say "infographic" for compatibility, but
12PR generation is image-first: scene, poster, painting, photograph, cover,
13tableau, staged artifact, or another editorial visual moment that describes the
14intent of the PR. PR images are non-gating BM Bossbot artifacts; changelog and
15release-summary images are manual evidence-pack workflows.
16
17## Output Contract
18
19- Base output directory: `docs/assets/infographics/`
20- PR image: `docs/assets/infographics/pr-<number>.webp`
21- Changelog image: `docs/assets/infographics/changelog.webp`
22- Weekly image:
23 - This is always a 2-Week Retro window: previous ISO week through current ISO
24 week (`start-week = current-week - 1`, `end-week = current-week`).
25 - Same year window: `docs/assets/infographics/<year>-w<start-week>-w<end-week>.webp`
26 - Cross-year window:
27 `docs/assets/infographics/<start-year>-w<start-week>-<end-year>-w<end-week>.webp`
28
29## PR Mode
30
31PR mode uses the BM Bossbot summary block as source material. Do not hand-write
32claims that are not present in the PR body.
33
341. Fetch the PR body:
35
36```bash
37gh pr view <number> --json body --jq '.body // ""' > /tmp/bm-pr-body.md
38```
39
402. Generate the canonical asset:
41
42```bash
43uv run --script scripts/generate_pr_infographic.py \
44 --pr-number <number> \
45 --pr-body-file /tmp/bm-pr-body.md \
46 --theme "<optional visual theme>" \
47 --provenance-output /tmp/bm-infographic-provenance.md \
48 --output docs/assets/infographics/pr-<number>.webp
49```
50
51If the PR body contains a managed image theme block, the script reads it
52automatically:
53
54```markdown
55<!-- BM_INFOGRAPHIC_THEME:start -->
56<theme>
57<!-- BM_INFOGRAPHIC_THEME:end -->
58```
59
60Before spending an image call, test the prompt path locally:
61
62```bash
63uv run --script scripts/generate_pr_infographic.py \
64 --pr-number <number> \
65 --pr-body-file /tmp/bm-pr-body.md \
66 --theme "<optional visual theme>" \
67 --output docs/assets/infographics/pr-<number>.webp \
68 --print-prompt
69```
70
71`--dry-run` is an alias for `--print-prompt`; both print the final prompt and
72exit without calling OpenAI.
73
74When no theme is supplied, the script selects a deterministic BM visual
75direction from the style pool below based on the PR number and Bossbot summary.
76This keeps repeated PR images from collapsing into the same generic visual.
77
78When the image is generated, also write provenance with
79`--provenance-output <path>`. BM Bossbot publishes that managed block into the
80PR body with these markers:
81
82```markdown
83<!-- BM_INFOGRAPHIC_PROVENANCE:start -->
84...
85<!-- BM_INFOGRAPHIC_PROVENANCE:end -->
86```
87
88The provenance block records the generated asset path, image model, size,
89quality, image mode, theme source, and selected visual direction. It
90intentionally does not dump the full generated prompt into the PR body. Treat
91this block as debugging and creative provenance only; it is not a merge gate.
92
93The PR image is visual support only. The authoritative merge gate is the
94GitHub commit status named `BM Bossbot Approval`.
95
96## Changelog Mode
97
98Build an evidence pack before writing a prompt:
99
100- diff truth source: merged PR diffs, merge commits, or local reconstructed diffs
101- changed-file orientation: `git diff --stat` plus key file reads
102- impact ledger: before/after outcomes tied to actual changes
103- discard list: misleading titles, reverted work, rename-only churn, speculative TODOs
104- chosen image form: poster, scene, tableau, cover, painting, photograph,
105 staged artifact, or another editorial visual moment
106- chosen BM style category: exactly one category from the selection pool below
107
108Read these references before drafting the prompt:
109
110- `references/prompt-blueprint.md`
111- `references/style-balance.md`
112
113Read the current `CHANGELOG.md` entries and include the latest meaningful
114changes.
115
116## Style And Category Selection
117
118Select exactly one BM style category per image based on semantic fit. The
119visual language should be recognizable and tasteful, while staying
120business-readable.
121
122Create an image-first visual form that communicates the change: poster, scene,
123tableau, cover image, painting, photograph, staged artifact, or another
124editorial visual moment. Maps, diagrams, dossiers, charts, and labels can appear
125as props inside the scene, but do not make a text-heavy infographic.
126
127BM category pool:
128
129- computer science college textbooks: SICP-style diagrams, algorithms lectures,
130 compiler pipelines, automata, database systems, type theory, operating systems
131- classic literature subjects: sea voyages, gothic manors, Dickensian city maps,
132 Austen social graphs, library marginalia, travel journals
133- fantasy/D&D-inspired: quest maps, dungeon keys, guild ledgers, spellbooks,
134 bestiaries, tavern notice boards; no copyrighted settings
135- Music: Metal, Hard Rock, Punk, techno, soul, reggae bands; no pop music, no
136 direct band logos, album covers, or musician likenesses
137- sci-fi: Star Wars inspired knockoff, Spaceballs-adjacent space opera, fleet
138 routes, mission consoles, contraband manifests; avoid copyrighted characters,
139 logos, or named fictional universes
140- Conan the barbarian-inspired sword-and-sorcery: ruined temples, desert routes,
141 battle standards, ancient maps; no named character likenesses
142- Comic books: issue covers, splash pages, action-panel maps, caption boxes,
143 halftone energy, clean sound-effect typography
144- French new wave movies: poster style, stark typography, city route maps,
145 jump-cut sequencing, high-contrast editorial photography cues
146- WWII propaganda posters: home-front public-information poster language,
147 logistics arrows, ration charts, mobilization maps, bold simplified figures;
148 no real-world party symbols, hate imagery, dehumanizing slogans, or false
149 historical claims
150- Italian movie posters: hand-painted drama, bold credits, expressive color,
151 route-map collage, 1960s or 1970s cinema energy; no direct film titles or
152 actor likenesses
153- Shakespeare: stage maps, acts and scenes, dramatis personae, royal courts,
154 backstage cue sheets
155- Greek mythology: temple diagrams, constellation routes, hero's journey maps,
156 oracle tablets, labyrinths, ship routes
157- noir detective boards: case files, red-string maps, typed evidence labels,
158 precinct wall charts
159- NASA mission-control dashboards: launch timelines, telemetry maps, orbital
160 routes, status boards
161- space exploration and astronomy: celestial atlases, observatory charts,
162 star-field maps, orbital mechanics diagrams, planetary survey routes,
163 telescope annotations, mission trajectories, deep-space timelines
164- paintings: abstract painting, classical landscape, Remington-inspired western
165 action painting, Rembrandt-inspired chiaroscuro, historical mural, stormy
166 seascape, allegorical editorial painting
167- classic black-and-white photography: documentary field report, newsroom
168 archive print, editorial photo essay, street photography, high-contrast
169 darkroom print, contact sheet, civic infrastructure photograph
170- 80's action movies: practical explosions, smoky backlit warehouses, neon city
171 streets, helicopter searchlights, mission dossiers, heroic silhouettes,
172 high-stakes countdowns, painted ensemble posters; no direct actor likenesses,
173 real film titles, franchise marks, or catchphrases
174- alchemy manuscripts: transformation diagrams, annotated symbols, recipe-like
175 process maps, illuminated margins
176- brutalist civic planning: transit maps, concrete signage, zoning blocks,
177 infrastructure diagrams
178
179Selection rules:
180
181- Pick one category only; do not create mixed mashups.
182- Pick the most appropriate image form. Prefer an actual scene, poster,
183 painting, photograph, tableau, or cover over a text-heavy infographic.
184- Match metaphor to content, but do not overthink it. The category is a creative
185 catalyst, not a semantic constraint.
186- Use a polished editorial rendering direction: smooth anti-aliased
187 text, high contrast, clean edges, readable labels.
188- Make the category drive the composition through a readable staged moment,
189 editorial composition, symbolic environment, route, artifact, or visual
190 metaphor.
191- Keep the structure literal enough to aid understanding, but not so heavy that
192 it obscures engineering meaning.
193- Give the image generator creative latitude on layout, structure, color palette,
194 and visual metaphors. Be precise about what content to show, loose about how
195 to show it.
196- Do not use copyrighted characters, logos, or named fictional universes. Use
197 genre cues, knockoffs, and original compositions instead.
198
199## Content-First Aesthetic Contract
200
201The meaning must be readable and clearly hierarchical. Everything else is
202creative territory: image form, layout, visual metaphors, decorative elements,
203color choices, and category-specific visual language.
204
205Hierarchy:
206
2071. Meaning: what shipped, what changed, and why it matters must be clear.
2082. If the image uses text, labels, sections, or evidence bullets, they must be
209 legible.
2103. The selected category's visual DNA should drive the composition as a poster,
211 scene, painting, photograph, tableau, cover, or symbolic object arrangement.
2124. Do not play it safe. A visually striking image that someone wants to look at
213 beats a correct but boring one.
214
215Hard rules:
216
217- Content sections and labels must be readable when present. Text cannot be
218 obscured by decorations.
219- Do not use lore-heavy copy that competes with engineering or business meaning.
220- Every prompt must include a clear image-first composition cue: a staged scene,
221 poster composition, painting, photograph, symbolic tableau, hero object,
222 mission room, dossier, artifact, route, or visual metaphor.
223- Do not over-prescribe exact coordinates or panel geometry; give a composition
224 backbone and let the model compose around it.
225
226## Generation
227
2281. Write the final prompt to a temporary markdown file.
2292. Generate with the shared image helper:
230
231```bash
232uv run --script scripts/generate_infographic.py \
233 --prompt-file /tmp/bm-infographic-prompt.md \
234 --output docs/assets/infographics/<name>.webp
235```
236
2373. Verify the image exists and is readable before reporting success.
238
239## Quality Bar
240
241- Tell a concrete before/after value story, not vague improvement claims.
242- Stay understandable for both engineers and non-technical stakeholders.
243- Use plain-language section titles and labels when text is present.
244- Include clear visual hierarchy: title, staged focal point, symbolic scene,
245 evidence props, or hero object.
246- Avoid invented facts; only use provided source material.
247- Favor shipped outcomes over intermediate or reverted work.
248- Preserve readability with high contrast, non-tiny labels, and uncluttered
249 layout.