create-carousel10.4 KB
View saved version →
---
name: create-carousel
description: "Create, revise, preview, and export editable .carousel projects for ACE: Aesthetic Carousel Editor from a brief, slide copy, and optional photographs. Use for native carousel projects or templates."
---
Deliver a downloadable `.carousel` project that can be imported and edited in ACE: Aesthetic Carousel Editor. Text, shapes, photo slots, and supported built-in artwork remain editable. Preserve the user's language, supplied copy unless revision is requested, slide count, and visual direction. If the ratio is unspecified, use portrait 4:5. Choose the sequence from the material: a photo essay can work through changing viewpoints without a dramatic story or a closing slogan.
## Writing and editorial choices
When writing or revising copy, read [the writing guide](references/WRITING_GUIDE.md), also available through `get_carousel_spec(section: "writing")`. Build the angle from supplied facts, observable details and the user's voice before fitting text into a layout. Distinguish observations from unknown context; do not invent experiences, quotes, chronology or feelings to make a post sound personal.
Compare a few materially different angles privately, then choose one suited to the brief. Check whether its headline and supporting lines could be pasted unchanged onto an unrelated subject; if so, make the observation more specific or remove unnecessary text. Each slide should contribute a detail, event, evidence or change of view. Do not default to poetic advertising, repeated aphorisms, suspense hooks or a mandatory CTA. Short literal captions and photo-only slides are valid. Preserve requested slogans and deliberate campaign styles.
Use available earlier drafts to avoid recycling their titles and narrative pattern; there is no automatic memory of other chats or Instagram posts, and no guarantee of unique wording. Examples demonstrate layout, not a stock library of headlines. Keep editorial notes and alternatives outside the exported YAML and final slides.
## Composition and resources
Start with a short working plan: visual idea, type hierarchy, photo treatment, and role of each slide. Keep it outside the native YAML. Read [the design decision guide](references/DESIGN_GUIDE.md) to choose between a frame, photo grid, simple border, and intentionally separate layers. Preserve the user's design direction; do not add elements solely to increase DSL coverage.
With MCP, read `get_carousel_spec(section: "overview")` for the server's capabilities, then `rules` for the contract. Search `catalogs` with category `frames`, `grids`, `fonts`, `stickers`, or `shapes` and a relevant query. Each result includes exact identifiers, constraints, and a complete native example. Follow `next_offset` for another page. `examples` provides complete compositions: photo-story, contact-gallery, type-led, free-collage, smart-stamp, and effects-study.
For local access, run `node <plugin-root>/scripts/get-spec.mjs overview` or `node <plugin-root>/scripts/get-spec.mjs catalogs quad grids`; the arguments are section, query, then category. The canonical catalog is `data/catalog.json`; the Markdown catalog is generated from it. If an older installed server rejects the new sections, use its `rules` and full `catalogs` response, and report that the upgraded discovery/diagnostics are not deployed there.
Use native frame presets for matching decorative photo treatments and native grids for aligned photo galleries. Grid recipes expand to `cells` and optional `swap`; `grid.preset` is not a DSL field. A grid contains photos, not text or arbitrary layers. White/dark photo outlines can use `image.border`; geometric outlines can use `shape.stroke`. A shape behind a photo remains appropriate for custom color, shadow, or independently positioned decoration.
For several requested styles, vary composition, typography, photo scale/crop and density in addition to palette. Do not reuse one fixed geometry for every style unless the user
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
