Index of every page on this site: llms.txt
All skills
Run it yourself

Expert workflow for ASP.NET Framework (.NET Framework 4.x) web apps using Vue 2, Vue 3, or Alpine.js with Razor and Web API. Use when integrating frontend frameworks into ASP.NET Framework, choosing framework patterns, implementing API and anti-forgery flows, troubleshooting runtime/version setup, or answering support and lifecycle questions with official Microsoft Learn .NET Framework documentation.

Use this Skill: https://skilld.dev/gh/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈108 tokens for metadata: the name and description. ≈683 when used: this file. ≈12k more on demand in 6 files.

Description uses 5.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈431 characters, or 5.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

ASP.NET Framework Frontend

Overview

Use this skill for ASP.NET Framework frontend architecture and implementation. Keep framework-specific code guidance in sync with official Microsoft Learn documentation before giving final recommendations.

Core Workflow

  1. Identify stack and runtime.
  • Confirm ASP.NET Framework (MVC 5, Web API 2, Web Forms, System.Web) versus ASP.NET Core.
  • Detect target runtime from .csproj, packages.config, or web.config.
  • State assumptions when the runtime is unknown.
  1. Choose frontend strategy.
  • Choose Vue 2 for legacy maintenance and Options API continuity.
  • Choose Vue 3 for new/expanded client-side features and composables.
  • Choose Alpine.js for lightweight progressive enhancement in server-rendered pages.
  • Use Vue + Alpine only with strict root-element isolation.
  1. Implement ASP.NET integration path.
  • Define bundles in BundleConfig.cs and toggle optimization by environment.
  • Pass server data to client using strongly typed models or serialized payloads.
  • Use Web API endpoints with anti-forgery validation on state-changing requests.
  • Centralize fetch helpers and error handling in shared JavaScript utilities.
  1. Validate against official documentation.
  • Load references/microsoft-learn-dotnet-framework.md for install/version/support questions.
  • Confirm lifecycle and support answers against policy pages before finalizing.
  • Use absolute dates when reporting end-of-support milestones.
  1. Deliver response.
  • Provide minimal safe implementation steps first.
  • Separate maintenance guidance from optional migration guidance.
  • Add direct documentation links used for the recommendation.

Guardrails

  • Do not mix ASP.NET Core implementation details into ASP.NET Framework instructions.
  • Do not use v-html or x-html for untrusted input.
  • Do not omit anti-forgery token handling for POST, PUT, or DELETE.
  • Do not recommend Vue 2 for new greenfield work unless constraints require it.

Reference Loading Order

  1. references/aspnet-integration.md
  • Use for ASP.NET MVC/Web API + frontend integration structure.
  1. Framework-specific reference
  • references/vue2-best-practices.md
  • references/vue3-best-practices.md
  • references/alpinejs-best-practices.md
  1. Official documentation map
  • references/microsoft-learn-dotnet-framework.md
  • Use for runtime versions, installation, API browser, and lifecycle policy routing.

Quick Checklist

  • Confirm runtime target (.NET Framework 4.x variant).
  • Select Vue 2, Vue 3, or Alpine with explicit rationale.
  • Implement bundle strategy and server-to-client data transfer.
  • Include anti-forgery flow in API calls.
  • Verify support/lifecycle answers with official policy links.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts8mo4 checks · Risk SAFE
  • Gen Agent Trust Hub8mo

    This skill provides expert guidance for integrating Vue and Alpine.js into ASP.NET Framework applications. It correctly emphasizes critical security measures like anti-forgery tokens and XSS protection. All external links and dependencies are from trusted or well-known industry sources.

  • Socket8mo

    No alerts

  • Snyk8mo

    Risk: LOW · No issues

  • Runlayer8mo

    7 files scanned · No issues

Signed by skilld at ea85083. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 10 months ago

README badge

README badge for rscoopcur/aspnet-framework-skills/aspnet-framework-frontend