Run any Skill in Manus with one click

$pwd:

dotnet-managedcode-mimetypes

Name: Dotnet Managedcode Mimetypes
Author: managedcode

// Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.

Run Skill in Manus

$ git log --oneline --stat

stars:40

forks:8

updated:April 19, 2026 at 19:47

File Explorer

2 files

SKILL.md

readonly

name	dotnet-managedcode-mimetypes
description	Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.
compatibility	Requires a .NET application that integrates ManagedCode.MimeTypes or evaluates MIME type mapping behavior.

ManagedCode.MimeTypes

Trigger On

integrating ManagedCode.MimeTypes into upload or download flows
mapping file extensions to content types in APIs or background processing
reviewing content-type handling for files, blobs, or attachments
documenting a reusable MIME-type decision point in a .NET application

Workflow

Identify where the application needs stable MIME-type decisions:
- upload validation
- download response headers
- storage metadata
- attachment processing
Centralize content-type mapping instead of scattering ad-hoc string tables across the codebase.
Use one library boundary for extension and MIME lookups.
Validate the extensions and media types that matter to the product.
Document any product-specific overrides separately from the library defaults.

flowchart LR
  A["File name or extension"] --> B["ManagedCode.MimeTypes lookup"]
  B --> C["Resolved MIME type"]
  C --> D["Upload validation, storage metadata, or HTTP response"]

Deliver

guidance on where MIME lookup belongs in application code
recommendations for centralized content-type decisions
validation expectations for real file types used by the product

Validate

MIME mapping is not duplicated across multiple services or controllers
important file types are verified explicitly
response or storage code uses the resolved type consistently

related-skills.json

same repository

dotnet-analyzer-config.md

from "managedcode/PrompterOne"

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific purpose.

2026-04-1940

dotnet-aspnet-core.md

from "managedcode/PrompterOne"

Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

2026-04-1940

dotnet-biome.md

from "managedcode/PrompterOne"

Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. Use when a repo prefers a modern all-in-one CLI over a larger ESLint plus Prettier style stack.

2026-04-1940

dotnet-blazor.md

from "managedcode/PrompterOne"

Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices.

2026-04-1940

dotnet-eslint.md

from "managedcode/PrompterOne"

Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. Use when a repo needs a configurable CLI lint gate for frontend correctness, import hygiene, unsafe patterns, or framework-specific rules.

2026-04-1940

dotnet-htmlhint.md

from "managedcode/PrompterOne"

Use HTMLHint in .NET repositories that ship static HTML output or standalone frontend templates. Use when a repo needs a focused CLI lint gate for DOM structure, invalid attributes, and basic HTML correctness checks on static pages.

2026-04-1940

package.json

"author": "managedcode"

"repository": "managedcode/PrompterOne"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	dotnet-managedcode-mimetypes
description	Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.
compatibility	Requires a .NET application that integrates ManagedCode.MimeTypes or evaluates MIME type mapping behavior.

ManagedCode.MimeTypes

Trigger On

integrating ManagedCode.MimeTypes into upload or download flows
mapping file extensions to content types in APIs or background processing
reviewing content-type handling for files, blobs, or attachments
documenting a reusable MIME-type decision point in a .NET application

Workflow

Identify where the application needs stable MIME-type decisions:
- upload validation
- download response headers
- storage metadata
- attachment processing
Centralize content-type mapping instead of scattering ad-hoc string tables across the codebase.
Use one library boundary for extension and MIME lookups.
Validate the extensions and media types that matter to the product.
Document any product-specific overrides separately from the library defaults.

flowchart LR
  A["File name or extension"] --> B["ManagedCode.MimeTypes lookup"]
  B --> C["Resolved MIME type"]
  C --> D["Upload validation, storage metadata, or HTTP response"]

Deliver

guidance on where MIME lookup belongs in application code
recommendations for centralized content-type decisions
validation expectations for real file types used by the product

Validate

MIME mapping is not duplicated across multiple services or controllers
important file types are verified explicitly
response or storage code uses the resolved type consistently

dotnet-managedcode-mimetypes

ManagedCode.MimeTypes

Trigger On

Workflow

Deliver

Validate

More from this repository

More from this repository

ManagedCode.MimeTypes

Trigger On

Workflow

Deliver

Validate