Which parts can I edit?

Change words, pictures, order, colors, layouts and notes in the browser editor, then Save. Presets guide the initial accent; there is no per-style theme chooser. PPTX keeps native text/notes and separate pictures, while backgrounds and complex art/charts are rendered. Check the export and recipient fonts, and use PDF for a separately inspected fixed-page copy.

Do I need a separate image-generation account?

No generation is needed for suitable supplied pictures or the eight bundled catalog photos. Optional built-in image generation uses the host account’s availability/limits with no separate key. The current package also permits its FAL helper with FAL_KEY and separate provider charges. Library downloads may need internet while building, but the finished embedded HTML is offline. Do not repeat a photo across pages.

Are the people and figures in the reference real?

No. The example context and people are fictional, and illustrative figures are not verified results. Use approved names, roles, dates, metrics and permitted photos for a real team, or retain clear fictional/illustrative identification. The installed generic schema fixture should not be described as the completed ten-page case.

Violet Editorial Team Deck

Previews from the publisher

Introduce a team through what each person owns, how work moves and which shared habits matter. Violet Editorial Team Deck uses grayscale editorial portraits, oversized uppercase headings and a restrained accent tile on light paper and selected black pages. Its ten layout archetypes guide the story; fictional people and illustrative figures must be replaced or clearly distinguished from your real team and evidence.

What you get

Ten adaptable archetypes: team-photo cover, three-chapter contents, panoramic overview, featured lead, three-person roster, person/responsibility split, three process cards, bar-chart/data page, working habits and contact close. Use the requested length; split larger rosters across pages instead of shrinking portraits. The installed schema example is generic, not a finished ten-page team case.
An editorial system with embedded Schibsted Grotesk uppercase headings and Inter body type, grayscale studio portraits, square photo/card corners and accent arrow tiles. Violet Editorial is the default; Cobalt, Forest and Brick are coordinated generation-time accent alternatives. Dark pages are reserved for contents, team and data; the shared editor itself has no theme picker.
Detailed composition limits: a 12-column grid with 77 px margins and 26 px gutters, content between 86 and 634 px on the 1280×720 canvas, at most three content blocks and substantial empty space. Headlines stay within seven words (cover five), supporting lines within eighteen, and each page within forty-five words excluding numbers; longer bios/context go into speaker notes.
Eight bundled monochrome catalog photos cover a group, working session and individual portraits. Build with permitted supplied material or relevant fictional imagery; never relabel a generated portrait as an actual colleague. Photos do not overlap; the white name/contact card inside a photograph appears on at most two pages. Limit each page to one accent element and avoid extra tags, date pills or folios.
A standalone offline HTML presentation with viewing, overview/thumbnails, notes, editing, presentation mode and print styling. Requested PPTX keeps native text/notes and separate pictures; complex art, backgrounds and rendered charts/decoration remain images. Print/PDF gives one 16:9 page per slide. Recipe/reference/build tools are installed resources, while your finished deck is created from the approved brief.

Before you choose

Read the deck as a new colleague would: can they identify who owns a decision, how to work with that person and what to do next? Preserve the sparse pages by moving context into useful speaker notes, not deleting it. Portrait style and confident bars should never replace verified identities or evidence.

Good fit

Onboarding or a small-team introduction where readers need names, responsibilities and a shared way of working.
A studio or service-team profile that can explain ownership, collaboration, process and contact in concise pages.
A team with accurate figures/dates and permission to use its supplied portraits, plus time to review the story and exported pages.

Not for

Using another team’s names or portraits, or representing fictional generated people as real staff.
Dense investor financial modeling or long biographies squeezed into forty-five-word slides.
Unverified client outcomes or illustrative chart values presented as measured business evidence.

How to use

You say/lavender-editorial-team-deck Make a ten-slide introduction for Shared Practice, a fictional four-role service studio.

Provide topic/outline, audience, the action or decision the deck should support, approximate length, people and roles, accurate figures/dates and permitted photographs. Agree the actual count from content/duration. State assumptions when details are missing. Copy defaults to English unless another content language is requested; keep communication/interface language separate.
Choose the accent preset and plan a sequence from team context to ownership, working process, habits and next action. Select/extend the ten archetypes; three people is the maximum on one roster page. Keep illustrative chart values explicitly identified and replace them with approved evidence. Put biographies and context in notes rather than dense page paragraphs.
Apply the grid and word budgets consistently: title ≤7 words (cover ≤5), one supporting line ≤18, at most three short items and ≤45 total words excluding numbers. Keep cards aligned, square-cornered and stylistically consistent, with one accent element. Use no overlapping photos or extra page labels/footers; use the in-photo signature card at most twice and restrict black pages to contents/team/data.
Choose supplied images first, then library reuse, generation for gaps or all-new imagery. The eight local photos can be embedded without an image-generation charge. Catalog reuse is the fallback; use each pictorial source on one page only, allowing the roster’s distinct portraits but no repeated photo. Generated reference inputs follow the package restrictions. New pictures can use built-in generation with account limits/no key or optional FAL/FAL_KEY with separate charges; submit paid tasks once and then check/fetch.
Compose from the recipes, replacing copy, portraits, alt text, roles, chart values and contacts and removing leftover example nodes. Python 3 handles compose/build/static checks; optional media helpers use Node. Resolve unfilled-image/example reports, preserve embedded fonts, inline all resources and keep below 20 MB. Library download may require internet during building; the completed HTML should make no network requests.
Inspect every 1280×720 page over local HTTP for hierarchy, word limits, grid/portrait crops, names/roles, chart labels, contrast and notes. Check any claimed outcome against sources. Test text/image/order/layout/color changes, notes, undo/redo, Save/reopen and presentation mode. Static checks cannot prove correct identities, permissions, source facts or visual fit.
Deliver in page view with Edit/E and Save (Cmd/Ctrl+S) instructions; browser recovery is local and Save writes portable edits. Use framework CJK/RTL support as needed. Export/check/inspect PPTX in the recipient application or PDF via print before sharing. The embedded export menu does not require the retired mandatory Node/Chromium chain; font availability can still alter wrapping.

Requirements and costs

You bring: Your topic or outline, audience, and intended decision. · The approximate page count and source figures that must be accurate. · Any permitted photographs or artwork you want included.
Dependencies: Modern browser — required for presentation and browser editing · Built-in image generation in your agent (GPT Image class) — only needed to create new pictures; no separate API key · Chrome, Chromium or Edge plus Node.js 20 or newer — required only for PowerPoint export · Internet access — optional, to download this Skill's picture library while building a deck
Outside costs: Decks can reuse this Skill's own picture library at no image cost: you choose up front whether to reuse it or generate every picture new. New pictures use your agent's built-in image generation tool (GPT Image class) with no separate API key, and availability follows your agent account.
Publisher testing: v1.0.3 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT