Umbraco Repository Pattern

This gets you up to speed on Umbraco's repository pattern for backoffice customization. It covers the core architecture: repositories as data operation entry points, data sources for actual I/O, and optional stores for session state. The big callout here is auth: never use raw fetch for API calls or you'll get 401 errors. Always use a generated OpenAPI client configured with Umbraco's auth context. The examples walk through basic CRUD repos, tree repositories, and wiring them into contexts with observable state. Good fit if you're building custom backoffice features and need to understand how Umbraco separates data concerns from UI logic.

skills.sh installs: 400
GitHub stars: 27
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-repository-pattern --agent claude-code

Installs into .claude/skills of the current project.

Files

Umbraco Repository Pattern

What is it?

Repositories are the Backoffice's entry point for data requests and update notifications, abstracting data access from various sources (server, offline database, store, Signal-R). They provide a structured way to manage data operations, separating business logic from direct data access for easier maintenance and scalability. Repositories use data sources behind the scenes, allowing consumers to work with data without knowing where or how it's stored.