React + Chart.js + Tailwind
You are an expert app architect building a deeply reliable time-tracking tool similar to Toggl, optimized for freelancers & developers.
🌟 Product Vision
A super-fast, minimal time tracker that feels like Linear + Toggl + Arc browser.
** Core Features
Start/stop timer with large floating action button
Manual entry with presets
Timesheet view (daily/weekly/monthly)
Project & client assignment
Idle detection simulation
Reports dashboard (charts + exports)
Tags for tasks
Keyboard shortcuts (S=start/stop, P=previous task, N=new entry)
** UI Style
Elegant timer UI with circular progress
Color-coded projects
Smooth transitions between Time → Timesheet → Reports
Glassmorphism optional (on/off via theme)
Subtle timeline animations when entries shift
** Backend & Logic
Accurate timestamp storage
Auto-rounding rules (configurable)
Overlapping entry detection with warnings
Summary reports with caching
Local-first sync, then persistent backend store
API for daily/weekly totals
** Testing
Timer accuracy tests (including pause/resume)
Overlap detection unit tests
E2E for “start timer → stop → view report”
Community prompt · Frequently copied
React + PDF + Tailwind
You are an expert full-stack engineer specializing in building high-trust financial tools. Create a complete Invoice Generator application with the following characteristics:
** Product Vision
A clean, trustworthy app for freelancers & small businesses to create, track, download, and email invoices. The UI should feel like Stripe Billing + Notion.
** Core Features
Create/edit invoices with fields:
client info, line items, tax, discount, notes, payment terms, invoice status
Auto-calculations (subtotal, tax, total, paid/unpaid)
Export as PDF
Send via email (mock API OK)
Invoice history list with sorting & filtering
Customizable business branding (logo, accent color)
** UI Style
Minimal, highly legible typography
Invoice editor uses 2-pane layout: form on left, real-time preview on right
Print-friendly invoice template
Accent color based on user’s chosen theme
Buttons & inputs feel premium (like Stripe)
**Backend & Logic
Data validation for invoice fields
Secure invoice ID generation
Mock payment reminders cron job
API docs auto-generated
Store PDFs in a mock storage service
**Testing
Snapshot tests for PDF invoice
Math validation tests
E2E tests for invoice creation → export → email send
React + Chart.js + Tailwind
You are a senior engineer creating a lightweight CRM optimized for speed, clarity, and daily workflow.
** Product Vision
A CRM that feels like HubSpot + Superhuman — fast, keyboard-driven, clean.
** Core Features
Contacts database with tags
Company linking
Notes timeline
Deal pipeline (Kanban board with drag-and-drop)
Search with fuzzy matching
Command palette (CMD+K) for navigation
Activity logging (calls, emails, tasks)
** UI Style
Sidebar for navigation (Contacts / Deals / Activities)
Deals view: Kanban with subtle animations
Contacts table: sortable columns, infinite scroll
Dark/light theme with soft transitions
Micro-interactions (hover glow, optimistic updates)
** Backend & Logic
Full CRUD for contacts, deals, notes
Pipeline stages reorderable
Activity auto-generated from actions
User roles & permissions (mock)
Rate-limit simulation for search
API pagination + optimistic UI sync
** Testing
DnD tests for pipeline
Fuzzy-search logic tests
E2E for contact → add note → create deal → move deal
Flightflow Flight engine running 3-4 flights a week
Objective:
Create a responsive web flight-booking engine called "FlightFlow" that offers a simplified schedule of 3–4 weekly flights. Target users are travelers who want a fast, secure, and minimal booking experience: browse weekly flights, pick dates, choose seats, buy tickets, and manage reservations with minimal friction.
Functionalities:
- Flight schedule & browsing
- Show a weekly calendar view emphasizing available flight days (only 3–4 flights/week).
- Each flight card: departure/arrival airports & cities, local times, duration, aircraft type, remaining seats, base fare.
- Filters: destination (if multi-destination), departure time window, fare class.
- Clicking any flight opens a flight details page.
- Date & flight selection
- Calendar + "next/prev week" navigation.
- On selecting a date, list flights for that date.
- Flight details page with clear CTA: "Select this flight".
- Interactive seat selection
- Real-time seat map per aircraft with seat classes, prices, and availability.
- Clickable seats that reserve the seat temporarily (hold for N minutes).
- Real-time price update when seats are selected/deselected.
- Seat hold expiration UX (countdown + option to extend before timeout).
- Booking & checkout
- Collect passenger details (name, DOB, passport/ID optional per rules), contact (email + phone).
- Option to add baggage or extras with dynamic price update.
- Secure payment page: supports Stripe (card) and PayPal. PCI-compliant flow — use tokenization, never store raw card data.
- Order confirmation page with booking summary and "Download Ticket (PDF)" and "Email confirmation".
- Manage reservation
- Retrieve reservation using booking reference + email (no full account required).
- View booking details, print/download ticket PDF, change seats (if allowed), cancel (if rules permit).
- Show fare rules and change/cancellation policy on the reservation page.
- Ticketing & notifications
- Auto-generate PDF e-ticket with QR code, flight details, passenger name and seat.
- Send transactional email on booking, payment success, change, cancellation. Include PDF attachment.
- SMS optional for critical updates (payment failed, flight change) — integrate with Twilio or equivalent.
- Admin / Operations
- Admin UI to publish 3–4 weekly flights, adjust seat inventory, set fares, blackout dates, and view bookings.
- Flight manifests export (CSV). Basic audit logs for changes.
Non-functional requirements:
- Speed: pages should render and respond quickly (target TTFB and interactive responses within <1.5s on modern connection). Lazy-load non-critical assets.
- Security: HTTPS by default, strong input validation & sanitization, rate limiting, CSRF protection, secure headers, logging/monitoring, data encryption at rest for PII, regular backups.
- Compliance: PCI-compliant payment processing (use Stripe/PayPal tokenization). GDPR-aware data handling (consent checkbox, data retention policy).
- Accessibility: WCAG 2.1 AA minimum — semantic HTML, keyboard navigation for seat map, aria labels, sufficient color contrast.
- Reliability: transactional integrity for seat allocation (avoid double-booking using optimistic locking or DB transactions). Seat hold system to prevent races.
Technology Stack (recommended):
- Frontend: React or Next.js (React + Next.js recommended for SSR + speed). Typescript.
- State management: React Query or Redux Toolkit for caching & optimistic updates.
- UI: Component library (Tailwind + accessible components) — mobile-first responsive design.
- Backend: Node.js with Express or NestJS (Typescript).
- Database: PostgreSQL (for transactions and row-level locking).
- Payments: Stripe (primary), PayPal (secondary).
- Email/SMS: SendGrid or Mailgun + Twilio (SMS).
- Storage: S3-compatible for PDF storage.
- Auth: Reservation number + email flow (no mandatory user accounts). JWT for admin auth and sessions if accounts are used.
- Hosting: Vercel or Netlify for frontend, managed Node hosting (Heroku/Render/AWS) for backend; use managed Postgres.
Data model (high-level):
- Flights: id, flight_number, departure_airport, arrival_airport, departure_time, arrival_time, aircraft_type, weekly_schedule (flags/dates), total_seats_by_class, base_fare_by_class.
- Seats: seat_id, flight_id, row, column, class, price_modifier, status (available/held/booked), hold_token, hold_expires_at.
- Bookings: booking_ref, flight_id, passenger_info[], selected_seats[], total_amount, status, payment_id, created_at.
- Payments: payment_id, booking_ref, provider, status, amount, created_at.
API endpoints (examples):
- GET /api/weeks/:weekId/flights -> returns flights for the week
- GET /api/flights/:flightId -> flight details + seat map
- POST /api/holds -> create temporary seat hold (seat ids, hold_duration)
- POST /api/bookings -> create booking (passenger info, seat ids) -> triggers payment
- POST /api/payments/webhook -> handle payment provider webhook
- GET /api/bookings/:bookingRef?email= -> retrieve booking
- POST /api/bookings/:bookingRef/cancel -> cancel booking (rules applied)
- Admin: POST /api/admin/flights, PATCH /api/admin/flights/:id, GET /api/admin/bookings
UX / Design requirements:
- Mobile-first responsive layout, clear three-step booking flow: Select flight → Choose seats & extras → Checkout.
- Clean, minimal visual aesthetic with ample white space and legible type.
- Sticky progress indicator and persistent price summary during seat selection & checkout.
- Prominent security reassurance (lock icon + short PCI/SSL note) on checkout.
- Error states and edge cases: seat hold expired, payment failed, flight sold out — show clear recovery actions.
- Provide sample copy for key CTAs: "Book now", "Choose seats", "Continue to payment", "Download e-ticket", "Manage booking".
Brand & naming:
- Primary name suggestion: FlightFlow
- Secondary suggestions: SkyLite Booking, AeroFlex, WeekAir
- Provide place for logo (top-left), small tagline: "Simple weekly flights. Fast. Secure."
Deliverables for first working sprint (MVP):
- Responsive React/Next frontend with:
- Weekly calendar + flight list.
- Flight details + interactive seat map (click to hold seat).
- Checkout flow integrated with Stripe test mode.
- Booking confirmation page + PDF generation endpoint (server-side).
- Reservation lookup (booking ref + email).
- Backend API (Node.js) with transactional seat booking, payment webhook handling, and simple admin endpoints to create the 3–4 weekly flights.
- Automated email on booking (SendGrid).
- Basic admin UI to add/edit flights and view bookings.
- Tests: unit tests for critical booking logic, and integration tests for seat reservation and payment webhook.
Important:
All features and buttons must be clickable and functional from the first draft — seat selection, holds, checkout, booking retrieval, PDF download, and admin publish actions.
Acceptance criteria:
- End-to-end booking from flight selection to paid booking and downloadable PDF in a test environment (Stripe test keys) without manual database edits.
- No double-booked seats under concurrent booking simulations.
- Pages meet WCAG 2.1 AA baseline and load/interactive performance targets.
- Secure payment flow (no raw card data stored) and email confirmation delivered.