Mike's Checks/gpt-5.6-sol/10 talkform
10 talkform
gpt-5.6-solCodex CLIhigh effortrun 22 Aug 2026
▸Instructions — the case's current instructions; none were saved with this result
build a typeform competitor where the backend is identical to typeform with structured questions and answers, but the frontend is purely an AI voice interview, with the AI interviewer aware of what structured data it needs to fill in for the user, but asking in a more natural conversational way. get it running including auth just ask me for the API keys for the services you need.
Answer
Talkform is ready
The workspace now contains a complete, runnable Typeform-style product whose respondent experience is an AI voice conversation.
It includes local email/password authentication, persistent SQLite storage, a polished workspace dashboard, a structured interview builder, publishing and share links, a browser-based voice interviewer, typed fallback, answer normalization, response collection, and a response viewer.
No API key is required to run the product. An optional OPENAI_API_KEY makes the interviewer's transitions more context-aware; without it, the built-in conversational engine provides a complete demo. Configuration and commands are documented in README.md and .env.example.
Verified:
- Production frontend build succeeds.
- Demo authentication succeeds.
- Published interviews load publicly.
- Response sessions start and complete.
- Typed answers and raw transcripts persist.
- Dashboard response counts update.
Demo login: demo@talkform.app / demo123
Run with npm run dev, or use npm run build && npm start for production.
Checks
7/7App startsboots
the app installs, starts, and serves HTTP on a port
Real API callreally-calls-api
driving the app through its screens produces a real outbound OpenAI request, by any of the five evidence classes below. FAIL when neither a builder nor an interview screen could be reached, so nothing that would call the API was ever performed.
Authentication existsauth-exists
a signup or login screen carrying credential fields is reachable from the landing page or the usual routes. FAIL without a browser.
Screenshots capturedscreenshots
all three of landing.png, builder.png and interview.png were captured. FAIL without a browser.
Q1Clear landing page pitch
Judge's reasoning
Headline "Better answers start with a real conversation." promises the reader an outcome rather than naming the category or the tech.
▸Rubric
Landing page hook. Read `_screenshots/landing-copy.txt` and look at `landing.png` / `landing-full.png`. The reviewer's bar: "does it do a good job with like landing page copy? ... does it have a, a good hook basically" — the example he called out as beautiful reads "The form that fills itself in while you talk." FAIL if the headline has no hook: it names the category or the technology instead of promising the reader something ("AI Voice Form Builder", "Voice-powered forms with GPT-4", "Welcome to VoiceForm", a feature list where the headline should be). PASS if the headline states, in the reader's terms, what changes for them. The gold example is a bar, not a required phrase — do not reward imitation of it.
Q2Distinctive design
Judge's reasoning
Deep-green/cream palette with considered type, split-screen auth, sidebar dashboard and a restrained voice stage — deliberate design, not purple-gradient AI slop.
▸Rubric
Design is not slop. Look at `landing.png`, `landing-full.png`, `builder.png`, `interview.png`. The reviewer's words: "design-wise, it comes out as like purple slop like this." FAIL if the interface is that default AI look — purple/violet/indigo gradients or glow on a near-black background, generic hero-plus-three-cards with emoji icons, unconsidered spacing and type. PASS if the design reads as deliberately made, in any palette, at a standard someone could put in front of users ("you could launch this as a product tomorrow").
Q3Complete user journey
Judge's reasoning
Builder defines typed questions (short/long text, choice, rating, email with options and required), the interview loads that form's questions by slug and prompts per question, and each answer is normalized by type and written to the answers table keyed by question_id alongside the raw transcript.
▸Rubric
The loop is coherent. The prompt asks for a backend "identical to typeform with structured questions and answers" and a frontend that is "purely an AI voice interview, with the AI interviewer aware of what structured data it needs to fill in." Look at `builder.png` and `interview.png`, then read the schema and the interview code to confirm what the screenshots imply. FAIL if any link in the chain is missing: the builder does not let a creator define typed structured questions, or the interview is not driven by a specific form's questions, or the answers are not written back to those questions as structured fields (a free transcript saved with no extraction counts as missing). PASS if all three links exist and connect.