The Insight Engine: AI-Powered Personalized Learning
A personalized, AI-generated learning experience — content dynamically created based on each user's profile, interests, and learning goals. MVP shipped in one weekend; iterated and polished over 8 days.
AI Product DesignClaude APIPrompt EngineeringSupabaseBehavioral DesignMultilingual
Project Overview
01
My Role
Sole product builder — product strategy · AI interaction design and prompt architecture · backend orchestration · front-end UX and onboarding · system debugging across six integrated services.
02
Timeline
Weekend MVP sprint (Jan 31 – Feb 2, 2026). Core product built in one weekend; features, debugging, and polish through Day 8.
03
Key Result
Functional MVP — profile-based onboarding, AI-generated insights, and automated daily emails personalized to each user. Scalable across unlimited subjects and languages.
Built With
Lovable
Discovery / Why I Built This
From Information Overload to Practical Wisdom
As a design leader with broad curiosity across many disciplines, I'm constantly exploring new ideas. Yet most learning platforms promise personalization while still delivering the same generic content to everyone.
The problem isn't the lack of information — it's the lack of usable understanding. Many platforms simply deliver information but rarely show how that knowledge can be applied in real-world situations. Without practical examples or context, it's difficult to translate new ideas into everyday decisions, work, or behavior. On top of that, much of the content is filled with jargon rather than explained clearly. I believe that if you can't explain something to a 10-year-old, you probably don't fully understand it.
The experience is also fragmented, with knowledge discovery and learning scattered across different platforms instead of integrated into one system. Many tools also require users to constantly check the app rather than delivering insights automatically.
Language also affects learning efficiency and speed. While I work in English daily, I can absorb and internalize complex ideas significantly faster when concepts are explained in my native language. When learning something new, reducing cognitive friction matters.
Conversations with design leaders upskilling in AI revealed the same friction points — the problem isn't lack of content, it's that existing tools deliver the wrong content, in the wrong format, at the wrong time.
Generic Content
Existing platforms deliver the same material regardless of expertise, learning style, or career trajectory — a senior director gets identical content as a mid-level designer.
Broken Continuity
No system remembers previous sessions or builds progressively on acquired knowledge. Users must context-switch back into learning mode each time.
App Proliferation
Each subject requires a different platform — one for tech news, another for psychology research, a third for design trends. Cognitive overhead actively discourages learning.
Language Friction
Most platforms deliver content exclusively in English with no native-language support — forcing non-native speakers to decode jargon before they can absorb the concept.
Theory Without Practice
Platforms teach abstract concepts without connecting them to practical job contexts — users master definitions but can't apply the knowledge to real-world situations.
Passive Content
Educational articles are delivered as static, one-way content — when learners have follow-up questions, there's no interactive way to get personalized explanations.
The Result: Fragmented Knowledge
5+ Apps Per User → Generic Content → No Memory Between Sessions → Push Notification Fatigue → Friction Between Curiosity And Learning
Discovery / Opportunities
How LLMs Solve Each Pain Point
Each pain point maps directly to a capability that large language models uniquely enable — turning limitations of traditional platforms into design opportunities.
01
AI-Curated Personalization at Scale
Use LLMs to deliver insights tailored to each user's goals and subject interests — moving beyond generic, one-size-fits-all content.
Personalization Layer
02
Bilingual Cognitive Access
Deliver insights in English and Chinese — reducing cognitive load for bilingual users and enabling deeper comprehension.
Language Intelligence
03
Frictionless Daily Ritual
Push insights directly to email — removing app-switching fatigue and letting learning integrate into existing daily routines.
Habit Architecture
04
Cross-Domain Knowledge Synthesis
Bridge psychology, neuroscience, philosophy, and design into unified insights — connecting disciplines that modern tools treat as silos.
Knowledge Graph
05
Compounding Growth Over Time
Build a personal insight archive — enabling reflection, visible progress, and the satisfying experience of knowledge compounding.
Retention Engine
06
End-to-End Builder Narrative
Showcase full-stack fluency — Claude API, Supabase, Resend — as a tangible portfolio signal of AI-native product thinking.
Portfolio Proof Point
The Approach: AI-Powered Personalization
One Engine, Infinite Personalization
The architecture separates who the user is (profile context) from what they need (content strategy) from how they receive it (personalized output). No two users get the same insight.
Input: User Profile
Contextual Data Captured
Learning Goals
Topics to explore, skills to develop, knowledge gaps to fill
Interest Areas
Multi-select from a growing subject library (MVP: 15 subjects across 8 categories, designed to scale)
Reading Level
Explorer, Learner, Practitioner, or Expert — calibrating AI tone and complexity
Language
Select any language — delivered in English, English + native, or native only
Schedule
Delivery time and timezone for daily email
Processing: Claude API
Prompt Engineering Framework
Role Definition
Claude established as expert learning advisor matched to user's domain
Context Injection
Profile variables inserted for deep personalization per request
Content Specs
Format, length, depth requirements calibrated to user level
Matched to reading level — from everyday analogies to field-specific language
Output: Daily Insight
Personalized Content Delivery
Adaptive Complexity
Content depth matches user's reading level — introductory to expert
Practically Relevant
Insights connected to real-world use cases, not abstract theory
Multilingual
Native language delivery — no translation overhead or cognitive friction
Conversational
Follow-up questions, deeper exploration within the learning experience
5-Minute Format
Optimized for quick daily consumption, replacing hours of fragmented reading
Process / System Architecture
The end-to-end flow from builder input to user delivery — showing how 6 services connect to generate and deliver personalized daily insights.
AI System Design
Five Layers That Power Every Insight
Instead of storing educational content, the system generates knowledge dynamically using user context and AI reasoning.
Layer 1
User Context
Goals, interests, reading level, language preference
→
Layer 2
Prompt Orchestration
Role definition, context injection, format rules, guardrails
→
Layer 3
LLM Generation
Claude API processes prompt + user profile into structured insight
→
Layer 4
Delivery Automation
Cron trigger → Edge Function → Resend email pipeline
→
Layer 5
User Experience
Daily email, settings, chat exploration
Visual 2
Prompt Architecture
Role
AI learning advisor tailored to user's professional context
Context
User goals + selected interests + reading level
Format
Hook → Explanation → Relevance → Real example → Reflection question
Tone
Matched to reading level — everyday analogies to field-specific language
Language
English, English + native, or native only
Visual 3
Personalization Engine
User Profile
Interests:Psychology, AI, UX Design, and more
Level:Practitioner
Language:English + Traditional Chinese
↓
AI Personalization Engine
↓
Generated Insight
Topic:Cognitive Bias in UX Decision Making
Format:Practitioner-level with real examples
Language:Bilingual (EN + 繁體中文)
User Experience
Two Touchpoints, One System
The product works through two complementary experiences: an app for personalization and exploration, and a daily email for proactive learning delivery. Together, they create a frictionless learning habit.
The App Experience
Configure, explore, and go deeper
Subject Selection
Choose from a growing subject library (MVP: 15 subjects across 8 categories) spanning AI, Psychology, Neuroscience, UX Design, and Behavioral Economics — chip-based multi-select with live counter.
Delivery Settings
Set daily email time, timezone, and preferred language. Changes apply immediately to the next scheduled insight.
Language Toggle
Switch between English and Chinese (Traditional) — enabling bilingual users to process in whichever language works faster.
Subscription Management
Pause, resume, or update active subscriptions. Full control over delivery without losing preference history.
Interactive Chat
Ask follow-up questions about any insight for deeper exploration — transforming passive reading into active learning.
The Daily Email Experience
Proactive delivery, zero friction
Personalized AI-Generated Content
Each email contains a unique insight generated by Claude, tailored to the user's selected subjects and reading level.
Structured 5-Minute Format
Every insight follows: Hook → The Connection → Simple Explanation → Why It Matters for UX → Real Business Example → Reflection Prompt.
Bilingual Delivery
Full content in English followed by Traditional Chinese (繁體中文) translation — both generated in a single API call.
Subject Tags
Each email is tagged with the relevant subjects (e.g., "Marketing & Growth · Human Behavior") so users can quickly identify the topic.
Scheduled Delivery
Arrives at the user's chosen time via cron-job.org → Supabase → Claude API → Resend pipeline. 100% delivery reliability.
Live Product
The Insight Engine In Action
A functional MVP built in one weekend — user authentication, profile capture, AI-generated personalized insights, and multilingual support. Try the live app below or open it directly.
The personalized settings dashboard once a user creates an account. This MVP is currently in closed testing and has not yet been scaled for open registration.
Challenges & Pivots
What Broke, What I Tried, What Worked
Building with AI tools isn't a straight line. These are the real debugging stories from my build diary — each one forced a pivot that made the final product more resilient.
Challenge 01
The Cron Job Nightmare
Problem
Supabase native cron kept failing with cryptic errors — "schema 'net' does not exist," "pg_net.http_post does not exist." 6+ hours debugging across multiple days.
What I Tried
Multiple Supabase cron configurations, Edge Function triggers, direct SQL scheduling. Full backend audit revealed: cron.job table was completely empty.
Solution
Pivoted to external cron-job.org. Set up in 30 minutes. 100% reliability since.
Learning
"Don't fall for sunk cost fallacy. If something takes 6 hours and still doesn't work, try a different approach."
Challenge 02
Email Template Persistence
Problem
Email template kept reverting to an old dark green design. Changes worked temporarily, then disappeared when updating send time.
What I Tried
Updated templates through Lovable UI multiple times. Each update worked briefly, then reverted on the next schedule change.
Solution
Went directly into the Edge Function code and hardcoded the template. Not elegant, but it worked. Decoupled scheduling from templating.
Learning
"When AI tools fail, go to the code level. And decouple your concerns — scheduling and templating shouldn't live in the same function."
Challenge 03
Duplicate Emails & Wrong Sender
Problem
A rogue second email was being sent at 4am from noreply@resend.dev instead of the correct onboarding@ address. Users received duplicates.
What I Tried
Full diagnostic audit of all 6 services. Discovered the end-to-end flow was "broken at Step 1" — the old cron job had been removed but a phantom trigger remained.
Solution
Removed duplicate trigger, recreated clean cron job, and wrote a systematic diagnostic prompt to audit each service independently.
Learning
"When debugging multi-service systems, audit each service systematically rather than guessing. Write the diagnostic checklist before you start fixing."
Before vs. After
Traditional Learning vs. The Insight Engine
The comparison highlights what changes when you apply AI personalization to the learning workflow.
Traditional
Insight Engine
Content
Generic, same for all users
Personalized to role, goals, expertise ✓
Continuity
No memory between sessions
Context maintained across sessions ✓
Engagement
Push notifications nagging to learn
Proactive daily delivery, habit-forming ✓
Language
English-only or manual translation
Native multilingual (EN/ZH) ✓
Depth
Static articles, no follow-up
Conversational exploration ✓
Time cost
Hours across fragmented platforms
5-minute daily insight ✓
Subjects
One app per domain
Unlimited subjects, one platform ✓
Results & Impact
System Capabilities
A weekend MVP that grew into a fully functional AI product — measured by system complexity, automation reliability, generation capability, and personalization scale.
100% email delivery reliability after cron migration
~5 sec generation-to-delivery latency
Scalability Potential
1,000+ personalized insight variations based on user profiles
365 insights per user annually with automated scheduling
Architecture supports unlimited subject expansion
What I Learned
Key Lessons From Building My First AI Product
01
Build First, Design Second (For AI Products)
As a designer, creating UI in Figma is familiar and relatively straightforward. What proved more important was understanding the workflow and constraints of the AI development stack. Before designing polished interfaces, I needed to experiment with the tools, APIs, and integration patterns to confirm what could actually work.
Building early prototypes helped me understand how the system behaves — response time, data flow, and feature feasibility. In AI products, validating what is technically possible should come before designing the final experience.
02
Ship Working Solutions Over Architectural Purity
While integrating multiple tools and platforms, I learned how sensitive these systems can be to configuration changes. A small setting change in one platform can break synchronization across several services, and diagnosing the issue can take hours — especially for designers without deep engineering backgrounds.
Instead of over-optimizing architecture, I learned to prioritize solutions that work reliably. In fast-moving AI workflows, pragmatic solutions that keep the system running are often more valuable than perfectly engineered ones.
What's Next
Phase 2: Multi-User Personalization
Phase 1 proved the core concept works. Phase 2 transforms the app from a single-user prototype into a scalable, multi-user platform with deep personalization — already in progress.
Phase 2: In Progress
Authenticated user accounts with onboarding wizard
Expanded subject library with 40+ topics across growing categories for personalized selection