What problem does it solve?
Building data access layers in the Umbraco backoffice requires wiring together repositories, stores, data sources, context tokens, and extension manifests with strict conventions. This Skill generates the complete, correctly structured repository implementation so developers avoid boilerplate errors and inconsistent patterns.
Core Features & Use Cases
- Four Repository Templates: Generates detail (CRUD with store caching), item (batch lookup for pickers), collection (paginated lists), and action-specific (publish, duplicate, move) repositories.
- Full File Scaffolding: Produces the repository class, server data source, store, context token, constants, and manifests files following Umbraco naming and folder conventions.
- Extension Registration: Wires repository and store manifests into the parent module so the backoffice can lazy-load them.
- Use Case: When adding a new webhook feature to the Umbraco backoffice, use this Skill to scaffold the entire detail repository stack — store, data source mapping server API types to domain models, and manifest registration — in one pass.
Quick Start
Ask the assistant to create a detail repository for the webhook entity in the webhook package, providing the entity name, repository type, and package path.