Comprehensive guide for building Blazor apps with Microsoft Fluent UI components.
Works with
Covers setup (service registration, mandatory providers), component patterns (lists, dialogs, forms), and icons via a separate NuGet package with strongly-typed variants and sizes
Explains critical patterns: FluentSelect / FluentAutocomplete use Items , OptionText , and SelectedOption binding (not <option> children), and dialogs use IDialogService with content components, not visibility toggling
Pr
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfluentui-blazorExecute the skills CLI command in your project's root directory to begin installation:
Fetches fluentui-blazor from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate fluentui-blazor. Access via /fluentui-blazor in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
This skill teaches how to correctly use the Microsoft.FluentUI.AspNetCore.Components (version 4) NuGet package in Blazor applications.
<script> or <link> tags neededThe library auto-loads all CSS and JS via Blazor's static web assets and JS initializers. Never tell users to add <script> or <link> tags for the core library.
These provider components MUST be added to the root layout (e.g. MainLayout.razor) for their corresponding services to work. Without them, service calls fail silently (no error, no UI).
<FluentToastProvider />
<FluentDialogProvider />
<FluentMessageBarProvider />
<FluentTooltipProvider />
<FluentKeyCodeProvider />
builder.Services.AddFluentUIComponents();
// Or with configuration:
builder.Services.AddFluentUIComponents(options =>
{
options.UseTooltipServiceProvider = true; // default: true
options.ServiceLifetime = ServiceLifetime.Scoped; // default
});
ServiceLifetime rules:
ServiceLifetime.Scoped — for Blazor Server / Interactive (default)ServiceLifetime.Singleton — for Blazor WebAssembly standaloneServiceLifetime.Transient — throws NotSupportedExceptiondotnet add package Microsoft.FluentUI.AspNetCore.Components.Icons
Usage with a @using alias:
@using Icons = Microsoft.FluentUI.AspNetCore.Components.Icons
<FluentIcon Value="@(Icons.Regular.Size24.Save)" />
<FluentIcon Value="@(Icons.Filled.Size20.Delete)" Color="@Color.Error" />
Pattern: Icons.[Variant].[Size].[Name]
Regular, FilledSize12, Size16, Size20, Size24, Size28, Size32, Size48Custom image: Icon.FromImageUrl("/path/to/image.png")
Never use string-based icon names — icons are strongly-typed classes.
FluentSelect<TOption>, FluentCombobox<TOption>, FluentListbox<TOption>, and FluentAutocomplete<TOption> do NOT work like <InputSelect>. They use:
Items — the data source (IEnumerable<TOption>)OptionText — Func<TOption, string?> to extract display textOptionValue — Func<TOption, string?> to extract the value stringSelectedOption / SelectedOptionChanged — for single selection bindingSelectedOptions / SelectedOptionsChanged — for multi-selection binding<FluentSelect Items="@countries"
OptionText="@(c => c.Name)"
OptionValue="@(c => c.Code)"
@bind-SelectedOption="@selectedCountry"
Label="Country" />
NOT like this (wrong pattern):
@* WRONG — do not use InputSelect pattern *@
<FluentSelect @bind-Value="@selectedValue">
<option value="1">One</option>
</FluentSelect>
ValueText (NOT Value — it's obsolete) for the search input textOnOptionsSearch is the required callback to filter optionsMultiple="true"<FluentAutocomplete TOption="Person"
OnOptionsSearch="@OnSearch"
OptionText="@(p => p.FullName)"
@bind-SelectedOptions="@selectedPeople"
Label="Search people" />
@code {
private void OnSearch(OptionsSearchEventArgs<Person> args)
{
args.Items = allPeople.Where(p =>
p.FullName.Contains(args.Text, StringComparison.OrdinalIgnoreCase));
}
}
Do NOT toggle visibility of <FluentDialog> tags. The service pattern is:
IDialogContentComponent<TData>:public partial class EditPersonDialog : IDialogContentComponent<Person>
{
[Parameter] public Person Content { get; set; } = default!;
[CascadingParameter] public FluentDialog Dialog { get; set; } = default!;
private async Task SaveAsync()
{
await Dialog.CloseAsync(Content);
}
private async Task CancelAsync()
{
await Dialog.CancelAsync();
}
}
IDialogService:[Inject] private IDialogService DialogService { get; set; } = default!;
private async Task ShowEditDialog()
{
var dialog = await DialogService.ShowDialogAsync<EditPersonDialog, Person>(
person,
new DialogParameters
{
Title = "Edit Person",
PrimaryAction = "Save",
SecondaryAction = "Cancel",
Width = "500px",
PreventDismissOnOverlayClick = true,
});
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
premium-frontend-ui
232github/awesome-copilot
Frontendsame repojava-springboot
52github/awesome-copilot
Backendsame repofrontend-design
651anthropics/claude-code
Frontendsame categoryui-animation
238mblode/agent-skills
Frontendsame categoryantigravity-design-expert
203sickn33/antigravity-awesome-skills
Frontendsame categoryhigh-end-visual-design
189leonxlnx/taste-skill
Frontendsame categoryReviews
4.7★★★★★55 reviews- CChinedu Mehta★★★★★Dec 28, 2024
Solid pick for teams standardizing on skills: fluentui-blazor is focused, and the summary matches what you get after install.
- PPratham Ware★★★★★Dec 20, 2024
Useful defaults in fluentui-blazor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- LLi Verma★★★★★Dec 20, 2024
fluentui-blazor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- CChen Johnson★★★★★Dec 16, 2024
fluentui-blazor has been reliable in day-to-day use. Documentation quality is above average for community skills.
- DDhruvi Jain★★★★★Dec 12, 2024
Keeps context tight: fluentui-blazor is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAarav Ramirez★★★★★Nov 19, 2024
We added fluentui-blazor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- LLi Thomas★★★★★Nov 11, 2024
fluentui-blazor reduced setup friction for our internal harness; good balance of opinion and flexibility.
- CChinedu Iyer★★★★★Nov 7, 2024
Useful defaults in fluentui-blazor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- CCamila Chen★★★★★Nov 7, 2024
I recommend fluentui-blazor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- CChen Malhotra★★★★★Nov 7, 2024
fluentui-blazor fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 55
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.