Violet Editorial Team Deck
A team deck that reads like your own magazine.
Turns your AI into a presentation designer — builds a team deck for an editorial or publishing team on a violet-ink magazine system: a masthead opener, serif headlines, one contributor per spread, and plain-spoken proof of what the team edits and ships.
Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Buy the skill ($4.99), download the ZIP from your checkout confirmation, unzip it into the directory shown above, restart your AI session — same result. Already bought it? Your AI assistant can download it for you.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Violet Editorial Team Deck
When to use
- An editorial, publishing, or content team needs a deck that introduces the people behind the publication — editors, writers, designers, fact-checkers — to readers, partners, advertisers, or new hires
- A magazine, newsletter, or media brand wants a team deck that feels like its own pages: masthead, bylines, beats, and voice, not a generic corporate org chart
- A team page, press kit, or partnership pitch needs a deck version that a stranger can read in five minutes and come away knowing who edits what
- An editorial team is hiring or fundraising and needs to show the bench: who covers which beat, who holds which standard, who to contact
- The existing team deck is a wall of headshots and job titles that says nothing about what anyone actually edits or believes
Workflow
- Set the masthead and the promise (input: the publication → output: a masthead opener + one promise line)
Open the deck like a magazine cover, not a corporate title slide: the publication's name set as a masthead, one promise line stating what the team edits for and whom ("Sharp reporting on the city, for the people who live in it"), and one issue-style line (date, edition, or season) to give it a moment in time. The promise line is the deck's thesis — every contributor spread that follows should be readable as evidence for it. If the team cannot agree on one promise line, the deck is not ready to build; a team deck without a shared promise is just a directory. - Map the beats before the bios (input: the team's coverage → output: a beat map)
List the beats the team actually covers — city hall, food, culture, investigations, photo, design — and assign one owner per beat before writing a single bio. Each beat gets one line: what it covers, what it refuses to cover, and the standard it holds ("City hall: every claim traced to a document, no anonymous sourcing on spending"). The beat map becomes the deck's spine: contributor spreads follow beat order, not seniority, so a reader can find the person who edits the thing they care about. A beat with no owner is a gap to name honestly, not to hide — "Culture is covered by rotation; we are hiring a dedicated editor."
Template preview
Violet Editorial Team Deck — Outline Template
One deck = one team, one promise. Fill this in before building slides.
Publication: {name}
Promise line: {what the team edits for, and for whom} Issue line: {date / edition / season} Audience for this deck: {readers / partners / advertisers / candidates / new hires} Ask: {subscribe / pitch us / book / apply}
Beat map
Contributor spreads (one per person)
{Name} — {Role} — {Beat}
Portrait/avatar: {file or note} Paragraph (in their editorial voice): {what they edit and how they edit it} Proof (checkable): {story shaped / standard set / correction owned} Contact: {name + address}
