agentleFS
Sign inStart free
Postpartum-genushyacinthus29Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-managedcode-mimetypes/SKILL.md

dotnet-managedcode-mimetypes

Skill13 starsChanged 8 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use one library boundary for extension and MIME lookups.

    line 26
  2. Distinctive:

    Document any product-specific overrides separately from the library defaults.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Identify where the application needs stable MIME-type decisions:
    • upload validation
    • download response headers
    • storage metadata
    • attachment processing
  2. Centralize content-type mapping instead of scattering ad-hoc string tables across the codebase.
  3. Use one library boundary for extension and MIME lookups.
  4. Validate the extensions and media types that matter to the product.
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free