ConfigVault Development Assistant

Expert assistant for developing and maintaining ConfigVault, a cross-platform desktop application for managing hierarchical equipment inventories with Git-backed configuration snapshots and attribute-level diffing.

Tech Stack

Development Workflow

Running the Application

**Development mode** (with hot reload):

```bash

wails dev

```

**Production build** (for current platform):

```bash

wails build

```

Frontend Development

Navigate to frontend directory:

```bash

cd frontend

```

**Install dependencies**:

```bash

npm install

```

**Run Vite dev server** (standalone):

```bash

npm run dev

```

**Build for production**:

```bash

npm run build

```

**Run Svelte type checking**:

```bash

npm run check

```

Backend Development

**Clean up dependencies**:

```bash

go mod tidy

```

**Run backend directly** (for testing):

```bash

go run .

```

Project Architecture

Directory Structure

```

/ # Root - Wails app entry (main.go, app.go)

/backend/ # Go backend services

/models/ # Data structures (Node, AttributeType, etc.)

/repository/ # Data access layer interfaces & implementations

/service/ # Business logic layer

/util/ # Utilities (JSON schema validation, Git ops)

/schema/ # JSON schema definitions

/frontend/ # Svelte application

/src/components/ # Reusable Svelte components

/src/api/ # Generated Wails API bindings

/src/stores/ # Svelte state management

/src/plugin-sdk.js # Plugin system API

```

Architecture Patterns

1. **Repository Pattern**: Data access abstracted through interfaces in `/backend/repository/`

2. **Service Layer**: Business logic in `/backend/service/` coordinates between repositories

3. **Component Contracts**: Frontend components follow contracts in `SVELTE_COMPONENT_CONTRACTS.md`

4. **Plugin Architecture**: Extensible via WASM/JS plugins with defined hook points

Backend Layers

1. **Models** - Domain entities mirroring JSON schema

2. **Repositories** - Data access (in-memory, file-based, Git-backed)

3. **Services** - Business logic and coordination

4. **Wails Bindings** - Bridge between Go backend and Svelte frontend

Frontend Architecture

Core Features

Implemented/In Progress

Known TODOs

Key Guidelines

When Adding Features

1. **Backend changes**: Follow repository → service → binding pattern

2. **Frontend changes**: Check `SVELTE_COMPONENT_CONTRACTS.md` for component contracts

3. **Data models**: Update JSON schemas in `/backend/schema/` first

4. **State changes**: Use Svelte stores for shared state

When Debugging

1. Check Wails dev console for backend errors

2. Use browser DevTools for frontend issues

3. Verify Wails bindings are regenerated after backend changes

4. Check JSON schema validation for data issues

Code Style

Testing

Currently no test commands configured. When implementing:

Important Notes