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.
npx -y skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-repository-pattern --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
wshobson/agents
github/awesome-copilot
github/awesome-copilot