Automated summary
This skill guides the implementation of custom SVG icons in the Umbraco backoffice, registered through an extension manifest and a JavaScript icon registry.
Strengths
- Requires fetching the latest official Umbraco documentation before generating any code
- Provides the three key files (umbraco-package.json, icons.ts registry, SVG icon module) as minimal, complete examples
- Covers both declaring icons in an extension manifest and consuming them in templates via <umb-icon>
- Points to the working reference example inside the Umbraco source for production patterns
Limitations
- Covers only the "icons" extension type, not other Umbraco backoffice extension types
- Relies on WebFetch and on the Umbraco documentation URLs being reachable to produce trustworthy code
- Assumes an Umbraco extension package and TypeScript build are already set up
- Does not address SVG optimization, accessibility, or icon caching concerns
Use it when you need to add or register a set of custom SVG icons in an Umbraco project's backoffice.
Avoid it when extending other Umbraco backoffice areas (dashboards, property editors, sections) or when the project is not built on Umbraco.
Security analysis
SafeThe skill only instructs reading official documentation via WebFetch and creating/editing local icon and manifest files using Write/Edit. There are no destructive commands, data exfiltration, credential handling, or unsafe execution patterns.
No concerns found
How this analysis is madeExamples
Create a custom icon set for my Umbraco backoffice package with three SVG icons (a star, a tag and a chart), register them in the manifest and show me how to use one in a header app.I have four SVG files in my assets folder. Turn them into an Umbraco icons registry module, wire up umbraco-package.json and explain how to render them with <umb-icon> in my template.Fetch the latest Umbraco icons documentation, confirm the correct shape of the icons extension manifest and registry for my version, then generate the files.name: umbraco-icons description: Implement custom icons in Umbraco backoffice using official docs version: 1.0.0 location: managed allowed-tools: Read, Write, Edit, WebFetch
Umbraco Icons
What is it?
Icons are custom visual elements that extension authors can register for use throughout the Umbraco backoffice. Custom icons are registered through the manifest and can then be used in any extension that accepts an icon property. Icons are defined as SVG content exported from JavaScript modules.
Documentation
Always fetch the latest docs before implementing:
- Main docs: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-types/icons
- Foundation: https://docs.umbraco.com/umbraco-cms/customizing/foundation
- Extension Registry: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry
Reference Example
The Umbraco source includes a working example:
Location: /Umbraco-CMS/src/Umbraco.Web.UI.Client/examples/icons/
This example demonstrates how to register and use custom SVG icons. Study this for production patterns.
Workflow
- Fetch docs - Use WebFetch on the URLs above
- Ask questions - What icons needed? SVG source available?
- Generate files - Create manifest + icon files based on latest docs
- Explain - Show what was created and how to use the icons
Minimal Examples
Manifest (umbraco-package.json)
{
"name": "My Icons Package",
"extensions": [
{
"type": "icons",
"alias": "My.Icons",
"name": "My Custom Icons",
"js": "/App_Plugins/MyPackage/icons.js"
}
]
}
Icons Registry (icons.ts)
export default [
{
name: 'my-custom-icon',
path: () => import('./icons/my-custom-icon.js'),
},
{
name: 'my-other-icon',
path: () => import('./icons/my-other-icon.js'),
},
];
Icon File (icons/my-custom-icon.ts)
export default `<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
<path d="M12 2L2 7l10 5 10-5-10-5zM2 17l10 5 10-5M2 12l10 5 10-5"/>
</svg>`;
Using Custom Icons
// In any extension manifest
const manifest = {
type: 'headerApp',
kind: 'button',
alias: 'My.HeaderApp',
name: 'My App',
meta: {
label: 'My App',
icon: 'my-custom-icon', // Use your custom icon
},
};
In HTML Templates
<umb-icon name="my-custom-icon"></umb-icon>
That's it! Always fetch fresh docs, keep examples minimal, generate complete working code.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/umbraco-custom-icons-ms9wny7n' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/umbraco-custom-icons-ms9wny7n/download' --output '.skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md.part' && mv '.skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md.part' '.skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, WebFetch
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md' && test -s '.skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/umbraco-icons' && cp -R '.skill-downloads/umbraco-custom-icons-ms9wny7n' '.claude/skills/umbraco-icons'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/umbraco-custom-icons-ms9wny7n'openskills read 'umbraco-custom-icons-ms9wny7n'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/umbraco-custom-icons-ms9wny7n/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.