Previous Next
0 / 3
Module VC-02VIBECODE

Map File Dependencies

VIBECODE • Vibe Coding: AI-First Software Delivery

Browser-only practice

Problem Statement

Stage: Context Engineering

An agent needs to know which modules depend on which files before editing.

Deliverable

An alphabetized dependency adjacency list.

Input and output contract

Read source->dependency edges and print every node as node: comma-separated dependencies or -.

Acceptance criteria

  1. Include dependency-only nodes.
  2. Deduplicate edges.
  3. Sort nodes and dependencies.

Suggested vibe loop

Read AGENTS.md, connect your Ollama or OpenAI-compatible provider in the browser, and ask the agent to restate the contract and make one small verifiable change. Watch edits stream into app.py while the editor is locked, then review the result and run the visible example. Keep the checkpoint when the evidence is correct or use Undo to restore it. The browser-client agent does not require an administrator gateway or API key.

Constraints

Use Python 3 standard library only. Read and follow AGENTS.md, keep main.py as the entry point, and implement solve(raw) in app.py.

Sample Testcases

Submit runs every public testcase in this browser. Results and code never leave this device.

Sample #1
Public sample
Input
app->db
app->auth
auth->db
Output
app: auth,db
auth: db
db: -
Explanation
Builds a complete graph.

Web terminal

C, C++, Java, and Python run locally in a browser VM. No worker or visualizer is used.

Saved in this browser
Editor settings