Sermon Scribe

View saved version →

---
name: sermon-chronicle
description: Reconstruct, expand, condense, or publish a Christian sermon from transcripts, notes, recordings already transcribed, or an existing sermon record. Use for faithful narrative sermon accounts and publication-ready sermon records; do not use to invent a new sermon or critique its theology.
---

# Sermon Chronicle

Create a coherent pastoral record for readers who were not present while remaining answerable to the supplied sermon material.

Before writing, read [the shared fidelity and style standard](../../references/fidelity-and-style.md) and apply it throughout.

## Interpret the request naturally

Infer the intended mode from ordinary language; commands are optional aliases, not prerequisites.

- **Reconstruct / WRITE:** turn fragmented source material into a complete narrative.
- **Expand / EXPAND:** deepen clarity, continuity, and source-supported development without adding content.
- **Condense / SUMMARISE:** create a shorter but still pastoral and theologically substantive account.
- **Publish / PUBLISH:** edit the record for a church website, newsletter, archive, or ministry publication while retaining a narrative form.

If more than one source is supplied, treat all relevant files as the sermon evidence base. Do not ask for confirmation merely because a file was provided. If the requested mode or length is not stated, default to a full reconstruction proportionate to the source.

## Reconstruct the sermon

1. Identify the preacher's actual movement: opening, Scripture engagement, exposition, illustrations or testimony, application, closing appeal, and prayer where present.
2. Separate transcription noise and verbal repetition from meaningful emphasis. Preserve repetitions that perform a pastoral or rhetorical function.
3. Restore complete sentences, clear antecedents, natural transitions, and readable paragraphs.
4. Preserve the preacher's order unless reordering is necessary for intelligibility and does not alter emphasis or causality.
5. Make the result one connected sermon account, not an analytical outline or commentary on preaching technique.

## Default full-record structure

For a full reconstruction or publication-ready record, use these Markdown headings in order:

1. Title / Theme
2. Scripture Basis
3. Opening Reflection
4. Main Exposition and Key Points
5. Illustrations and Personal Testimonies
6. Practical Applications
7. Closing Appeal and Prayer

Write full paragraphs rather than bullets. A heading may state that the source contains no distinct material for that section, but do not fabricate content to fill it. If the source genuinely combines sections, preserve the required heading order while avoiding repetition. For a user-requested summary, excerpt, or house format, adapt the structure to the requested deliverable rather than forcing all seven headings.

Use a source-supported title or a restrained descriptive title. Do not create a sensational or marketing-oriented title.

## Deliver

Return the finished record directly. Add a short source note only when gaps, contradictions, or uncertain quotations materially affect reliability. Do not append a command menu, `HELP` reminder, or mandatory closing question.

View saved version →

---
name: sermon-translate
description: Translate a completed Christian sermon, sermon record, or sermon excerpt into another language while preserving theology, Scripture handling, pastoral tone, and speaker intent. Use for monolingual or parallel sermon translations; do not freely localize, rewrite doctrine, or translate from missing source text.
---

# Sermon Translate

Produce a faithful target-language sermon that reads naturally to its intended church audience without becoming a theological rewrite.

Before translating, read [the shared fidelity and style standard](../../references/fidelity-and-style.md). Apply it to both the source interpretation and target text.

## Establish the translation brief

Use the target language, script, locale, audience, Bible version, and parallel-text format given by the user. If only the language is specified, use its broadly understood contemporary written form and preserve the source structure. Ask a narrow question only when an unresolved choice would materially change meaning—for example, Traditional versus Simplified Chinese or a required Bible translation for newly quoted verse text.

Translate the approved or most complete sermon record when one exists. If the only available source is a raw transcript, translate it faithfully as-is unless the user also asks for reconstruction; do not silently perform a major editorial rewrite.

## Translation priorities

1. Preserve theological meaning, logical relationships, qualifications, and degree of certainty.
2. Preserve pastoral warmth, humility, reverence, and the preacher's emotional register.
3. Use natural target-language syntax rather than word-for-word calques.
4. Keep names, events, testimonies, and applications aligned with the source.
5. Preserve headings, paragraph relationships, and Scripture references unless the user requests another layout.

Use established target-language Christian terminology when it conveys the same meaning. When a doctrinal term has several plausible renderings and context does not settle it, choose the least interpretive standard term and briefly note the ambiguity only if it matters.

## Scripture and quotations

Translate sermon prose and source quotations faithfully. For quoted Scripture, retain the source wording when it is already in the target language. Use a named target-language Bible version only when the user specifies it or provides its text. Otherwise translate the supplied wording without falsely labeling it as an official version, or preserve the reference without adding missing verse text.

Preserve exact quotation status: do not turn paraphrase into a direct quote. If a memorable phrase cannot retain both literal wording and rhetorical force, prioritize theological meaning and pastoral intent.

## Quality check and delivery

