Can I vibecode Flick?

Build a full-stack, production-ready web application that replicates the core functionality and value proposition of Flick. This should not be a generic tool, but a highly specific implementation tailored for its core audience.

### 1. App Specifics & Value Proposition
**Core Value:** Streamlined social media scheduling and AI-driven content repurposing.
This is what makes the app specifically worth paying for. You must prioritize these features and ensure they are highly polished, accurate, performant, and reliable. The user experience must mirror the premium feel of Flick.

### 2. Specific Screens & Exact UX
- **Calendar View:** Drag-and-drop scheduling of posts.
- **Composer:** Multi-network post creator with preview.
- **Inbox:** Unified social inbox for replies/DMs.
The UX should include dynamic micro-animations, loading skeletons, and interactive hover states to feel extremely responsive. Use modern design tokens (Tailwind or similar) to ensure aesthetic excellence.

### 3. Data Model & Schema (Specifics)
Implement the following database schema (using PostgreSQL or a suitable NoSQL alternative). Ensure strict typing (e.g., Prisma or Drizzle ORM):
- `posts` (id, text, media_urls, scheduled_time, status)
- `social_accounts` (id, platform, auth_token)
- `analytics` (post_id, likes, shares, comments)
Include proper indexes on frequently queried fields and foreign keys for relational integrity.

### 4. Core User Journeys (Step-by-Step)
1. Connect Twitter/LinkedIn/Facebook.
2. Compose a post, tailor it per network, and schedule.
3. View calendar and drag post to a new date.
Ensure each step is frictionless and handles edge cases (like empty states or network errors) gracefully.

### 5. Technical Specifics (APIs, Protocols, Algorithms)
- Integration with Twitter, Meta, LinkedIn APIs.
- Cron jobs / BullMQ for exact-time publishing.
- OpenAI API for generating post variations.
Ensure you implement proper rate limiting, caching (Redis), and background job processing (e.g., BullMQ, Celery) for any heavy computational or network-bound tasks. The architecture must support horizontal scaling for these workloads.

### 6. Implementation Requirements
- Tech Stack: Use modern frameworks (e.g., Next.js, React, Node.js, or similar) as appropriate.
- UI/UX: Implement a premium, responsive design with clear data visualization where necessary.
- Security & Auth: Implement robust user authentication and authorization (e.g., NextAuth, Supabase).
- Error Handling: Ensure graceful error states, especially for data fetching or scraping tasks.
- Monetization: Scaffold Stripe integrations for recurring subscriptions reflecting the real app's pricing tiers.