---
description: Initialize agent context for the D3V-Server project
---

## /init Workflow

Use this workflow at the start of a new session.
Goal: understand the repo quickly without scanning the full codebase.

### Required first step

1. Read `D:\AntiGravity\D3V-Server\AI_CONTEXT.md`

Do not start with a broad recursive scan unless the user explicitly asks for a repo-wide audit.

### Minimal orientation sequence

After reading `AI_CONTEXT.md`, open only these files:

1. `D:\AntiGravity\D3V-Server\README.md`
2. `D:\AntiGravity\D3V-Server\backend\index.js`
3. `D:\AntiGravity\D3V-Server\backend\app.js`
4. `D:\AntiGravity\D3V-Server\backend\routes\main.js`
5. `D:\AntiGravity\D3V-Server\frontend\src\main.tsx`
6. `D:\AntiGravity\D3V-Server\frontend\src\App.tsx`
7. `D:\AntiGravity\D3V-Server\frontend\src\Router.tsx`
8. `D:\AntiGravity\D3V-Server\docker\Dockerfile`

That set is normally enough to understand:

- top-level architecture
- backend startup flow
- frontend startup flow
- route structure
- production packaging model

### Area-specific follow-up

Only then open files for the requested area:

- Backend/API task: inspect `backend/routes/`, `backend/internal/`, `backend/models/`
- Frontend/UI task: inspect `frontend/src/pages/`, `frontend/src/hooks/`, `frontend/src/api/`
- WireGuard task: inspect `backend/internal/wireguard.js`, `backend/routes/wireguard.js`, `backend/routes/wg_public.js`, `frontend/src/pages/WireGuard/`
- Build/deploy task: inspect `docker/`, `scripts/`, `install.sh`
- Docs task: inspect `docs/`
- Test task: inspect `test/`

### Important reminders

- This is a multi-package repo. Commands run in subdirectories, not from one obvious root workspace.
- Docker packaging is part of the product behavior, not just deployment.
- The frontend must be built before the production Docker image can be built.
- Some runtime behavior depends on env vars, mounted volumes, and container capabilities.
- Avoid rewriting upstream-shaped structure unless the task requires it.

### Ready message

When initialization is complete, summarize the project in 3-5 lines:

- what the app is
- backend entry
- frontend entry
- production assembly path
- the specific area relevant to the user's task