How zho-zho-zho/zho-nano-banana-creation works
This repository is not an application codebase; it is a documentation-and-curation repo centered on a single README.md. Architecturally, it functions as a public catalog of prompt recipes and example outputs for “Nano-Banana” image/video generation workflows.
Main subsystems
1. Content catalog
• The core of the repo is a numbered collection of 46 “original玩法” entries.
• Each entry follows the same pattern:
- an image or short media example,
- a prompt or prompt sequence,
- a link back to the author’s original post on X.
• The catalog is organized by use case rather than by implementation:
- character/style transformation,
- identity preservation,
- object replacement and composition,
- product visualization,
- architecture/model rendering,
- fashion/editorial generation,
- toy/package mockups,
- lighting/reference transfer,
- pose/expression transfer,
- multi-panel process generation,
- video-oriented workflows.
2. Deployment / companion-product section
• A separate section presents three external tools as the “three-piece set”:
- Nano Bananary / 香蕉超市
- BananaPod / 香蕉铺子
- BananaFlow / 香蕉工厂
• These are not implemented in this repository; they are outbound links to other repositories/products.
• Their purpose in the architecture is important: this repo is a showcase and entry point, while the actual interactive experiences live elsewhere.
3. Change log / maintenance metadata
• The changelog records repository evolution by date:
- project creation,
- addition of the standalone open-source app,
- completion of the 46-item prompt collection,
- addition of the three deployment options.
• This is the only lifecycle/operational metadata present.
4. Attribution and credit boundary
• The README explicitly credits Gemini 2.5 Flash Image as the base model.
• Some prompts are attributed to other creators or X posts.
• The repo also contains a strong attribution note and a request to cite sources, indicating that provenance is part of the repo’s “governance” layer.
External services and tools that materially affect the architecture
• Gemini 2.5 Flash Image is the central model referenced for image generation/editing.
• Veo 3 is referenced for video generation in several workflows.
• X/Twitter is used as the canonical publishing and sharing channel for the examples.
• GitHub serves only as the hosting layer for the documentation and media embeds.
Data flow
1. Source idea and prompt crafting
• The author designs a workflow idea, often starting from an image transformation concept.
2. Example capture
• Before/after images or short clips are produced using external generative models.
3. Documentation
• The prompt, example media, and explanatory notes are embedded into the README.
• Related X posts are linked for provenance and discussion.
4. Distribution
• Readers consume the README directly on GitHub.
• For hands-on use, they are directed to one of the three companion projects rather than this repo.
Important architectural boundaries
• No application runtime boundary exists here.
• No backend, database, API server, job queue, or frontend app is defined in this repository.
• All generation execution happens outside the repo, in model services and companion applications.
• This repo’s responsibility is limited to curation, presentation, and linkage.
• The repo is effectively a static knowledge base / prompt playbook, not an executable system.
How to draw the architecture accurately
• Put this repository in the center as a documentation layer.
• Show one inbound flow from the author’s prompt experiments and generated media into the README.
• Show one outbound flow from the README to:
- Gemini 2.5 Flash Image,
- Veo 3,
- the three companion repos/apps,
- X/Twitter posts.
• Do not depict internal services inside this repo; there are none beyond static markdown content.
Main entry points: README.md README
Components 21
Documentation
Static README-based catalog and metadata
- README · Single-file public catalog of prompt recipes and example outputs
README.md - Prompt recipes · Numbered collection of Nano-Banana workflow prompts
README.md - Example media · Before/after images and short clips shown with each recipe
README.md - Use cases · Catalog organized by transformation, product, fashion, pose, and video workflows
README.md - Character style · Style transfer and character transformation examples
README.md - Identity preserve · Identity-preserving edits and controlled transformations
README.md - Product visuals · Object replacement, packaging, and product mockups
README.md - Architecture · Building, model, and environment rendering examples
README.md - Fashion · Editorial, clothing, and styling generation examples
README.md - Pose transfer · Pose, expression, and multi-panel process workflows
README.md - Video flows · Short video-oriented generation workflows
README.md - Changelog · Date-based history of project milestones and additions
README.md
External services
Model services and publishing platforms used by the catalog
- Gemini 2.5 · Primary image generation and editing model referenced by the repo
- Veo 3 · Video generation model referenced in video workflows
- X posts · Canonical source posts linked for each example and prompt
- GitHub · Static hosting and rendering layer for the README catalog
- Source ideas · Upstream prompt experiments and generated media created by the author
Companion tools
Outbound companion products referenced as the hands-on path
- Nano Bananary · External companion tool in the three-piece set
- BananaPod · External companion tool in the three-piece set
- BananaFlow · External companion tool in the three-piece set
Governance
Attribution and provenance boundary
- Attribution · Credits, source links, and citation request
README.md
Connections 21
- Source ideas → Example media: generate · Author experiments produce the media and prompt material
- Source ideas → Prompt recipes: craft · Upstream ideas are distilled into reusable prompt recipes
- Example media → README: embed · Captured media is embedded into the documentation catalog
- Prompt recipes → README: publish · Prompt instructions are collected in the README
- README → Use cases: organize · The catalog is arranged by workflow family
- Use cases → Character style: includes · One major family of workflows
- Use cases → Identity preserve: includes · One major family of workflows
- Use cases → Product visuals: includes · One major family of workflows
- Use cases → Architecture: includes · One major family of workflows
- Use cases → Fashion: includes · One major family of workflows
- Use cases → Pose transfer: includes · One major family of workflows
- Use cases → Video flows: includes · One major family of workflows
- README → Gemini 2.5: references · Primary model used for image generation and editing
- README → Veo 3: references · Video workflows point to this external model
- README → X posts: links out · Each recipe is tied back to an original X post
- README → GitHub: hosts on · The repository is delivered as a static README on GitHub
- README → Nano Bananary: points to · One of the external companion tools for hands-on use
- README → BananaPod: points to · One of the external companion tools for hands-on use
- README → BananaFlow: points to · One of the external companion tools for hands-on use
- README → Changelog: records · README includes the repository evolution log
- README → Attribution: governs · README includes source credit and citation guidance