cheffy

Our mission is to make cooking more intuitive and enjoyable. Whether you’re a seasoned chef or just starting your culinary journey, Cheffy is here to help you turn your ideas into delicious meals.

Through voice conversations with our AI assistant, you can describe what you’re craving, discuss dietary preferences, and explore new flavors. Our intelligent system then generates personalized recipes tailored to your needs, complete with ingredients, step-by-step instructions, and helpful tips.

plans for the futere

Cheffy Future Features Roadmap**

Based on the current architecture (Anam AI conversations, Recipe management, Event system with MCP integration, and Clerk auth), here’s a structured plan for upcoming features:

Phase 1: Alerts & Notifications System

Database Changes:

• Create Alert model for storing alert configurations
• Add UserPreference model for notification settings
• Create Notification model for delivery tracking (email, push, in-app)

Features:

• Event-based alerts (e.g., “Recipe is ready to cook in 30 mins”)
• Recipe reminders (e.g., “Check your soaking times”)
• Conversation milestones (e.g., “You’ve saved 10 recipes!”)
• Email/SMS integration via SendGrid or Twilio
• Push notifications via OneSignal or Firebase Cloud Messaging
• User notification preferences dashboard

API Routes:

• POST /api/alerts/configure - Create/update alert rules
• GET /api/alerts/user - Get user’s active alerts
• POST /api/notifications/send - Trigger notifications

---

Phase 2: Leaderboard & Gamification

Database Changes:

• Create UserStats model (recipes created, conversations, events)
• Create Achievement model (badges, milestones)
• Create Leaderboard model for caching leaderboard data

Features:

• Global leaderboards (Most recipes shared, Most helpful, etc.)
• Friend leaderboards (private groups)
• Achievement badges (First recipe, 100 recipes, etc.)
• Points system (create recipe = 10 pts, share = 5 pts, etc.)
• Weekly/monthly reset options for seasonal leaderboards
• Leaderboard visualization with charts

API Routes:

• GET /api/leaderboards/global - Get global rankings
• GET /api/leaderboards/friends - Get friend rankings
• GET /api/achievements/:userId - Get user achievements
• POST /api/achievements/unlock - Award achievement

---

Phase 3: Social & Sharing Features

Database Changes:

• Create RecipeShare model (shared recipes with sharing settings)
• Create Comment model (comments on recipes/conversations)
• Create Like model (favorites/likes on recipes)
• Add visibility field to Recipe (private, friends-only, public)

Features:

• Share recipes with specific users or generate shareable links
• Comments and ratings on recipes
• Like/favorite recipes
• Recipe collections/lists
• Follow other chefs
• Activity feed showing friends’ new recipes

API Routes:

• POST /api/recipes/:id/share - Share recipe
• GET /api/recipes/:id/comments - Get comments
• POST /api/recipes/:id/like - Like recipe
• GET /api/feed - Get activity feed

---

Phase 4: Advanced Event Management

Enhancements to existing Event system:

• Event categories (meal prep, cooking sessions, dinner parties)
• Recurring events
• Event invitations (invite other users)
• Event reminders (integrated with alerts from Phase 1)
• Calendar view
• RSVP tracking

Database Changes:

• Add category, recurring, location, capacity to Event
• Create EventInvite model
• Create EventRSVP model

---

Phase 5: Enhanced Analytics & Insights

Features:

• User cooking analytics (favorite cuisines, cook times, difficulty progression)
• Recipe performance metrics (how many times used, ratings, difficulty)
• Conversation insights (topics discussed, common questions)
• Usage patterns and trends
• Export data (PDF reports, CSV)

API Routes:

• GET /api/analytics/user - User analytics
• GET /api/analytics/recipes - Recipe insights

---

Phase 6: AI & MCP Enhancements

Building on existing MCP event server:

• Add recipe CRUD tools to MCP (create_recipe, list_recipes, etc.)
• Conversation analysis tool (summarize cooking discussions)
• Meal planning tool (suggest recipes based on inventory)
• Ingredient availability checker

---

Questions for You Before Proceeding:

1. Priority: Which feature matters most for your MVP? (Alerts, Leaderboard, Social, Events, Analytics, or MCP?)

2. Scope: Are you planning this for a single-user platform or multi-user with social features? Should we focus on the core features first?

3. Notifications: What’s your preference for notification delivery?

• Email only
• Email + push notifications
• Email + SMS
• In-app only

4. Leaderboard Scale: Are you thinking:

• Just user achievements/badges
• Global leaderboards (all users)
• Friend/group leaderboards
• All of the above?

5. Analytics: Do you need real-time analytics or can it be batch processed daily?

6. MCP Integration: Should MCP tools be fully featured or just read-only for now?