Menú
Add a nav item to the Blazor NavMenu.razor for a new feature, inside the correct AuthorizeView policy block and section, following the existing nav structure.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | umbrella-blazor-register-nav-item |
| description | Add a nav item to the Blazor NavMenu.razor for a new feature, inside the correct AuthorizeView policy block and section, following the existing nav structure. |
Add a navigation link for a new feature to NavMenu.razor, placed inside the correct <AuthorizeView> policy block and logical section group. Nav items are always controlled by <AuthorizeView> — they are only rendered for users who satisfy the policy, matching the [Authorize] policy applied to the index and manage pages.
Web\<AppName>.Web.Client\Layout\Shared\NavMenu.razor in full to understand the existing structure — how sections are grouped with <div class="nav-header">, how <AuthorizeView> blocks are arranged by policy, and the naming/icon conventions.<AuthorizeView> block matches the policy used by the new feature's index page. If no matching block exists, a new one must be added.Find the <AuthorizeView Policy="@<AppName>PolicyNames.<Policy>"> block that matches the policy on the new feature's pages. The nav item goes inside this block.
<AuthorizeView Policy="@SharedPolicyNames.<Policy>" Context="<contextVarName>">
<div class="nav-header">Section Name</div>
<!-- existing items -->
<!-- ADD HERE, in alphabetical order by label -->
<div class="nav-item">
<NavLink class="nav-link" href="/admin/<route-plural>">
<i class="fas fa-<icon-name>" aria-hidden="true"></i>
<span><Label></span>
</NavLink>
</div>
</AuthorizeView>
Rules:
<div class="nav-item"> in alphabetical order by label within the same contiguous group and authorization block. Preserve nested policy blocks and established section structure; do not globally reorder unrelated navigation while adding one item.href must match the index page route exactly (e.g. /admin/industries).<span> label is the human-readable plural name of the feature (e.g. Industries, Career Quiz Questions).aria-hidden="true" on the icon element is required for accessibility.<div class="nav-header"> unless creating an entirely new section — use the existing section header.Add a new block at the appropriate position in the nav hierarchy:
<AuthorizeView Policy="@SharedPolicyNames.<Policy>" Context="<policy>Context">
<div class="nav-header"><Section Name></div>
<div class="nav-item">
<NavLink class="nav-link" href="/admin/<route-plural>">
<i class="fas fa-<icon-name>" aria-hidden="true"></i>
<span><Label></span>
</NavLink>
</div>
</AuthorizeView>
The Context attribute value must be unique within the file — use a descriptive name (e.g. siteSettingsContext, adminContext).
Use a FontAwesome Free icon that relates to the feature's subject matter. Browse at fontawesome.com/icons (free filter). Common examples from the codebase:
| Feature type | Icon |
|---|---|
| Industry / sector | fa-industry |
| People / users | fa-users |
| Documents | fa-file-alt |
| Settings | fa-cog |
| Education | fa-graduation-cap |
| Messages | fa-envelope |
| Charts / analytics | fa-chart-bar |
| Questions / quiz | fa-question-circle |
If unsure, check what icon an analogous existing feature uses.
Before finishing, read .ai-shared\bundles\umbrella\analyzer-compatibility.md and build the affected projects with their installed analyzers enabled. Treat diagnostics introduced by the generated or changed code as defects in this workflow.
<div class="nav-item"> is inside a <AuthorizeView> block whose policy matches the [Authorize] attribute on the index and manage pages.href on the <NavLink> matches the index page route.aria-hidden="true".<div class="nav-header"> was added unless the feature genuinely belongs to a new section that didn't previously exist.Add an EF Core database migration with auto-detection of the migrations project, startup project, and DbContext. Reports generated and modified files and warns on empty migrations.
Generate integration tests for a concrete API controller derived from UmbrellaGenericRepositoryDataServiceApiController (Pattern 2, backing controller service), covering every testable response status code per endpoint including ExistsById and TotalCount. Resolves enablement and authorization flags on the backing data service. Use after integration test infrastructure exists.
Generate integration tests for a concrete API controller derived from UmbrellaGenericRepositoryApiController (Pattern 1, direct repository), covering every testable response status code per endpoint: success paths, 401/403 authorization, 404, 405 disabled endpoints, 409 concurrency via stamp rotation, 400/422 validation, and optional 500. Use after integration test infrastructure exists.
Migrate AutoMapper Profile classes to Mapperly source-generated mappers, following the Umbrella catalog pattern. Covers ForMember translation, AfterMap, Ignore, flattening detection, DI rewiring, and AutoMapper removal.
Scaffold API model records (request/response types) for a new feature, following the Umbrella shared models pattern with optional base class hierarchies.
Scaffold Mapperly mapper classes that map between EF Core entities and API model records, or between client-side model types, following the Umbrella source-generated catalog pattern.