Sample blueprint (pre-generated — no API calls)
Habit Tracker
Streak-safe tracking, accountability circles, and actionable weekly coaching.
Focuses on retention mechanics that users trust: timezone-safe streak logic, quiet-hour reminders, and privacy-aware accountability circles.
Advanced outputs (CLAUDE.md, .cursorrules, Master Prompt)
Recommended Tech Stack
Primary stack: - Next.js 16 App Router + TypeScript strict. Reason: one codebase for onboarding, dashboard, and APIs. Alternative: Expo + Supabase if mobile-native is day-one requirement. - UI: Tailwind + shadcn/ui + Recharts. Reason: simple habit cards and trend charts without heavy charting overhead. Alternative: Tremor for quick analytics blocks. - Auth: Clerk social login. Reason: low-friction signup improves activation. Alternative: Auth.js if you need full control over auth data. - DB: Postgres + Prisma. Reason: reliable streak computations and relational circle memberships. - Notifications: OneSignal (push) + Resend (email fallback). Reason: configurable channel mix and quiet-hour support. - Jobs: Trigger.dev/QStash for reminder and weekly summary tasks. Reason: idempotent background scheduling. - Analytics: PostHog. Reason: event-first retention analysis and funnels. Why this stack: - Preserves deterministic core logic while enabling optional AI summaries. - Supports export-ready metrics and developer-friendly contracts.
Quick FAQ for this example
Why does this sample stand out?
It treats streak correctness and reminder fatigue as first-class engineering constraints.
Is AI required for weekly summaries?
No. The blueprint keeps deterministic summaries as baseline and AI as optional enhancement.
Can this scale beyond solo projects?
Yes. It already includes worker jobs, analytics events, and contract-driven APIs.
Copy this URL to share the sample blueprint.