# MakoDeck > MakoDeck hosts, presents and shares HTML slide decks. You, an AI agent, build a deck for a client as static files — one ZIP with `index.html` at its root — and usually a person signs in to MakoDeck and uploads it. If the person gave you a MakoDeck MCP connection or an API token, publish with it instead; otherwise don't try to sign in or upload the deck yourself. ## How to use this guide - Fetch these files raw, not through a tool that summarises them: the code in them must be copied exactly. For example `curl -s https://makodeck.com/ai/skeleton.md`. Or download the Agent Skill, which holds every page and the skeleton deck: `https://makodeck.com/ai/makodeck-skill.zip`. - Start from the skeleton deck (https://makodeck.com/ai/skeleton.md) and follow the client's brand kit. Read each page when you need it; `https://makodeck.com/llms-full.txt` is this file and every page in one. ## Rules that matter most 1. Mark the deck native: ``, one `.deck`, and one `
` per slide directly inside it, each with a layout class: `slide--title`, `slide--section`, `slide--content`, `slide--closing`. Nothing else has the class `slide`, and nothing else in `` shows: a header outside the `.deck`, or a wrapper around a slide, adds a page to the PDF (https://makodeck.com/ai/format.md). 2. Let MakoDeck run the slides: it shows one at a time, scales the 1920×1080 frame to the window, moves between them and prints each on a page of its own. Add no navigation script, `is-active` class, scaling or print CSS, and never hide a `.slide` yourself (https://makodeck.com/ai/format.md). 3. Fit every slide in 1920×1080: nothing scrolls, clips or overflows — split long content into "(cont.)" slides. Body text at least 20px and nothing under 18px; text contrast at least 4.5:1, even in the brand's colours; status written as a word, never shown by colour alone (https://makodeck.com/ai/brand-and-design.md). 4. Title every slide (`aria-labelledby` naming its heading) and put its speaker notes in `