Loading lesson…
A shipped vibe-coded app needs a one-page handbook: what it does, where data lives, how to run it, how to deploy, and known risks. Write the smallest useful scope the agent can finish.
A shipped vibe-coded app needs a one-page handbook: what it does, where data lives, how to run it, how to deploy, and known risks.
Create HANDOFF.md with: product purpose, routes, database tables, env vars, deploy steps, test account, known risks, and next three improvements.Use this as the working prompt or checklist for the lesson.15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-maintenance-handbook
What is the primary purpose of a maintenance handbook for an AI-built application?
Which of the following would NOT typically be included in a maintenance handbook?
What does the principle 'name the job before naming the tool' mean?
Why is it important to 'run the result as a user, not as a fan of the tool'?
What does 'inspect the diff' refer to in app maintenance?
What does 'failure path' mean in the context of maintaining an AI-built app?
According to the principles in this lesson, what type of data should an app never expose?
What is the purpose of identifying a 'rollback path' when maintaining an app?
What does it mean to write 'the smallest useful scope' for a maintenance handbook?
Why should the maintenance handbook be written early in the app's lifecycle?
Which of the following is NOT listed as a key term in the lesson?
In this context, what does 'observable' mean for an application?
What is a 'runbook' in the context of app maintenance?
What is the relationship between the maintenance handbook and the concept of 'handoff'?
Why is it important to inspect data access when maintaining an AI-built app?