Skip to main content

​
Overview

The examples below come from real runs in the projects/ directory. Each is a blueprint (PRD, PLAN, specs, prompts, infra). The code snippets are illustrative of style and structure; you implement the final app from the specs and prompts.

​
1. SnackRush — Junk Food Ordering App (Web Application)

Idea A junk food ordering app for urban users: curated snack menus, vendor partnerships, real-time ordering, and Google Pay. Web-first, with promotions for late-night snackers. Platform Web Application — Next.js, Node/Express, PostgreSQL, auth, real-time tracking, payments. What the blueprint includes PRD (excerpt) 
## 4. Key Features

### 4.1 User Authentication and Profiles
- Users register/login via email, Google, or phone (OTP).
- Profile: favorites, delivery addresses, order history.
- Backend API: /auth/register, /auth/login, /users/profile (JWT).

### 4.2 Browse and Search Junk Food Menu
- Catalog: Chips, Burgers, Pizzas, Candies, Fast Treats.
- Search/filter: type (salty/sweet/spicy), price, popularity, vendor.
- Backend: /menu/search, /vendors/{id}/menu (WebSocket for stock).

### 4.3 Shopping Cart and Order Placement
- Cart persists; customization (e.g. extra cheese).
- Delivery or Pickup (QR at store).
- Backend: /cart/add, /cart/checkout, /orders/place.
Lesson Be specific in Idea/Intent. Terms like “junk food”, “vendor partnerships”, “Google Pay”, “web-first” produced a focused PRD and clear API surface.

​
2. Web-Based Solana Wallet (Phantom-like) (Web Application)

Idea Build a Solana wallet like Phantom: create/import wallets, manage SOL and SPL tokens, connect to dApps, sign transactions. Web-only, non-custodial, no fiat on-ramps. Platform Web Application — Next.js, Solana Web3.js, client-side key handling, optional backend for indexing. What the blueprint includes PRD (excerpt) 
## 3.1 Wallet Management (P0)
- Create Wallet: BIP39 seed (client-side), encrypted key in localStorage.
- Import Wallet: Seed phrase or private key; validate BIP39/base58.
- dApp Integration: Connect, sign transactions.
- Exclusions: No fiat on-ramps, no staking, no NFT minting.
Lesson Exclusions matter. Explicit “no fiat, no staking, web-only” kept scope tight.

​
3. IndieTunes — Solana Music Marketplace (Web Application)

Idea A Solana-based marketplace for indie music: artists upload and sell; fans pay with SOL/SPL. Royalties on-chain, discovery, and streaming-style playback. Platform Web Application — Next.js, Node, PostgreSQL, Solana, storage for audio. What the blueprint includes Full web app layout: docs, frontend, backend, db, infra, testing, meta. Backend specs cover /api/music, /api/transactions/create, upload flows, and Solana integration. Lesson Chain + use case up front drives correct backend and PRD structure.

​
4. Decentralized P2P Messaging (Android)

Idea A decentralized P2P messaging app: E2E encryption, no central server, offline support. Android-first. Platform Android — Kotlin, Jetpack Compose, Firebase (optional), Room, GCP. What the blueprint includes Lesson Platform choice changes everything. “Android-first” produced Kotlin/Compose specs and GCP infra.

​
5. SaaS for Selling Digital Products (Web Application)

Idea A SaaS to sell digital products (PDFs, text files) with Solana payments: creators upload, set prices; buyers pay and download. Platform Web Application — Next.js, Node, PostgreSQL, Solana, file storage. What the blueprint includes
  • docs/ — PRD, HUMAN_REVIEW, PROJECT_RULES
  • frontend/ — react_nextjs, components, state_management, prompts
  • backend/ — node_express, auth
  • db/ — schema, migrations, orm
  • infra/ — monitoring, secrets
  • meta/ — github_push, export
Lesson Payments + asset type directly shape payout and download flows.

​
6. Student PG Finder for Bangalore (Web Application)

Idea An app for students in Bangalore to find PG accommodations: search by area, budget, amenities; contact owners; reviews and shortlist. Platform Web Application — Next.js, Node, PostgreSQL, auth, search, reviews. Lesson Audience + geography (“students”, “Bangalore”, “PG”) directly influence filters and flows.

​
Common patterns in generated blueprints

PatternWhere it shows up
PRD structureExecutive summary, goals, personas, features, exclusions
User storiesPRD / PLAN (“As a… I want… so that…”)
API-firstBackend specs and openapi.md
Tech alignmentStack matches chosen platform
SecurityJWT, env-based secrets, no keys in client
InfraTerraform, CI/CD, monitoring; mobile adds GCP/Xcode

​
Code samples (from specs)

Frontend (state management style) 
const response = await fetch('/api/cart/add', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': `Bearer ${token}`
  },
  body: JSON.stringify({ itemId, quantity, customizations }),
});
Backend (auth pattern) 
jwt.verify(token, process.env.JWT_SECRET, (err, user) => {
  if (err) return res.status(401).json({ error: 'Unauthorized' });
  req.user = user;
  next();
});
Blockchain-style spec 
const connection = new Connection(process.env.SOLANA_RPC_URL, 'confirmed');
const balance = await connection.getBalance(publicKey);
Use these as reference patterns; implement with your own validation and error handling.