# Pulso festival partnership deck > A festival partnership proposal with a geometric cover, audience and demographic charts, a riverfront stage map, a color-coded schedule and three sponsorship tiers. An open-slide demo deck; its commits credit Claude Opus 5.5. - Kind: Slides - Live deck: https://demo.open-slide.dev/s/pulso-festival-partners - Page: https://meetreference.com/v/bauhaus-colour-block-festival-proposal/ - Ready-to-use agent handoff: https://meetreference.com/v/bauhaus-colour-block-festival-proposal/agent.txt - Authorship: AI-made, per the source - Made with: Not stated - Model: Claude Opus 5.5 - Built with: open-slide, React - Style: Decks; bauhaus, primary colors, geometric, poster typography, paper grain, data visualization, editorial - Slides: 9 - Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions. - Shared by 1weiho (Yiwei Ho) in GitHub, Oct 12, 2026: https://github.com/open-slide/open-slide/tree/main/apps/demo/slides/pulso-festival-partners - 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. Requirements reported by the source: open-slide (npx @open-slide/cli init); Coding agent (the repo names Claude Code, Codex, Cursor). ## 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. Build a shared geometric vocabulary that works as both decoration and information: circles for growth, semicircles for stage capacities and rectangular bands for scheduling and pricing. Alternate cream information slides with saturated chapter pages, retaining consistent margins, tracked labels and oversized wide headlines. For a new subject, replace the festival content, map and metrics with relevant equivalents while preserving color assignments across related diagrams; keep decorative shapes clear of essential numbers. 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 captured walkthrough frames, not by the creator. A bold Bauhaus-inspired festival proposal using geometric color blocks, oversized numerals and clear infographic elements. - Color: Cobalt blue, bright red, yellow, warm cream and black, with occasional pale gray and pink accents. - Type: Heavy geometric sans-serif, mostly uppercase, paired with compact labels and small supporting text. - Framing: Strong grid alignment and high contrast; large circles and numerals anchor the layouts, balanced by charts, tables and concise text. - Structure: A sequence of proposal pages moves from festival identity and headline metrics through audience data, event branding, venue planning and schedules to pricing and partnership options. Storyboard of the slides: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/storyboard.webp - Slide 1: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f1.webp - Slide 2: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f2.webp - Slide 3: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f3.webp - Slide 4: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f4.webp - Slide 5: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f5.webp - Slide 6: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f6.webp - Slide 7: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f7.webp - Slide 8: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f8.webp - Slide 9: https://meetreference.com/media/bauhaus-colour-block-festival-proposal/f9.webp ## How it was made, per the creator - Notes: Showcase deck added to the open-slide demo in PR #554 (https://github.com/open-slide/open-slide/pull/554); commits carry a Claude Opus 5.5 co-author trailer. No prompt published. ## Links - View deck: https://demo.open-slide.dev/s/pulso-festival-partners - Original post: https://github.com/open-slide/open-slide/tree/main/apps/demo/slides/pulso-festival-partners