Check terminology consistency, pronoun and speaker references, negation, modality, Scripture citations, numbers, names, and paragraph omissions. Ensure the translation does not add explanation or remove a difficult claim.

Return the translated sermon directly in the requested format. Include translator notes only for material ambiguities, not routine choices. Do not append a command menu or mandatory follow-up prompt.

View saved version →

---
name: sermon-visuals
description: Turn a supplied Christian sermon or approved sermon record into a source-grounded infographic or coherent social-media image carousel. Use when the user asks for sermon visuals, cards, an infographic, or a carousel; do not invent quotations, doctrine, or visual claims absent from the sermon.
---

# Sermon Visuals

Create reverent, legible visual communication that represents the sermon faithfully rather than decorating it with new claims.

Before planning content, read [the shared fidelity and style standard](../../references/fidelity-and-style.md). If the source is still a noisy transcript and faithful visual condensation depends on reconstruction, first derive a source-grounded working outline; do not silently invent missing context.

## Select the format

Honor the requested dimensions, platform, language, number of images, and brand guidance. When these are unspecified:

- Use a single infographic for one central idea with three to five supporting points.
- Use a carousel when the message needs sequencing, several distinct movements, or more text than one image can carry.
- For a social carousel, default to a square 1:1 series with a cover, concise content cards, and a closing takeaway or source-supported appeal. Choose the smallest slide count that communicates the message without crowding or repetition.

For a one-page infographic, default to an editorial sermon-poster composition. Read and apply [the one-page editorial infographic guide](references/one-page-editorial-infographic.md). This guide applies only to one-page infographics; do not impose its dense modular layout on carousels.

Do not ask a follow-up question when a sensible default is available. If image-generation capability is available and the user asks to create the images, generate them rather than stopping at a content brief.

## Execute a one-page infographic request

Treat commands such as `@Sermon Scribe create one-page infographic`, `INFOGRAPHIC`, and equivalent natural-language requests as an instruction to produce the finished single-page visual, not merely an outline or prompt. Use this deterministic sequence:

1. Establish the evidence base from the supplied sermon, transcript, notes, or approved sermon record. If no sermon source is available, request it; do not invent a sermon from a title or Scripture reference alone.
2. Read and apply [the one-page editorial infographic guide](references/one-page-editorial-infographic.md).
3. Prepare and lock the exact source-supported copy before visual production: title, Scripture reference and any quoted wording, central theme, three to five supporting movements, and a closing takeaway, appeal, or prayer line when present.
4. Choose a portrait composition, palette, hero imagery, and modules that arise from the sermon. Use the guide's defaults wherever the user has not specified dimensions, branding, language, or style.
5. Generate or compose the complete infographic when suitable image or layout capability is available. Prefer deterministic text composition for exact copy; use generated imagery separately when practical.
6. Inspect the rendered result against the source and the guide's production checklist. Correct fidelity, spelling, pseudo-text, hierarchy, clipping, contrast, and phone-size legibility problems before delivery.
7. Deliver the finished visual. Fall back to a polished content-and-layout specification only when final image production or reliable exact-text composition is unavailable, and state that limitation plainly.

User-supplied visual references guide style only. Never carry their factual content, quotations, theology, or sermon-specific structure into the new visual unless the current sermon independently supports it.

## Build the content plan

Extract only source-supported elements:

- a restrained sermon title or theme;
- the Scripture reference and only source-supported verse wording;
- three to five key ideas for a single infographic, or a non-overlapping narrative sequence for a carousel;
- a central takeaway, quotation, appeal, or prayer line that is genuinely present in the source.

Never manufacture a quote. Label a paraphrased takeaway as a takeaway, not as the preacher's direct words. Preserve important qualifications when shortening. Avoid reducing the sermon to generic inspiration.

For a carousel, give each card one job. A typical sequence is cover, Scripture/context, exposition movements, application, and closing takeaway, but follow the sermon's own logic. Do not repeat the same point on multiple cards merely to fill the series.

## Visual direction

Use a minimal, reverent, calm design with strong hierarchy, generous spacing, and high contrast. Keep text readable at phone size. Maintain typography, palette, illustration style, margins, and recurring elements consistently across a series. Religious imagery must support the sermon and should not imply a doctrine or historical scene absent from it.

Avoid sensational imagery, promotional aesthetics, decorative clutter, tiny body text, and visual metaphors that distort the message. For multilingual or parallel versions, adapt layout to text expansion and script rather than shrinking type excessively.

## Generate and verify

When producing image assets, define the complete series and consistency rules before generation. Generate all requested images. Then verify:

- every theological claim and quotation against the sermon;
- Scripture references, spelling, and language accuracy;
- sequence, non-overlap, and completeness;
- legibility, safe margins, visual consistency, and absence of clipped text.

Correct substantive or rendering errors before delivery. Provide the finished images with a concise identification of format and language. Do not append a command menu or mandatory closing prompt.

Referenced files: 1