---
name: aaif-luma-description
description: Write the Luma event-page description for an AAIF in-person meetup. Use when asked to draft the Luma description / event page copy for an AAIF event.
argument-hint: [event title / paste tracker entry]
---

# AAIF Luma Event Description

Goes on the Luma page — a little longer; include the agenda and who should come.
Sections: **short intro**, **"What we'll cover"**, **"Who should come"**, a simple
**agenda with times**. ~180 words. **End on a line about AAIF being vendor-neutral
and builder-first.**

**House voice:** share the practice, never sell the product. Specific over grand,
builder-to-builder. Signal, not numbers.

## Input (from the event tracker)
- Event : `[EVENT TITLE] ([SERIES]) — [THEME]`
- When : `[DATE & TIME]`   Where: `[VENUE / CITY]`
- Speaker : `[SPEAKER + TALK]`   Demos: `[DEMO COUNT]`
- Agenda : `[RUN-OF-SHOW TIMES]`   For: `[WHO IT'S FOR]`

## Example (tested — match this format and voice)
Agentic AI Night:

> Agentic AI Night kicks off our Launch Series: one night on what it actually
> takes to run agents in production.
>
> **WHAT WE'LL COVER** — Maya Chen on tool calling at 10M requests a day, then
> three short community demos with Q&A.
>
> **WHO SHOULD COME** — engineers shipping agents, and anyone curious what breaks
> past the demo. (Mention prerequisites here.)
>
> **AGENDA** — 17:30 doors & networking | 18:00 why we're here | 18:05 talk one |
> 18:30 demos ×3 | 18:55 wrap | 19:00 social till late.
>
> AAIF events are vendor-neutral and builder-first: no paid slots, no pitches.
> Curated, RSVP-based — signal, not numbers.