Flora You.

› 提示词You are a senior AI-native software engineer. Given this problem: [your problem here] Help me: 1. Identify ambiguous requirements 2. List clarifying questions 3. Define success criteria (include 1-2 measurable eval metrics I can verify against) 4. Separate MVP vs Nice-to-have 5. Estimate what can realistically be built in a 45-minute interview If an answer is not available, state explicit assumptions and move on. Keep answers concise.

› 提示词Design the thinnest end-to-end workflow for this problem. Output: - components - data flow - APIs - dependencies Use simple ASCII diagrams. Optimize for getting a working version running in 5-10 minutes.

› 提示词 — MVP 骨架Define the golden path (the single main success scenario) and a minimal runnable skeleton. Requirements: - describe the MVP scope first (what's in / what's out) - produce only an end-to-end runnable skeleton — wiring, not feature code - mock external systems if needed - no premature abstractions - no authentication - no database unless required - if the solution includes a frontend page, make it runnable in a browser and provide the URL/opening step Goal: a skeleton that runs end-to-end; real feature code comes per-slice next. Smoke test before delivery: - after producing the skeleton, actually RUN it and exercise the golden path ONCE - show the real stdout / curl response / what you observed — do NOT infer from reading code - happy path only; just prove the skeleton boots and returns a response end-to-end - if it doesn't run: minimal fix (max 1-2 iterations), then re-run; if still broken, stop and report Gate: do NOT proceed to the GIT step until the skeleton has booted and answered the golden path once for real.

› 提示词Break the MVP into vertical slices. Each slice must: - be independently runnable - provide visible user value - be demoable - take less than 10 minutes to implement Avoid splitting by layers (frontend/backend/database). Prefer end-to-end slices.

› 提示词 — 将 N 替换为切片编号Implement only Slice N. Constraints: - for Slice 1, scaffold minimally; from Slice 2 on, modify existing code only - do not refactor unrelated files - keep diff minimal - return code changes only - assumptions only if strictly required for implementation (no design discussion)

› 提示词 — 将 N 替换为切片编号Run and verify Slice N now — actually execute, do NOT infer from reading code. Pick the verification that fits this slice and actually DO it: - backend / CLI / script / API → run the command, show real stdout/stderr or curl response - web page / UI → actually open the page, walk this slice's flow, observe the result If it fails: perform minimal fix (max 1–2 iterations). If still failing, stop and report. Before giving PASS/FAIL, PRINT the test cases you actually ran: | # | input / action | expected | actual (real output / observed) | pass? | At least 1 case for the happy path; add an edge case only if cheap. Then give overall PASS / FAIL. Gate: a slice isn't "done" without printed test cases backed by a real execution. Demo card (for presenting to the interviewer): - what this slice added (one line) - how to demo it: where to open / what to type (exact input) / what I'll see Only list what actually passed; if it didn't run, leave it out.

› 提示词I'm about to demo this app to the interviewer, but I haven't tracked slice by slice what you built. Consolidate every slice that is done AND actually passed in step 6 into a single demo script I can read off and click through end to end. Write the whole script to DEMO.md. It must contain: 1. Feature list: one line per completed slice — what it added + which file holds the code. 2. How to start: one command to boot the server + the URL to open. 3. Demo route (ordered for presentation), each step gives: - action: which URL / where to type / what to type (quote it exactly) / which button - what I'll see: what actually appears on screen (one line) - what to say: one line I can say to the interviewer 4. Flag anything broken: if a slice didn't pass, call it out — don't let me demo a broken feature live. Only describe features that were actually built and verified; do not put unimplemented work in the demo route. When done, save/overwrite DEMO.md and tell me its path and how to open it.

› 提示词Given this AI workflow: [paste architecture] Design a lightweight evaluation strategy. Include: - 5 test cases - expected behavior - failure modes - metrics Keep it interview-sized.