Blazor And Fluent UI Development
SkillDev toolsUse for Blazor Server development with Fluent UI Blazor, Razor components, layouts, pages, scoped UI services, culture switching, localization, forms, loading/empty/error states, and Studio-style dashboard workflows.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Blazor And Fluent UI Development skill
What this skill tells your AI
The instructions your AI receives, as published by aterdev/perigon.cli in .agents/skills/blazor/SKILL.md and read by ahel’s review.
Workflow
- Identify the page, component, layout, or service under
src/Apps/Dashboard. - Read nearby Razor components and code-behind for local patterns.
- Check
Program.csandServiceCollectionExtension.csbefore changing service registration or middleware. - Read the CoreMod service/manager before putting workflow logic in UI code.
Conventions
- Keep Razor components focused on UI composition and user interaction.
- Put reusable workflows in CoreMod services or managers.
- Use Fluent UI Blazor components and icons consistently with surrounding pages.
- Preserve app-level providers for message bars, toasts, dialogs, tooltips, menus, and theme.
- Use scoped managers/services registered through the app startup path; avoid ad hoc service construction.
- Make loading, empty, success, and error states explicit for data and form flows.
- Keep UI text product-facing, not implementation-facing.
Localization And Validation
- Use
@Localizer.Get(Localizer.Key)for user-facing labels. - Add new strings to both
src/Share/Localizer.zh-CN.resxandsrc/Share/Localizer.en-US.resx. - Prefer testing workflow behavior at the CoreMod service/manager layer. Run the Dashboard manually only when the UI change is risky or the user asks.
Signals
- GitHub stars
- 54
- Forks
- 7
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
blazor- Source
- github.com/aterdev/perigon.cli