Update to Beautiful.ai

{
  "description": "Which Beautiful.ai slide template fits which content, what each template's model looks like and how to switch a slide to another template. Use when choosing a template for new or restructured content, when the user asks for a different layout, or when a slide's content does not fit its template.",
  "included_files": [],
  "name": "beautiful-ai-slide-templates",
  "skill_md_contents": "---\nname: beautiful-ai-slide-templates\ndescription: Which Beautiful.ai slide template fits which content, what each template's model looks like and how to switch a slide to another template. Use when choosing a template for new or restructured content, when the user asks for a different layout, or when a slide's content does not fit its template.\n---\n\n# Beautiful.ai slide templates\n\nA slide's `template_id` picks the template that renders it; each template is rendered by one root element whose model is `states[0].primary` (the element reference is in the slide-elements skill, `beautiful-ai://skills/slide-elements`). `list_slide_templates` lists the templates with their description, category and tags, and gives one template's `defaultData` (what an empty slide of it starts with) and capabilities; `get_slide_examples` gives complete, real slide models of a template.\n\n## Which template to pick\n\nWhere several templates are listed, the first is the one the app prefers, the rest are alternatives for when the first does not fit, the user asks for that look, or the deck already leans on the first: a template should not run three or more slides in a row or carry more than about a third of a deck (see \"Varied across the deck\" in the slide design skill), so when a slide's content points to a template the deck already uses that much, take the next one of its list or restructure the content for another entry below. The item counts are the ones the app's own slide builder keeps to so the slide stays readable; the element documents (slide-elements skill) give each element's hard limit (`maxItemCount`), which is sometimes higher but makes the slide crowded or report as not fitting. Above the count, shorten the content or pick the next template.\n\n- Presentation title with optional subtitle, presenter names, company logo: `title`.\n- A single headline, mission statement or slogan; a section break; a quote with an author; a one-person biography with a photo; free-form paragraphs or a key concept that is not a list (optionally with an image): `headline2`; a plain section divider: `section`.\n- A list of text items or bullet points: `textlist` for bullets, numbered lists and checklists (up to 6 items in 2 columns, or 1 column next to a side image tray when there are at most 4; above 6 items 3 columns and no image), `textgrid_vertical_icons` for an icon list (max 6), `textBoxGrid` for text boxes / cards / columns (max 8, one row up to 4). A before/after comparison is `textlist` with two column headers, or `textBoxGrid`. Free-form text that is not a list: `text`; a long biography: `long_bio`.\n- Agenda or meeting schedule: `agenda`.\n- Statistics, factoids, metrics, KPIs: `dashboard` with `Statistic`, `RadialBar`, `Chart` or text (`TextAndImage`) cells (max 8 cells); a few big numbers with change indicators: `big-numbers`; one single big number: `action-number`.\n- Line, column, bar or area chart of trends: `dashboard` with a single `Chart` item (the `chart_line`, `chart_column`, `chart_bar`, `chart_area` templates are that preset); waterfall / bridge chart: `chart_waterfall`; pie chart: `dashboard` with a `PieChart` item (one series, max 8 slices; `chart_pie` is that preset). Charts are cells of a `dashboard`, so a chart can share the slide with other cells.\n- Comparing two or more numeric values: `compare_vertical_bars`, `compare_horizontal_bars` (up to 7 bars), `dashboard` with a `PieChart`; `compare_circles` and `compare_radial_bars` look best with at most 4 items; `compare_vertical_pictograph` (max 4) for icon-based comparison; `radial_bar_chart` (max 8) when a radial look is requested; `arrow_bars` for values shown as arrows; `slicechart` (max 8) for a value split into slices; `visual_percentage` for percentages as filled pictograms.\n- Side-by-side comparison of up to 4 non-numeric items, plans or options, and pillars / principles / core values: `stackDiagram`.\n- A table or pricing table: `dashboard` with a `Table` item (`table-v2` is that preset); a heatmap or color-coded grid: the same `Table` with a cell color per value.\n- Linear process or sequence of 2–10 steps: `step_chevrons` (or `step_boxes`). Circular, looping process: `cycle_diagram` (max 6) or `step_circular`. Central concept with items radiating outward: `hub_and_spoke`. Flowchart with decisions and branches, or any diagram of freely placed nodes joined by connectors (a system or data flow, a decision tree, boxes with arrows between them): `flow_chart` (the node diagram: boxes, circles, diamonds, text and icon nodes you position yourself, with labeled connectors). Sources feeding into one target: `connection_diagram`.\n- Ordered sequence shown as connected shapes (2–10 items): `sequence`, `gears`, `puzzle`.\n- Pyramid, funnel, hierarchy or filtering progression: `pyramid`, `funnel`; slope / ramp / wedge across 3–10 ordered stages: `horizontal-funnel`.\n- Timeline of events: `timeline`, `journey`. Monthly or weekly calendar of dated events: `calendar-month`, `calendar-week`. A countdown to a date: `countdown`; a timer for a break or exercise: `timer`.\n- Tasks, project plans, sprints: `gantt_chart` when tasks have dates, `kanban` when they have statuses or lanes, `horizontal-task-list` otherwise.\n- SWOT analysis: `swot_diagram`. Items plotted against two dimensions (effort vs impact, priority matrix): `xygraph`. Overlapping sets (2–4 circles): `vennDiagram`. Concentric rings / layered priorities: `target`. Org chart, reporting lines: `orgchart`. Countries or regions on a map: `world_map`.\n- Team members with names, titles and photos: `team`. A customer quote with the person's photo: `user_testimonial`. A wall of logos (max 12): `logogrid`. Contact information (address, phone, email, socials, optional map): `contactus`. Several photos with captions: `textgrid_photos`; a photo carousel: `textgrid_carousel`; photos only: `collage` (or a single full-bleed `image`). Word cloud of weighted terms: `wordCloud`. Product screenshot in a device mockup with bullet points: `product_laptop`. An embedded video: `video`; an embedded web page: `web-view`. An ROI / savings calculator: `roi_calculator`.\n- Free-form layout: `authoring` (called \"Classic\" in the app) is a blank canvas of shapes, text boxes, images, icons and lines you position pixel by pixel. Use it only for complex slides that need a lot of custom layouting and that no other template can express (an architecture diagram with many parts, a custom infographic, a layout the user sketched); everything else is better served by a smart template, which lays itself out and adapts to the content. When you do use it, expect to iterate on positions and sizes with the render until it looks right.\n\n## Dashboards\n\nA `dashboard` is a grid of cells: `primary.gridLayout` (`cols: 12, rows: 12`, one `{ x, y, width, height }` per cell) and `primary.items` with one item per cell, matched by position in the two arrays. Each item has a `componentType` of `Chart`, `PieChart`, `Statistic`, `RadialBar`, `RadialBarChart`, `Table` or `TextAndImage`, a `cellColor`, and the cell's content in `childElement`. A dashboard can hold several cells at once, which is often the nicest answer when the user asks to add a number, a takeaway, a second chart or an image next to a chart: a full-width chart with two text cells under it, a chart beside a column of statistics, a pie chart with its key figure next to it. Keep it to a few cells (the app never builds more than 8) so each stays readable, and when adding a cell add both the grid cell and the item (and shrink the neighbors to make room). The `dashboard` examples show many such combinations; the element reference has the exact model (`Dashboard.md`, `LayoutContainerItem.md`, `Chart.md`, `PieChart.md`, `Statistic.md`, `Table.md`, `TextAndImage.md`).\n\n## Switching templates\n\nSwitch a slide to another template when the user asks for it (\"turn this into a bar chart\", \"make this a timeline\"), when the request clearly cannot be fulfilled with the current template, or when splitting or combining slides (each resulting slide gets the template that presents its content best).\n\n- To switch: set `template_id` to the new template and rebuild `states[0]` for it, carrying over the user's content (title, text, numbers, images) where it fits. The element reference (the root element's document in the slide-elements skill) says what each field means and what is required; for the shape and style to copy, prefer a slide of that template already in this deck (it fits the theme and the deck's style), then a real example (`get_slide_examples`), then the template's `defaultData` (`list_slide_templates`).\n- Keep `layout` fields the new template supports (header position, tray) and drop the ones it does not (check its capabilities: `allowHeader`, `availableTrayLayouts`, `allowColorBackgrounds`).\n- Render before saving, as for any change, and mention the template switch to the user.\n"
}