Domain: Design

This is a thin overview page. Detailed content lives on dedicated entity / concept / synthesis pages — follow the links.

Team

  • ben — Head of Design, harmony.ai
  • ayala — Designer (under Ben); prototype tracks and SDR productization

Active design work

  • self-learning-voice-agent — productization gap is design-led: UX, onboarding flow, playbook builder, CRM-integration polish, customer-facing dashboards (AI-016, owners: vitali / ayala)
  • Prototype tracks (AI-014, ayala + two groups) — two competing product mockups: deep SDR vertical AND Global Maximum platform; landing page + product UI

Design-partner program

Practices & principles

  • designer-as-developer — expanding designers’ role to write production code with tooling and training
  • touch-onboarding — the GTM model design must support (sales reps + SE-led, hours/days)

Tooling stack (emerging from ai-first-design-setup-2026-04-20)

  • IDE/agent: claude-code is the primary tool (Claude Code Visual under evaluation per AI-026)
  • Design system foundation: vibe — use atoms/tokens layer; build molecules with AI (AI-027 experiment)
  • Skills: install superpowers, skill-creator, Notetaker/CRM front-end rules (via yuval-ezov) — see AI-025
  • Context agent: in-Slack design agent planned (AI-024) for on-the-fly context capture
  • External advisor: elad (Vibe team lead at monday)

Customer-facing surfaces design owns

  • Onboarding & playbook-builder UX for the self-learning-voice-agent
  • Dashboards proving the self-learning-loop (versioned playbooks, objection tracking, qualification rate, meeting rate, downstream pipeline quality)
  • The “Twitter feed”-style revenue-platform UI surfaced in brain-layer (transparent / auditable / “white box”)

Cross-references

  • Active design action items live in action-items — AI-012, AI-014, AI-016 are the current design-led / design-co-led tasks
  • Design-relevant decisions: DEC-013 (positioning impacts marketing UI), DEC-015 (voice-as-feature shapes how the brain is surfaced visually), DEC-018 (API-first means design must work for headless/embedded contexts too)
  • For competitive product/UX references see competitive-landscape