verify-blazor

Validate Blazor component structure, DI patterns, and token handling in .razor files.

2|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/daeha76/RianFriends --skill verify-blazor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-blazor
Source: https://github.com/daeha76/RianFriends/tree/main/.claude/skills/verify-blazor
Command: npx skills add https://github.com/daeha76/RianFriends --skill verify-blazor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically checks Blazor components for adherence to best practices in structure, dependency injection, security, and naming conventions, preventing common errors and improving code maintainability.

Core Features & Use Cases

  • Component Structure Validation: Verifies correct placement of @code blocks and lifecycle method order.
  • DI Pattern Enforcement: Ensures dependencies are injected via interfaces.
  • Security Checks: Detects insecure token storage in localStorage or sessionStorage.
  • Naming Convention Checks: Confirms .razor files follow PascalCase.
  • Render Mode Verification: Checks for explicit @rendermode declarations.
  • Use Case: Before merging a pull request that introduces new Blazor components, run this Skill to catch potential issues related to code organization, security, and adherence to project standards.

Quick Start

Run the verify-blazor skill to check all .razor files in the current directory for adherence to coding standards.

Frequently Asked Questions about verify-blazor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Blazor component structure and enforce best practices?

You can validate Blazor component structure by running an automated check that verifies correct placement of @code blocks, lifecycle method order, and explicit @rendermode declarations in .razor files.

How do I check Blazor dependency injection patterns for interface compliance?

Checking Blazor dependency injection patterns involves scanning .razor and .razor.cs files to ensure all dependencies are injected via interfaces rather than concrete implementations.

How do I detect insecure authentication token storage in Blazor applications?

Detecting insecure authentication token storage in Blazor requires scanning code to identify tokens placed in localStorage or sessionStorage, which violates security best practices.

Can I automatically verify PascalCase naming conventions for Blazor .razor files?

Yes, you can automatically verify PascalCase naming conventions for Blazor .razor files by running a validation script that confirms all component filenames follow standard casing rules.

What is the best way to check Blazor render mode declarations before merging a pull request?

The best way to check Blazor render mode declarations before merging is to run an automated validation that scans .razor files for explicit @rendermode declarations to ensure components follow project standards.

When should I run Blazor code quality validation in my development workflow?

You should run Blazor code quality validation before merging a pull request that introduces new Blazor components, catching potential issues related to code organization, security, and adherence to standards.