Install
$ agentstack add skill-benknightdark-neo-skills-neo-dotnet-mvc ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
.NET MVC Expert Skill
Trigger On
- The user requests to create, debug, refactor, or review ASP.NET Core MVC applications.
- The project contains
ViewsandControllersdirectories and inherits fromController(notControllerBase). - The target framework is .NET 6.0 (LTS) and above.
- There is a need to optimize Server-Side Rendering (SSR) performance or improve view organizational structure.
Workflow
- Perceive (Architecture Awareness):
- Check
.csprojto identifyTargetFramework. - Analyze
Views/Sharedto confirm existing configurations for layouts and partial views. - Identify whether Tag Helpers and static resource versioning are enabled.
- Reason (Planning Phase):
- Evaluate whether complex Partial Views need to be migrated to View Components.
- Determine whether custom Tag Helpers are needed to simplify UI logic.
- Choose an appropriate ViewModel organization method based on project scale.
- Act (Execution Phase):
- Write high-quality controllers and strongly-typed views.
- Implement data validation (Data Annotations) and integrate them into ViewModels.
- Configure and use Tag Helpers to ensure the semantic correctness of forms and links.
- Validate (Standard Validation):
- Validate whether page rendering conforms to the expected HTML structure.
- Check whether model validation correctly operates on both the frontend and backend.
- Ensure Antiforgery tokens are correctly applied to all state-modifying requests.
Feature Roadmap (.NET 6 - 10)
.NET 6 & 7 (Foundation)
- Tag Helpers: Declarative HTML attribute extensions.
- View Components: Logic-driven UI block modularization.
- Cache Tag Helper: Server-side view fragment caching.
- Nullable Views: Better Razor null safety support.
.NET 8 & 9 (Productivity)
- Blazor Integration: Hybrid development support for MVC and Blazor components.
- Antiforgery Improvements: Global anti-forgery automatic validation optimization.
- Keyed Services in Controllers: Finer-grained dependency injection support.
- Native AOT for MVC: Metadata compilation optimization tailored for AOT.
.NET 10+ (Version-Specific Features)
- Extension Members for IHtmlHelper: Extending view helper functions.
- Advanced Serialization in Views: Performance optimization for large view models.
Coding Standards
- Strongly Typed Views: All views must have an explicit
@model. - ViewModel Separation: Strictly prohibit exposing database entities directly to views.
- Naming: View models must end with
ViewModel, action methods prioritize asynchronous patterns. - Formatting: Follow the Allman style and use Tag Helpers instead of HTML Helpers.
Deliver
- Version-Optimized MVC Code: Provide modernized controllers, models, and views suitable for the target version.
- UI Architecture Suggestions: Provide design suggestions for view components and Tag Helpers.
- Validation Logic: Provide a complete model validation and error prompting implementation plan.
Validate
- Ensure the code complies with C# 10+ syntax standards.
- Validate endpoints correctly handle model validation failures and return form states.
- Confirm static resources and scripts are correctly cached via
asp-append-version.
Documentation
Official References
Internal References
- [MVC Coding Style and Naming Conventions](reference/coding-style.md)
- [MVC Anti-Patterns and Best Practices](reference/anti-patterns.md)
- [MVC Modern Patterns Guide](reference/patterns.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Benknightdark
- Source: Benknightdark/neo-skills
- License: MIT
- Homepage: https://neo-blog-iota.vercel.app/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.