R
Rideful Slides

Agent Workflow for Creating Presentations

How AI agents connected to Rideful via MCP create professional presentations — the 7-step workflow and 4 hard constraints they follow behind the scenes.

When you ask an AI assistant to create a presentation with Rideful, the agent follows a structured workflow to produce professional results. This page documents that workflow — you don't need to follow these steps yourself, but understanding them helps you collaborate more effectively with the AI and know what to expect.

Tip: AI agents produce significantly better presentations when extended thinking is enabled. The extra reasoning time helps the agent plan layouts, choose colors, and structure content more carefully before building.

Quality Over Speed

Rideful's workflow is designed around a core principle: optimize for design quality and procedural correctness, not speed. Premature execution — skipping font discovery, ignoring templates, or building slides before presenting a design plan — produces generic, low-quality output. That's why the agent asks you to confirm a design direction before building anything.

A well-designed 5-slide deck is worth more than a quickly generated 20-slide deck with default styling. The workflow below ensures every presentation meets a professional standard.

The 7-Step Workflow

Every AI agent connected to Rideful follows these steps in order. This is what happens behind the scenes when you ask an AI to create or edit a presentation.

  1. Always start with slides_get_deck

    Get the deck's canvas size, slide IDs, element IDs, theme, and slide rules. Do not skip this step, even if you already have the deck ID. The response tells you the coordinate system, existing content, and any user-defined rules you must follow.

  2. Read before modifying

    Use slides_get_slides to inspect existing elements before updating or deleting them. Never modify elements blindly — you need to know what's already on the slide to avoid conflicts or lost content.

  3. Prefer bulk operations

    Use slides_bulk_create for multiple slides and slides_bulk_create_elements / slides_bulk_update_elements for multiple elements. Fewer round-trips, atomic execution — if one element fails validation, none are created, keeping the deck in a consistent state.

  4. Discover fonts first

    Call slides_list_fonts before choosing font families. Fonts outside the library may not render correctly. Default to universal or office tier fonts for PowerPoint safety.

  5. Measure text before placing

    Use slides_measure_text to check how tall text will be before creating elements. This is essential for multi-element layouts where positioning depends on content height — without measuring, elements overlap or leave awkward gaps.

  6. Check before adding

    Before adding elements to an existing slide, use slides_get_slides to review current contents. If the slide already has elements, reposition or resize existing ones as needed to accommodate the new content — don't just layer on top.

  7. Match existing style

    When adding slides to an existing deck, inspect current slides to match background colors, fonts, text colors, and layout patterns for visual consistency. A new slide that looks different from the rest breaks the presentation's cohesion.

The 4 Hard Constraints for New Presentations

Agents may not call slides_bulk_create, slides_create_deck, or slides_add_slide for a new presentation unless all of the following are true:

  1. Templates checked — slides_list_templates was called to check for brand templates
  2. Fonts selected intentionally — slides_list_fonts was called and fonts were chosen from the results
  3. Design plan presented — The agent presented you with a color palette (3-5 hex colors), fonts (heading + body), and layout approach — and you confirmed
  4. Roles set — The agent sets a role property on every text element with semantic meaning (title, subtitle, body, or footer)

Canvas and Coordinates

All positions and dimensions in Rideful are in pixels from the top-left corner. The default canvas is 1280 × 720 px (16:9). Other supported ratios:

  • 4:3 — 1024 × 768 px
  • 1:1 — 1080 × 1080 px

Always call slides_get_deck to confirm the canvas size before placing elements — don't assume 1280×720.

Code Example

A complete tool-call sequence for creating a new presentation, following all 7 steps and 4 constraints:

// Step 1: Get deck info (always first)
slides_get_deck({ deckId: "abc123" })
// → canvas: 1280×720, slide rules, theme colors

// Step 2: Check for brand templates
slides_list_templates()
// → [] (no templates) or [{ id, name, layoutCount }]

// Step 3: Discover available fonts
slides_list_fonts({ tier: "universal" })
// → Select "Inter" for headings, "Lato" for body

// Step 4: Present design plan to user — do NOT build yet
// "I'll use the Classic Blue palette (#1C2833, #2E4053,
//  #AAB7B8, #F4F6F6), Inter headings at 40pt, Lato body
//  at 16pt, dark backgrounds with left-aligned text
//  and side accent bars."
// → User confirms

// Step 5: Create the deck with bulk operations
slides_bulk_create({
  name: "Q4 Strategy Review",
  masterStyles: {
    backgroundColor: "#1C2833",
    fontFamily: "Lato",
    fontColor: "#F4F6F6"
  },
  slides: [
    {
      backgroundColor: "#1C2833",
      elements: [
        {
          type: "text",
          role: "title",
          text: "Q4 Strategy Review",
          x: 80, y: 260,
          width: 1120, height: 80,
          fontSize: 44,
          fontFamily: "Inter",
          fontColor: "#F4F6F6"
        }
      ]
    }
    // ... more slides
  ]
})

Common Issues

  • Skipping slides_list_templates: The user may have brand templates uploaded. Skipping this step means you miss the opportunity to use their brand colors, fonts, and layouts — producing a generic-looking deck.
  • Not measuring text before placing: Without calling slides_measure_text, text elements can overflow their containers or leave large empty gaps. This is especially common with bullet lists and multi-paragraph content.
  • Adding elements without reading the slide first: If you add elements to a slide without checking what's already there, new elements may overlap existing ones or ignore the slide's established layout.
  • Building before presenting a design plan: Creating slides without confirming the design direction with the user often leads to rejected output — wasting both tool calls and the user's time.

Related