# Unity Mvc Pattern

> Implementation of Model-View-Controller (MVC) and Model-View-Presenter (MVP) patterns in Unity. Focuses on Separation of Concerns for scalable UI and game systems.

- Skill: `muharremtozan/unity-mvc-pattern` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add muharremtozan/unity-mvc-pattern`
- Raw SKILL.md: https://api.skillmd.com/api/skills/muharremtozan/unity-mvc-pattern/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: muharremtozan (https://skillmd.com/u/muharremtozan)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/muharremtozan/unity-mvc-pattern

---


# Unity MVC / MVP Pattern

This skill implements the architectural principle of "Separation of Concerns." It divides your code into three distinct layers: Model (Data), View (Visuals), and Presenter (Logic bridge).

## Core Features
1. **ObservableList**: A reactive collection that notifies listeners (the View) when data changes.
2. **Passive View**: Views are MonoBehaviours that only care about HOW to display data, not WHERE it comes from.
3. **Mediated Logic**: The Presenter handles the "Wiring" and lifecycle, keeping Data and Visuals completely decoupled.
4. **MMO Hotbar Pattern**: A concrete implementation of the multi-slot observable layout described in the reference text.

## Core Files (Max 3)
- `ObservableList.cs.txt`: Generic collection wrapper with structural change notifications.
- `GenericPresenter.cs.txt`: Base class for creating M-V-P relationships without boilerplate.
- `MMOHotbarExample.cs.txt`: Practical application showing data flowing from a Model to a UI view.

## Usage

### 1. The Model (Data)
Contains your state using `Observable<T>` or `ObservableList<T>`. It does not know about Unity UI.

### 2. The View (Visuals)
A MonoBehaviour that exposes public methods for updating its state (e.g., `SetHealth(float val)`).

### 3. The Presenter (Bridge)
```csharp
public class MyPresenter : Presenter<MyModel, MyView> {
    protected override void Bind() {
        model.health.OnChanged += view.SetHealth;
    }
}
```

## When to Use
Use this pattern for complex UI (Inventories, Skill Trees, Settings) or high-level game managers where logic and visuals are likely to change independently.