Skip to content

feature/Slide-proposal-topic · L-261107-75b313 - #25

Merged
lchoquel merged 1 commit into
devfrom
feature/Slide-proposal-topic
Nov 7, 2026
Merged

lchoquel merged 1 commit into
devfrom
feature/Slide-proposal-topic

Conversation

@lchoquel

@lchoquel lchoquel commented Nov 7, 2026 •

Copy link
Copy Markdown
Member

TL;DR

  • The slide designer now draws each proposal's mockup with the deck's own title, and returns every theme paired with the mockup drawn in it.
  • The image step never saw the brief, so the image model invented a title: a "Q4 2025 Financial Results" brief came back reading "Q3 2024".
  • ⚠️ Breaking: generate_design_proposals_from_rough_brief returns DesignProposals instead of Html; the HTML page is now generate_design_proposals_report.

Behaviour changes

  • The mockup's title slide shows a subject and a period the image model made up → it shows the brief's topic word for word, and the other three slides carry placeholder content fitting the topic, the audience and the goal.
  • Polishing the brief could reword the topic → it keeps the topic exactly as typed.
  • The main pipe returns an HTML page whose images and themes sit in two separate grids → it returns DesignProposals: the polished brief and a list of proposals, each a theme with its mockup.
  • The report showed the "Enhanced Brief" block even when the polish changed nothing → it shows it only when a field differs.

Breaking changes

  • A caller of generate_design_proposals_from_rough_brief that read the Html output names generate_design_proposals_report instead, which takes the same brief and returns the page, now one card per proposal with its mockup beside its theme. A caller that wants the old pipe exactly stays at @v0.3.0. The next release is a minor, v0.4.0.

Changes

methods/slide_designer/slide_designer.mthds

  • render_visual_proposal takes polished_brief beside theme, and its prompt names $polished_brief.topic as the title to draw word for word, keeping the four-slide mosaic.
  • New DesignProposal and DesignProposals concepts; a draft_proposal sub-sequence (draw, then pair through a PipeCompose construct) batched over the themes, then assemble_proposals.
  • New generate_design_proposals_report sequence; compose_proposals_report reads DesignProposals and compares the original and polished briefs field by field.
  • The unused Slide and SlidePrompt concepts are removed, and the domain and pipe descriptions say what the method now does.

methods/slide_designer/METHODS.toml

  • Exports generate_design_proposals_report beside the main pipe; the description says what the result pairs.

How it was verified

  • plxt fmt --check and plxt lint on the bundle and the manifest: clean.
  • pipelex validate bundle methods/slide_designer/ (Pipelex 0.95.1): "Successfully validated the method".
  • Live runs on the hosted API: the "Q4 2025 Financial Results" brief, run_6dcc9217-961d-41be-9f1e-bc081221bd86, drew three mockups all titled "Q4 2025 Financial Results", each in its own theme's palette; the sample inputs.json, run_3de8f0a8-5744-476f-8696-76beab5400fc, kept the topic as typed and drew it as the title; generate_design_proposals_report, run_6a6de223-e8a7-4ef0-b41e-ed7c346be41d, rendered three cards, each mockup beside its own theme.
  • compose_proposals_report rendered alone from the first run's result: the "Enhanced Brief" block is hidden for an unchanged brief and shown for a topic-only one.

Documentation

  • CHANGELOG.md [Unreleased]: the breaking change under Changed, the title fix under Fixed.
  • README.md: the slide_designer row says what the result pairs and names the report entry.
  • The manifest's description and the bundle's concept and pipe descriptions.

Not done

  • The copies of this bundle in pipelex-demos, pipelex-demo-frostbeam and mthds-form's input-form fixture are not fed from the library and keep the old image step.
  • The release itself, cut separately with the /release skill.

Closes L-261107-75b313

🤖 Generated with Claude Code

https://claude.ai/code/session_019TF9N3ixWPEiwAUJDxxxfd


Summary by cubic

Makes the slide designer draw the deck's own title and return each theme paired with its mockup.

The image step previously never saw the brief, so the image model invented a subject and period for the title slide; it now reads the polished brief and draws its topic word for word, with the other slides' placeholder content fitting the topic, audience and goal. The polish step keeps the topic exactly as typed.

Breaking change

  • generate_design_proposals_from_rough_brief now returns DesignProposals (the polished brief plus one theme-and-mockup pair per proposal) instead of the HTML page; callers use the newly exported generate_design_proposals_report for the old page and stay on @v0.3.0 to keep the old pipe.
  • The report renders one card per proposal with its mockup beside its theme, and shows the "Enhanced Brief" block only when a field actually differs.

Written for commit 3f6b2e9. Summary will update on new commits.

View guided diff

…s mockup

The image step now reads the polished brief and draws its topic word for word as the deck's title, and the polish keeps the topic as typed. The main pipe returns DesignProposals (the polished brief and one theme-and-mockup pair per proposal) instead of Html; the report moves to the exported generate_design_proposals_report, one card per proposal. The unused Slide and SlidePrompt concepts are removed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019TF9N3ixWPEiwAUJDxxxfd
@lchoquel
lchoquel merged commit b8d96ee into dev Nov 7, 2026
1 check passed
@lchoquel
lchoquel deleted the feature/Slide-proposal-topic branch November 7, 2026 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant