publishing-build-content

name	publishing-build-content
description	Publishes blog and social content about the build, Google AI usage, and hackathon journey, and is used when the team wants bonus visibility after the core demo is stable.

Creates bonus-content assets that tell the build story clearly and give Diverge extra visibility.

Use this skill when

• The core demo is already stable.
• The team wants bonus points or extra exposure for building with Google AI.
• A blog post, launch thread, or social post must be drafted quickly.
• The PM wants a simple narrative that explains the project to a broad audience.

Capabilities

• Writes a blog post about the product and build journey.
• Highlights the use of Gemini, ADK, Cloud Run, and Cloud Storage.
• Frames the project around emotional storytelling, not just technical novelty.
• Drafts social copy for LinkedIn, X, or Devpost updates.
• Includes the hashtag #GeminiLiveAgentChallenge.
• Reuses existing assets like architecture diagrams and screenshots.

Workflow

1. Only do this after the demo is stable. Bonus content should never steal time from the core submission.
2. Collect proof points.
   • screenshots
   • architecture diagram
   • short demo clip
   • key build decisions
3. Write the blog narrative.
   • what Diverge is
   • why emotional intake matters
   • why multi-agent architecture was chosen
   • how multimodal storytelling works
   • what graceful degradation made possible
   • what was learned in the hackathon
4. Write short social versions.
5. Include challenge and Google AI references clearly.
6. Publish and link back to the repo or demo.

Suggested blog outline

• Title
• The idea behind Diverge
• Why storytelling quality mattered more than feature count
• The 8-agent architecture
• How Gemini + ADK were used
• Frontend motion-comic design choices
• What graceful degradation meant in practice
• Lessons learned from building fast
• What comes next

Example social post

We built Diverge for the #GeminiLiveAgentChallenge: an AI storytelling experience that starts by understanding how you feel, then turns that into a motion-comic narrative with meaningful moral choices. Powered by Gemini, Google ADK, FastAPI, React, Cloud Run, and Cloud Storage.

Guardrails

• Do not overstate what the MVP does.
• Keep the story-first positioning front and center.
• Avoid writing technical jargon for a general audience unless it adds clarity.

Project references

• AGENTS.md — product positioning, stack, user context, graceful degradation, MVP focus.
• docs/PRD.md — vision, emotional-intake premise, multimodal storytelling approach.
• docs/roadmap.md — helps frame MVP vs future vision in the write-up.