2 Commits
Author SHA1 Message Date
glennandClaude Opus 5 d913cdf09a Add the run-of-show and one-pager templates the README describes
templates/README.md specified three docs; only demo-script-1pager.template.html
existed, so two of the three were rebuilt from the prose every engagement. Both
now ship, matching the section order the README already documented, with
brand.css inlined and no external deps beyond Google Fonts.

The markup comments say what belongs in each slot rather than naming it: status
pills come from the verification log, so "tested" means Test heroes actually
exercised it; the pre-loaded data table marks the records that must stay
untouched, because a live click is consumed the first time it is used.

Two rules from the first engagement to use them:

No rate card means deleting the investment grid and keeping the note that
explains its absence. Filling those cards to avoid a gap contradicts Phase C's
"every number traces to something", and an invented figure becomes the figure
you are held to.

The docs carry spoken lines, so write them in the language the demo is held in.
An English Say column for a Dutch demo gets translated live in the room, which
is exactly where the wording stops matching the client's own quoted words.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 14:43:27 +02:00
SMEtoolsandClaude Opus 4.8 618bdcb444 odoo-demo-architect: discovery -> live Odoo demo + sales docs, AI-built
Public skill for Claude Code. Mines a discovery call, researches native-vs-custom,
stands up a working Odoo demo over XML-RPC (modules + data + tested hero features),
and generates run-of-show, one-pager, and a 1-page demo script.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SBytQq5dcASi4ETm7n6THb
2026-06-28 20:13:22 +03:00