author
From a terminal brief to a deck Noor can actually present
Noor uses the OpenStage skills through either Claude Code or Codex, reviews ordinary source, passes the repository build, and opens the finished slide deck in a browser.
Noor starts with the repository's rules
Noor needs a client-ready deck but does not want an agent inventing a style from scratch. She finds planning, slide, component, and quality skills inside the same repository that will own the result.
ls .claude/skills/{plan-presentation,slide-mode,component-reference,quality-standards}/SKILL.mdThe brief is portable between agents
She can open Claude Code or Codex and issue the same outcome-focused prompt. The agent changes; the instructions, source contract, and review bar do not.
claude # or: codex
The work lands as ordinary source
Noor reviews a content module, route, and registry change. She can edit it, diff it, or hand it to another engineer without exporting a conversation transcript.
git diff -- src/content/proof-before-promise.tsx src/app/proof-before-promise/page.tsx src/content/registry.ts
The repository gets the final word
The build compiles the deck, checks TypeScript, and generates its route. Noor does not accept 'looks right in the prompt' as a delivery state.
npm run build
The thesis is visible in a browser
The generated route opens on a composed title slide. The browser is now evidence of the product result, not merely a viewer for generated text.
/proof-before-promise
Noor can present the finished argument
She advances to the terminal slide and sees both agent workflows inside the deck itself. The artifact now explains how it was made and is ready to share locally for review.
/proof-before-promiseThe payoff
Noor has a built, keyboard-driven presentation with a stable local link and inspectable source.