# Ameba blog brand guidelines

> A white-and-green brand guideline deck showing an illustrated cover, brand relationship diagram, vision and concept statements, three illustrated principles, logo variants, icon treatments, and photographic brand applications.

- Kind: Slides
- Live deck: https://speakerdeck.com/spindle/amebablog-brand-guidelines
- Page: https://meetreference.com/v/ameba-blog-brand-guidelines/
- Ready-to-use agent handoff: https://meetreference.com/v/ameba-blog-brand-guidelines/agent.txt
- Authorship: Not stated
- Made with: Not stated
- Model: not stated
- Built with: not stated
- Style: Decks; brand guidelines, minimal, green, line illustration, rounded typography, modular grid, photographic collage
- Slides: 33
- Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions.
- Shared by Ameba Spindle in Website, Jun 8, 2023: https://speakerdeck.com/spindle/amebablog-brand-guidelines
- 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.

Build rhythm by alternating oversized statement slides with compact diagrams and orderly asset grids, keeping section labels and page markers fixed. Use a limited accent palette across outlined characters, filled icons, and loose looping overlays on photographs to connect expressive imagery with practical system documentation. For a new subject, replace the mascot, characters, copy, and photographs while retaining the contrast between spacious presentation pages and denser comparison pages.

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.

Clean, friendly Japanese digital-brand identity built around a small green mascot and simple geometric graphics.

- Color: Primarily white with Ameba green accents, black or charcoal text, and occasional neutral gray; application examples add photographic colors.
- Type: Modern sans-serif typography, with bold Japanese headings and prominent Ameba wordmarks.
- Framing: Editorial guideline pages combine open white space, short text blocks, logos, diagrams, character illustrations, icon samples, and product imagery.
- Structure: A sequence of brand-guideline sections covers the brand concept and principles, mascot and logo usage, visual language and iconography, and examples of the identity in use.

Storyboard of the slides: https://meetreference.com/media/ameba-blog-brand-guidelines/storyboard.webp

- Slide 1: https://meetreference.com/media/ameba-blog-brand-guidelines/f1.webp
- Slide 5: https://meetreference.com/media/ameba-blog-brand-guidelines/f2.webp
- Slide 9: https://meetreference.com/media/ameba-blog-brand-guidelines/f3.webp
- Slide 13: https://meetreference.com/media/ameba-blog-brand-guidelines/f4.webp
- Slide 17: https://meetreference.com/media/ameba-blog-brand-guidelines/f5.webp
- Slide 21: https://meetreference.com/media/ameba-blog-brand-guidelines/f6.webp
- Slide 25: https://meetreference.com/media/ameba-blog-brand-guidelines/f7.webp
- Slide 29: https://meetreference.com/media/ameba-blog-brand-guidelines/f8.webp
- Slide 33: https://meetreference.com/media/ameba-blog-brand-guidelines/f9.webp

## Links

- View deck: https://speakerdeck.com/spindle/amebablog-brand-guidelines
- Original post: https://speakerdeck.com/spindle/amebablog-brand-guidelines