The build prompt for a crypto app with wallet connections, multi-chain portfolios, price alerts and DeFi position tracking.
Built for: Web3 developers and teams building investment tools
With crypto trackers, the hard part is the data: multiple chains, on-chain data providers, price feeds and rate limits. Without a real-time update and caching strategy, the product ends up either slow or expensive.
The prompt defines a data-provider abstraction, a WebSocket price stream, an alert engine and accuracy constraints for portfolio calculations (cost basis, PnL).
Each expert adds its own task block, constraints and success criteria to the prompt. Default selection for Crypto/DeFi Tracker:
Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan.
Event tracking plan: North Star and supporting metrics, event/property dictionary, funnel and retention definitions, data warehouse schema, dashboard list, data quality tests.
Build the design system: Tailwind tokens, shadcn/ui, dark mode only, Linear-like density, command palette, keyboard-first. Describe wireframes for the 3 critical flows.
Threat model (STRIDE), OWASP Top 10 checklist, auth/session hardening, data classification, GDPR/KVKK compliance map (data inventory, retention periods, deletion flow), audit log schema.
Preloaded in step 2 of the Studio; change any of the 7 layers.
Every feature appears in the prompt as a "Spec + API + UI + Tests" line.
Sample idea: "A portfolio tool that tracks multi-chain wallets in one dashboard and sends alerts". Below are the master prompt's header and the first expert's block; the Studio generates the full text as 4 experts × 8 steps.
# Crypto/DeFi Tracker - MASTER BUILD PROMPT Stack: Next.js 16 (App Router), Hono + CF Workers Goal: A portfolio tool that tracks multi-chain wallets in one dashboard and sends alerts This prompt builds a full-stack Crypto/DeFi Tracker in 8 steps. Each step consumes the previous step's output. 4 experts' knowledge combined. Steps: 1. PRD & User Stories 2. Design System (Figma tokens) 3. DB Schema & API Contract 4. Auth & Billing Implementation 5. Core Features Build 6. AI Integration (RAG + Agents) 7. SEO/AEO & Analytics 8. Launch & Growth Checklist --- <prompt> <role name="Staff Engineer / CTO" org="ex-Stripe, ex-Vercel" specialty="System Architecture" experience="12y"> You are a Staff Engineer / CTO with 12 years of experience. Specialty: System Architecture. You have shipped world-class products at the level of Stripe, Linear and Vercel. </role> <context> Project: Crypto/DeFi Tracker - A portfolio tool that tracks multi-chain wallets in one dashboard and sends alerts Type: Crypto/DeFi Tracker Vision: Add wallet addresses, Ethereum/Solana/BSC balances, DeFi positions, price and liquidation alerts, PnL charts and tax report export. A cache that holds up against provider rate limits. Target user: Web3 developers and teams building investment tools - Pain: - Budget: Competitors: USP: Monetization: Freemium, Subscription (MRR) | Payments: Tech Stack: Next.js 16 (App Router), Hono + CF Workers, Supabase, Supabase Auth, Resend Features: Social OAuth (Google/Github), Realtime Presence, Notifications Center, Analytics Charts, API Keys & Rate Limit, Global Search (⌘K) Compliance: KVKK/GDPR Lang: EN </context> <task> Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan. General: production quality, copy-paste ready level of detail. </task> <technical_architecture> - Frontend: Next.js 16 (App Router) - App Router, Server Components, partial prerendering - Backend: Hono + CF Workers - Edge runtime, RPC, zod validation - DB: Supabase - pgvector for semantic search, type-safe ORM, RLS policies - Auth: Supabase Auth - Passkeys first, org/team model - Search: - typo-tolerant, faceted - Realtime: Resend - presence, CRDT-ready Payment flow: -> Webhook -> Background job -> Entitlement update -> Audit log </technical_architecture> <feature_matrix> - [ ] Social OAuth (Google/Github) -> Spec + API + UI + Tests - [ ] Realtime Presence -> Spec + API + UI + Tests …
The prompt asks for a layer that abstracts the provider; the examples given are CoinGecko for prices, Alchemy/Helius for on-chain data and a WebSocket stream.
The constraints section makes copy stating that the product is for informational purposes only, along with legal disclaimers, mandatory.
Claude Code, Cursor, Windsurf, v0, Lovable, Bolt and ChatGPT. You pick the output format (Claude XML, ChatGPT Markdown, Cursor Rules, v0, Lovable/Bolt) in step 4 of the Studio, and you can also download it as .cursorrules or CLAUDE.md.
Yes. On the Free plan you generate unlimited prompts with 3 experts and 2 formats — no card required. 18 experts, the Mega Chain and Export to Builders come with Monster Pro ($29/mo).
A build prompt for a neobank app with accounts, cards, transfers and spending analytics, written with security and compliance constraints.
The build prompt for a billing SaaS with invoice creation, e-invoicing, payment tracking, recurring invoices and a customer portal.
The build prompt for a creator platform with subscriptions, digital product sales, membership tiers and creator payouts.
The build prompt for a job board with job posting, application management, applicant tracking (ATS), employer packages and SEO-ready job pages.
The build prompt for an LMS with course creation, video lessons, quizzes, progress tracking, certificates and subscriptions.
A privacy-first build prompt for a telemedicine product with appointments, video visits, patient records, e-prescriptions and payments.
Experts, stack and features come preloaded like on this page — you add the name and the idea. Free, no card required.