agentleFS
Sign inStart free
AterDevAterDev/Perigon.CLI/.agents/skills/blazor/SKILL.md

blazor

Skill54 starsChanged 2 months agoApache-2.0View on GitHub

Use 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.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. Mindrally/skills★ 275same name
    2. G1Joshi/Agent-Skills★ 15same name
    3. Sorcha-Platform/Sorcha★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read nearby Razor components and code-behind for local patterns.

    line 11
  2. Very specific:

    Check Program.cs and ServiceCollectionExtension.cs before changing service registration or middleware.

    line 12
  3. Distinctive:

    Read the CoreMod service/manager before putting workflow logic in UI code.

    line 13
  4. Distinctive:

    Keep Razor components focused on UI composition and user interaction.

    line 17
  5. Distinctive:

    Put reusable workflows in CoreMod services or managers.

    line 18
  6. Distinctive:

    Use Fluent UI Blazor components and icons consistently with surrounding pages.

    line 19
  7. Distinctive:

    Use scoped managers/services registered through the app startup path.

    line 21
  8. Distinctive:

    Keep UI text product-facing, not implementation-facing.

    line 23
  9. Very specific:

    Use @Localizer.Get(Localizer.Key) for user-facing labels.

    line 27
  10. Very specific:

    Add new strings to both src/Share/Localizer.zh-CN.resx and src/Share/Localizer.en-US.resx.

    line 28
  11. Distinctive:

    Prefer testing workflow behavior at the CoreMod service/manager layer.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blazor And Fluent UI Development

Workflow

  1. Identify the page, component, layout, or service under src/Apps/Dashboard.
  2. Read nearby Razor components and code-behind for local patterns.
  3. Check Program.cs and ServiceCollectionExtension.cs before changing service registration or middleware.
  4. 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.resx and src/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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free