Skip to content

PRODUCT.md

Latest commit

 

History

History
57 lines (35 loc) · 4.32 KB

PRODUCT.md

File metadata and controls

57 lines (35 loc) · 4.32 KB
Raw

Product

Register

brand

Platform

web

Users

The primary audience is technically sophisticated builders, engineering leads, and agent-tool users evaluating whether an agent workspace can do real work without surrendering control of their machine, data, or execution history. They arrive curious but skeptical and need concrete evidence more than category claims.

The secondary audience is open-source contributors who need a fast path into Maka's architecture, current capabilities, and source repository. The website audience and the eventual product user substantially overlap.

Product Purpose

The homepage explains Maka as a local-first workspace for directing, supervising, and completing real work with agents. It must distinguish Maka from disposable chat interfaces, show how conversation, Tool Calls, permissions, artifacts, and durable task state stay connected, and make the project's current source-first maturity explicit.

Success means a visitor can understand Maka's trust model and execution model within one pass, verify the claims through real product imagery and architecture links, and confidently continue to the GitHub repository.

Positioning

Maka turns agent work into inspectable, recoverable local execution—not disposable chat.

Conversion & proof

  • Primary CTA: View source at maka-agent/maka-agent.
  • Secondary CTA: Read architecture in the official repository.
  • The line a visitor remembers after 10 seconds: A local-first Agent workspace built for real work.
  • Belief ladder: Maka is more than chat → work runs locally by default → Tool Calls and permissions remain inspectable → outputs become real artifacts → event logs make progress recoverable → the implementation is open for inspection.
  • Proof on hand: the public source repository, ARCHITECTURE.md, DESIGN.md, security documentation, and official product screenshots for the Artifact pane, first-run provider setup, and honest error states. No testimonials, customer logos, adoption metrics, or release claims are available and none may be fabricated.

Brand Personality

Calm, exact, capable. The interface should feel like a well-made command instrument used in daylight: spacious enough to think, dense where evidence matters, and confident without spectacle. The emotional goal is agency—visitors should feel that Maka exposes the work instead of performing intelligence at them.

Anti-references

  • Generic AI tool marketing: purple-blue gradients, decorative glow, glassmorphism, sparkle, floating chat bubbles, or fake “thinking.”
  • Fake terminal aesthetics, invented commands, fake metrics, fake dashboards, testimonials, or capability claims unsupported by the official repository.
  • Mascots, anime characters, fake emotion, or avatar-led storytelling.
  • Identical card grids, hero-metric templates, bento layouts, and repeated tiny uppercase section eyebrows.
  • Blindly copying another product's claims, identity, or portfolio content. Reference geometry, motion, typography ratios, and rendering techniques may be reproduced when they make Maka more coherent; the meaning shown must remain truthful to Maka.

Design Principles

  1. Show execution, not AI theatre. Every visual signal maps to a real Maka concept: task, turn, Tool Call, permission, artifact, event, recovery, or surface.
  2. Proof sits beside the claim. Real product screenshots and repository links carry the story; abstract copy never outruns evidence.
  3. One working plane. Conversation, runtime evidence, and artifacts read as one connected workspace rather than a dashboard of disconnected cards.
  4. Local means legible boundaries. The page keeps data location, permissions, and recovery visible without fear-based messaging.
  5. Judge by coherence, not distance from the reference. Reproduce proven spatial grammar, typography ratios, DOM/canvas cooperation, and motion when they improve the result. Adapt only where Maka's content, execution model, or trust semantics require it.

Accessibility & Inclusion

Target WCAG 2.2 AA. All core content and navigation remain semantic and usable without WebGL or JavaScript. Keyboard focus is always visible, text supports 200% zoom and reflow, touch targets are at least 44×44 CSS px, color is never the only state signal, and prefers-reduced-motion replaces continuous motion with a static execution map.