venue-activation-visualizer
Use when a user wants to visualize brand activations, event takeovers, sponsor placements, stage looks, booth concepts, or before/after venue mockups from real or supplied venue photos.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 13
- Forks
- 4
01 前言 Front Matter
- name
- venue-activation-visualizer
- description
- Use when a user wants to visualize brand activations, event takeovers, sponsor placements, stage looks, booth concepts, or before/after venue mockups from real or supplied venue photos.
02 资源文件 1
- 参考文档.hivemind-skill-source.json1.1 KB
03 SKILL.md 正文
Venue Activation Visualizer
Turn venue photos and brand constraints into reviewable activation concepts.
Inputs
- Venue name or supplied photos.
- Brand, sponsor, campaign, or event objective.
- Required surfaces: stage, booth, signage, lounge, entry, projection, merch, photo wall, or wayfinding.
- Output format: image prompts, generated before/after images, interactive page, or deck.
Workflow
- Gather venue evidence. Prefer user-supplied photos or rights-cleared venue media. If searching the web, cite what was used.
- Identify fixed constraints: sight lines, exits, accessibility paths, lighting, scale, and surfaces that should not be covered.
- Propose three activation levels: light-touch, standard, and hero takeover.
- For each concept, specify what changes and what must remain untouched.
- Generate or prompt before/after visuals while preserving the real architecture.
- Verify that logos, text, exits, and people are not distorted in a way that misrepresents feasibility.
- Package with a production checklist and unanswered venue-permission questions.
Capability Map
- Image generation/editing: use a discovered image tool that supports references or editing. Verify outputs.
- Web/page artifact: use frontend design guidance for comparison toggles.
- Delivery: send only with approval and receipt if shared externally.
Safety
- Do not claim venue approval or code compliance.
- Do not use private venue photos in external generators without approval.
- Mark dimensions and pricing as estimates unless measured and sourced.
Provenance
This is a HivemindOS-authored clean-room skill inspired by a public skill catalog. No unlicensed upstream text, JSON, or scripts are copied.
04 同仓库更多 Skills
tailscale-generation-skill-authoring
This skill should be used when the user asks to "create a Tailscale generation skill", "add a local generation skill", "document a generation endpoint", "add an image generation provider", "add a TTS provider", "add video generation", "add 3D generation", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.
localtts
This skill should be used when the user asks to "generate local TTS", "use local text to speech", "use remote TTS over Tailscale", "make speech audio", "add a TTS provider", "use Qwen3-TTS", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.
karpathy-guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
comfyui-image-generation
This skill should be used when the user asks to "generate images", "generate images with ComfyUI", "use local ComfyUI", "use remote ComfyUI", "use Z-Image", "add an image generation provider", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.