# Playful bot meetup deck

> A Spanish bot-meetup deck: a purple event cover, an agenda, a colorful bot lineup, a three-step workflow, an anatomy diagram and a crowded illustrated closing screen. Made with Claude Sonnet 5.5 in Cursor.

- Kind: Slides
- Page: https://meetreference.com/v/playful-bot-character-event-deck/
- Ready-to-use agent handoff: https://meetreference.com/v/playful-bot-character-event-deck/agent.txt
- Authorship: AI-made, per the source
- Made with: Cursor
- Model: Claude Sonnet 5.5
- Built with: HTML and CSS
- Style: Decks; playful, mascot-led, oversized typography, dark mode, geometric illustration, sticker graphics, purple gradients
- Playback: a muted visual reference. The original soundtrack is available only at the source.
- Shared by @fildotai in X, Sep 30, 2026: https://x.com/fildotai/status/2105277984722554965
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this deck

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Create a small family of geometric characters with consistent eye marks and white outlines, then reuse them as oversized illustrations, row markers, and UI avatars. Alternate quiet dark information slides with light or purple statement slides, keeping headline alignment and margins consistent. Explain processes through simplified interface cards rather than bullet lists, and finish with a tightly cropped character collage. For a new subject, replace the bot roles, interface examples, and event details while retaining the visual rhythm; increase contrast on secondary labels.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the recording frames, not by the creator.

Playful Spanish-language presentation about bots, combining bold editorial typography, concise instructional content, and simple geometric bot characters.

- Color: Mostly near-black backgrounds with white text, accented by vivid teal, orange, purple, pink, and blue; occasional pale gray and bright blue or purple slides.
- Type: Large, clean sans-serif headlines with smaller restrained supporting text and compact labels.
- Framing: Strong headline-led layouts with generous negative space, modular cards and diagrams, and colorful bot shapes used as illustrations and visual anchors.
- Structure: The deck opens with event and access information, introduces an agenda and bot characters, explains bot-making and examples, presents bot anatomy and volunteer information, then closes with a build prompt and a character-filled end card.

Storyboard, nine frames spread across the recording: https://meetreference.com/media/playful-bot-character-event-deck/storyboard.webp

- Frame 1 at 4.3s: https://meetreference.com/media/playful-bot-character-event-deck/f1.webp
- Frame 2 at 12.9s: https://meetreference.com/media/playful-bot-character-event-deck/f2.webp
- Frame 3 at 21.4s: https://meetreference.com/media/playful-bot-character-event-deck/f3.webp
- Frame 4 at 30.0s: https://meetreference.com/media/playful-bot-character-event-deck/f4.webp
- Frame 5 at 38.6s: https://meetreference.com/media/playful-bot-character-event-deck/f5.webp
- Frame 6 at 47.2s: https://meetreference.com/media/playful-bot-character-event-deck/f6.webp
- Frame 7 at 55.8s: https://meetreference.com/media/playful-bot-character-event-deck/f7.webp
- Frame 8 at 64.3s: https://meetreference.com/media/playful-bot-character-event-deck/f8.webp
- Frame 9 at 72.9s: https://meetreference.com/media/playful-bot-character-event-deck/f9.webp

## How it was made, per the creator

- Notes: 'slides i made for the @grok @bot event yesterday. sonnet 5.5 in @cursor_ai'. 14-slide event deck (agenda, credits, how bots work, build session).

## Links

- Watch: https://x.com/fildotai/status/2105277984722554965
- Original post: https://x.com/fildotai/status/2105277984722554965