The One-Screen MVP Rule

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-one-screen-mvp

1. A developer starts a vibe-coded project by saying 'Build me a task management app with user auth, dark mode, push notifications, and cloud sync.' What fundamental mistake are they making?

   1. They're being too specific about technical requirements
   2. They're asking for too few features to test the AI's capabilities
   3. They're not giving the AI enough creative freedom
   4. They're defining the solution before defining the problem

2. What is the primary risk when an AI builds an app without a clearly defined first screen?

   1. The AI will invent functionality you didn't intend
   2. The AI will refuse to generate code
   3. The code will be syntactically incorrect
   4. The app will be too simple to be useful

3. What does RLS stand for in the context of vibe coding safety?

   1. Row-Level Security
   2. Runtime Language Syntax
   3. Remote Loading System
   4. Response Logging Service

4. A vibe-coded app passes all functional tests but exposes user email addresses to anyone with the app URL. What safety principle was violated?

   1. The app didn't have enough features
   2. The failure path wasn't inspected
   3. The diff wasn't reviewed before deployment
   4. Data access controls weren't properly defined

5. Why is running the app 'as a user, not as a fan of the tool' an important habit?

   1. The tool works better when you compliment it
   2. Developers should only test on weekends
   3. Fans get early access to new features
   4. Users find bugs that developers miss because they test realistically

6. What is a 'brittle fix loop' in the context of vibe coding?

   1. A situation where fixes create new problems that require more fixes, creating an endless cycle
   2. When the AI refuses to make changes
   3. A loop that runs too slowly
   4. When the code is too rigid to modify

7. What is the purpose of defining a rollback path before deploying a vibe-coded app?

   1. To ensure the AI can learn from mistakes
   2. To make the app load faster
   3. To impress investors with technical sophistication
   4. To have a way to revert changes if something goes wrong

8. Which question should you NOT ask when scoping a one-screen MVP?

   1. Which AI model should generate the code?
   2. What should the user be able to do when this is finished?
   3. What test proves the change works?
   4. What data should the app never expose?

9. A developer adds 'just one more feature' to their one-screen MVP, then another, then another. What is this pattern called?

   1. Vertical scaling
   2. Scope creep
   3. Iterative development
   4. Feature enrichment

10. What does inspecting the 'diff' involve in vibe coding?

    1. Analyzing user feedback
    2. Reviewing the code changes before running the app
    3. Comparing different AI models
    4. Checking visual differences between screens

11. The lesson states that AI can make a working demo quickly. What does it identify as the real skill?

    1. Writing prompts faster
    2. Turning demos into observable, reversible, and safe products
    3. Making demos look impressive
    4. Using the latest AI model

12. Why is it risky to deploy a vibe-coded app without testing the failure path?

    1. Failure paths don't exist in AI-generated code
    2. The AI will get offended
    3. You won't know how the app behaves when things go wrong
    4. The app will run too slowly

13. What is the relationship between scope and completion in the one-screen MVP approach?

    1. The scope should be the smallest useful unit the agent can finish
    2. Smaller scope means longer development time
    3. Bigger scope impresses users more
    4. Scope doesn't affect completion

14. A vibe-coded app shows the wrong data to users but works fine in testing. What likely happened?

    1. The test environment was different from production
    2. The AI used hardcoded test data
    3. The failure path wasn't tested
    4. The app has too much security

15. What is a key difference between a prototype built with Lovable versus a production app?

    1. Prototypes may not have proper security, rollback, or observability
    2. Production apps require manual coding
    3. Lovable prototypes are always faster
    4. There is no difference