Home/
Part XII — Building Real Products (End-to-End Projects)/34. Project 3: "Vibe Coder" Assistant for Your Own Repo/34.1 Requirements: what it should and shouldn't do
34.1 Requirements: what it should and shouldn't do
Overview and links for this section of the guide.
On this page
Scope Definition
The "Vibe Coder" assistant must:
- Read files: It must have access to the current state of the filesystem.
- Understand ignored files: It must NOT read `.env` or `node_modules`.
- Edit files: It must be able to propose changes.
- Run commands: It should be able to run `npm test` or `ls`.
Non-Goals (What to Cut)
To keep this buildable in a weekend, we will NOT build:
- A full IDE: We will build a CLI or a simple wrapper. We won't rebuild VS Code.
- Multi-modal vision: We won't ask it to look at screenshots of the app (yet).
- Autonomous Agents: It will not run in a loop forever. It will run one turn at a time: User Input → AI Thought → AI Action → User Approval.
The "Human in the Loop" Pattern
The most important requirement is safety. The AI never edits a file without you seeing the diff first.