Skip to content

PRODUCT.md

Latest commit

 

History

History
58 lines (35 loc) · 3.54 KB

PRODUCT.md

File metadata and controls

58 lines (35 loc) · 3.54 KB
Raw

Product

Register

brand

Users

Marinara Engine is for AI roleplayers, character chatters, immersive story players, and everyday users who may not be comfortable with technical setup. The product should welcome people who want rich AI conversations, roleplay scenes, game-mode adventures, visual assets, voice, agents, and prompt tools without feeling like they need to be engineers to enjoy it.

Primary users include:

  • AI roleplayers who want expressive character interactions, branching scenes, sprites, backgrounds, memories, lorebooks, and game-like immersion.
  • Casual chat users who want an approachable local AI companion/chat engine that feels fun instead of technical.
  • Power users who want deep control over models, prompts, agents, TTS, image generation, lorebooks, regex, and imports.
  • Nontechnical users who need clear setup flows, forgiving defaults, visible guidance, and mobile-friendly controls.

Product Purpose

Marinara Engine is a local, AI-powered chat, roleplay, and game engine built to make advanced AI interaction feel playful, visual, and plug-and-play. It combines conversation mode, immersive roleplay, and game mode into one connected experience where characters, memories, assets, agents, and prompts can work together.

Success means users can install Marinara, connect or configure a model, create or import characters, and quickly reach an immersive experience that feels alive. The interface should support serious power-user workflows while still feeling warm, pretty, and unintimidating for people who are bad at tech.

Brand Personality

immersive, pretty, playful

Marinara should feel like a lovingly built engine for stories and characters: expressive, slightly magical, approachable, and full of personality. It can be cute, dramatic, romantic, game-like, and cozy, but it should still feel capable and well-made. The tone should make advanced features feel discoverable rather than scary.

Anti-references

Marinara should not look like:

  • Sterile SaaS dashboards with gray cards, dry labels, and enterprise emptiness.
  • A bland SillyTavern clone that copies structure without adding identity.
  • A generic Discord clone that loses the roleplay, visual novel, and game fantasy.
  • A developer-only control panel where every screen assumes technical confidence.

Design Principles

  1. Make immersion the default impression. The interface should quickly communicate that Marinara is about characters, scenes, stories, voice, images, and game-like play, not only text boxes and settings.

  2. Hide complexity until it is useful. Powerful systems should be available, but common paths should stay clear, guided, and forgiving.

  3. Keep the interface pretty without sacrificing control. Visual charm matters, but controls still need to be legible, predictable, responsive, and efficient for repeated use.

  4. Treat mobile as a first-class play surface. Roleplay, conversation, and game mode should remain usable on phones with touch-friendly controls, readable text, and layouts that do not require desktop precision.

  5. Let personality show through utility. Settings, logs, agents, lorebooks, and prompt tools can still feel playful and polished. Functional screens should not become lifeless.

Accessibility & Inclusion

Marinara should prioritize mobile support and color-blind support. Core information should not rely on color alone; status, warnings, actions, and character states need labels, icons, contrast, or shape cues. Mobile layouts should preserve readable text, large enough tap targets, and controls that work without hover.