Project Info
Inspiration
Most people will never know what it’s like to truly see sound or hear color. For millions with sensory or cognitive challenges—and for anyone craving deeper therapy, connection, or creativity—access to new senses has always been a dream. We wanted to turn that dream into reality. Harmony was born from a single question: What if technology could give everyone new senses? We set out to build a platform that bridges art, therapy, and accessibility—where sound becomes color, emotion becomes music, and everyone can experience the world in entirely new ways.
What it does
Harmony lets users see, hear, and feel the world differently. Users can describe their experiences, upload songs, or share photos—and Harmony generates immersive, multi-sensory outputs in real time. Deaf users can visualize music and sound as moving color. Blind users can hear images and artwork as layered ambient soundscapes. Anyone can translate emotions into visual and musical experiences for therapy, mindfulness, or creativity. Harmony blends text, audio, and images into a coherent 3D sensory world—bridging accessibility, art, and emotion.
How we built it
Our architecture brings together multiple cutting-edge tools for multimodal generation and rendering: Frontend → FastAPI: The user describes an immersive experience through text or images. The frontend sends this data to the backend via FastAPI. Storage + Memory: All user data is saved to MongoDB for persistence and Letta for contextual memory tracking. Orchestration Layer: The Harmony Orchestrator receives input data and calls Claude to interpret text and images into a coherent “story” that defines mood, emotion, and sensory tone. 3D World Generation: Claude produces a structured 3D world JSON, describing spatial layout, color palette, and movement. This is passed to Tripo3D for world generation. Immersive Music Creation: In parallel, Google Lyria Realtime composes dynamic, emotion-matched music based on the same story context. Frontend Visualization: The generated 3D world is rendered interactively in the frontend using Three.js, syncing sound, color, and movement into a single living experience. Together, these components make Harmony feel alive—reacting instantly to emotions, sounds, and visuals in real time.
Challenges we ran into
Translating abstract emotion into both sound and color required careful multimodal alignment and experimentation with embeddings. Managing real-time performance across Claude, Lyria, and Tripo3D while maintaining low latency was extremely difficult. Making Harmony accessible for both blind and deaf users pushed us to think beyond standard interfaces—how can someone feel color or see rhythm? Building a coherent orchestration layer that merged APIs and models into one narrative pipeline took extensive debugging and fine-tuning.
Accomplishments we're proud of
Built a fully functional pipeline that fuses Claude, Google Lyria, and Three.js into an end-to-end multimodal system. Successfully generated real-time 3D worlds and matching ambient soundscapes from just text and images. Designed Harmony to serve both accessibility and creativity—not just assistive tech, but expressive tech. Created something that feels human—users described it as “a new way to experience emotion.”
What we learned
True innovation in accessibility happens when we design for emotion, not limitation. AI can act as a sensory bridge—translating modalities like sound and sight in deeply meaningful ways. Building multimodal orchestration pipelines (text → 3D → sound) taught us how important synchronization and latency control are for immersive experiences. Working with creative AI systems like Claude and Lyria showed us that narrative and technical design go hand in hand.
What's next
Launching Harmony Studio, a creative toolkit where artists, therapists, and educators can design their own multi-sensory worlds. Integrating wearable haptics to add touch feedback—letting users feel sound and light. Expanding real-time accessibility features for deafblind users through vibration and braille devices. Partnering with accessibility organizations and mental health practitioners to bring Harmony into therapy and classrooms. Harmony turns synesthesia into a superpower—making therapy, creativity, and accessibility open to everyone.
🌈 SenseSync - Universal Sensory Translation Platform
See sounds. Hear colors. Experience synesthesia through AI.
🎯 Objective
SenseSync democratizes synesthesia through AI, making multisensory experiences accessible to everyone.
The Problem:
- 48M deaf Americans cannot experience music emotionally
- 8M blind Americans cannot experience visual art
- Mental health conditions need multisensory therapeutic tools that don't exist
- Only 4% of people naturally experience synesthesia
Our Solution:
An AI platform built on Model Context Protocol (MCP) that translates between senses in real-time:
- 🎵 Audio → Visual: See music as real-time colors
- 🎨 Visual → Audio: Hear paintings as soundscapes
- 💬 Text → Multisensory: Transform emotions into colors + sounds
- ♿ Accessibility: Deaf users "see" sounds, blind users "hear" images
- 🧠 Therapy: PTSD, anxiety, autism treatment tools
- 🎭 Creative: Compose with colors, paint with sounds
Impact:
- 56M Americans with sensory disabilities gain new experiences
- Clinical applications for mental health (40% improvement in studies)
- Educational enhancement (multisensory learning = 40% better retention)
- New creative medium for artists, musicians, game developers
Total Market: $8.2B (accessibility + mental health + creative tools)
🛠️ Tech Stack
Frontend
Next.js 14 + TypeScript + TailwindCSS
Three.js (3D visualizations)
WebAudio API (sound synthesis)
Framer Motion (animations)
Backend & AI (MCP Architecture) ⭐
Claude Sonnet 4.5 ⭐ → MCP orchestrator, semantic understanding
Letta Cloud ⭐ → Stateful memory, learns preferences
Groq ⭐ → Ultra-fast inference (<100ms)
Custom MCP Servers
1. audio-analysis → Librosa, Essentia (extract audio features)
2. color-generation → Groq (real-time color palettes)
3. sound-synthesis → Vapi ⭐ + fish.audio ⭐ (generate audio)
4. image-analysis → Claude Vision ⭐ + Reka ⭐
5. memory → Letta ⭐ (user preferences)
Data & Storage ⭐
Elastic Cloud ⭐ → Search, Agent Builder with MCP
Chroma ⭐ → Vector database (similarity search)
Conway ⭐ → Real-time streaming
PostgreSQL → User data
Redis → Caching
Integrations ⭐
Composio Toolrouter ⭐ → MCP server orchestration
Bright Data ⭐ → Research data scraping
CodeRabbit ⭐ → AI code reviews
Warp ⭐ → AI terminal
Architecture
User → Next.js Frontend
↓
Claude (MCP Orchestrator) ⭐
↓
5 Custom MCP Servers → Composio Router ⭐
↓
Letta Memory ⭐ + Elastic ⭐ + Chroma ⭐
↓
Real-time Output
📦 Key Dependencies
Frontend:
"next": "^14.0.0"
"three": "^0.159.0"
"@anthropic-ai/sdk": "^0.20.0"
"tone": "^14.7.77"
Backend:
anthropic>=0.20.0
letta>=0.1.0
librosa>=0.10.0
fastapi>=0.109.0
elasticsearch>=8.11.0
chromadb>=1.7.0
Analysis
View
Metric
- 9
- 4
- 2
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- MongoDBIn code
- Next.jsIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
- FastAPIClaimed
- PythonClaimed
6 of 8 appear in the indexed code. 2 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
19 KB
Source files
9
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
VishnuK1947/Harmony
21 files · 273 KB · @ d101ab9
Structure
Interface
5 files · 24%Screens, components and styles rendered to the user.
Application logic
8 files · 38%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript67%
- Markdown25%
- CSS8%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
src/sense-sync-frontend/package.json
npm · 16- @clerk/nextjs
- @specy/liquid-glass-react
- liquid-glass-react
- lucide-react
- mongodb
- next
- react
- react-dom
- +8 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.