--- name: t13-presentations description: Create or revise editable T13 presentations from the T13 dark or light template, with concise content, readable typography and a visual review of every slide before delivery. --- # T13 presentations Create a presentation that people can read, understand and edit. Less is more. Use the user's language for slide content. Follow an explicit brief and preserve approved content. ## Start from the template - Use the supplied T13 PPTX or Google Slides template. If none is supplied, obtain the chosen variant from https://prezentacje.t13.dev. Do not invent a new visual identity. - Establish the audience, purpose, presentation setting and intended next step. Infer routine details from the brief; ask only about missing information that materially changes the result. - Select only the layouts needed for the story. The template is a library, not a requirement to use all 33 slides. Keep the closing slide last. - Choose one variant for the whole deck. Dark slides keep a dark background; light slides keep a light background. Accent cards and meaningful photographs may use other palette colors. - Work on a copy. Keep text, tables, charts and diagram components native and editable. Do not flatten entire slides into images to conceal layout problems. ## Write for understanding - Give each slide one main message. Prefer a title that states the point. Do not add overlines, redundant labels or decorative slogans. - Never use an em dash (U+2014), including in titles, notes, captions and generated guidance. Rewrite the sentence with a full stop, comma, colon or parentheses. Do not substitute two hyphens. - Use short, concrete sentences. Remove filler, repeated claims, unnecessary introductions and decorative text. - Longer text is allowed when the audience needs it. Use the plain text, two-column or paragraph-and-image layouts. Divide long content across slides before shrinking it to fit. - Use bullets for parallel points and numbered lists for a meaningful sequence. Lists with six to eight points are valid when each point is concise and readable. Do not impose a five-point limit. - Replace all instructional placeholders and sample claims before delivering a finished presentation. For a reusable template, retain only intentional, clearly named placeholders. ## Compose with restraint - Preserve the template's 16:9 format, alignment grid, margins and spacing rhythm. Align edges deliberately and balance content vertically. - Use Google Sans Flex for titles and body text, and Google Sans Code for short technical labels and numbers. Check that the target application actually renders these fonts. If it cannot, use an agreed compatible fallback and review line wrapping again. - Retain the existing type scale where possible. For projected slides, aim for body text around 24 pt or larger; dense reference slides can use 20 to 22 pt when still readable. Titles are usually 32 to 48 pt. Split content instead of silently reducing it below a readable size. - Use natural line spacing, consistent paragraph gaps and short line lengths. Avoid isolated final words and excessive gaps between related lines. Do not stretch text to fill empty space. - Keep dark background #101013 with light text #F5F3F7; light background #F5F3F7 with dark text #17111F. Preserve the template's lavender, lime and peach accents. Light text on light accents is not acceptable. - Use one dominant accent per slide unless the content needs distinct categories. Maintain strong contrast; aim for at least 4.5:1 for normal text and 3:1 for large text. Never encode a distinction by color alone. - No unintended overlaps, clipped text, objects outside the canvas or captions covering important image content. Decorative layering is allowed only when intentional and every element remains legible. - Use images that explain the message. Preserve aspect ratios, choose a deliberate crop and keep subjects visible. Use owned, licensed or explicitly supplied assets. Avoid decorative stock imagery when plain text is clearer. - Keep tables simple, with clear headers, adequate cell padding and readable row contrast. Split wide or dense tables. Show units, labels and sources where needed. ## Preserve trustworthy, editable content - Never invent statistics, quotations, credentials, sources or project results. Mark illustrative data as examples. Attach concise sources to factual claims and keep fuller references in notes when appropriate. - Charts need meaningful labels, units, honest scales and legible values. Prefer native charts with accessible source data. Avoid 3D effects, unnecessary legends and visual decoration that distorts comparison. - Use native automatic slide numbers, not typed literals. Check numbering after duplication or reordering. Do not put layout names in footers. Use a shared presentation-title footer only when requested and centrally editable in the chosen tool. - Use real lists, logical object reading order and useful image alt text where supported. Keep visible text editable instead of baking it into graphics. - Google Slides may render native charts differently from PowerPoint. Preserve editability unless the user explicitly prioritizes exact appearance. Explain material differences; never claim pixel equivalence without verifying it. - A Google presentation copy does not automatically copy its linked spreadsheet. Provide a copyable data source and explain how to insert charts from the user's copied sheet. Do not grant edit access to the original template or data source. ## Required review before delivery 1. Render or export the final deck from the target application. Inspect every slide at presentation size. A contact sheet alone is insufficient. 2. Check contrast, font substitution, line breaks, margins, visual balance, image crops, list indentation, chart labels, table padding, slide order and numbering. Confirm no unintended overlaps or clipped content. 3. Check readability at the expected viewing size. If a slide needs zooming to understand its main content, simplify it or split it. 4. Verify editability by inspecting native objects and chart data. When delivering both PPTX and Google Slides, inspect both outputs independently, especially charts, tables and text-heavy slides. 5. Fix defects, render the changed slides again and repeat the relevant checks. Reopen the exact final file, verify its slide count and test the actual download or copy links. 6. Deliver the presentation, required fonts or data links, and a brief statement of what was checked and any remaining limitation. If rendering or target-application access was unavailable, state that visual verification is incomplete; do not label the deck fully verified. Creating a deck does not itself authorize publication, sending it to others or changing permissions. Use the destinations and sharing scope explicitly authorized by the user.