Skip to content
TrustedSkillsbeta
Back to all skills

Modern Csharp Coding Standards

Checked
aaronontheweb·vlatest·backend·MIT

This skill suggests modern C# coding standards for improved code quality, readability, and maintainability in your backend projects.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aaronontheweb/dotnet-skills --skill modern-csharp-coding-standards -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aaronontheweb

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aaronontheweb/dotnet-skills at e426ed93a9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e426ed93a9
Manifest
skills/csharp-coding-standards/SKILL.md
Scanned
5 files, 1,546 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

Enforces modern C# coding standards, including formatting conventions, naming rules, and best practices for clean, maintainable code. It supports the latest language features and aligns with industry guidelines to ensure consistency across projects.

When to use it

  • Refactoring legacy C# codebases to follow current best practices
  • Ensuring team members adhere to a unified coding style in collaborative projects
  • Automating code reviews or pre-commit checks for C# files
  • Preparing code for open-source contributions or public repositories

Key capabilities

  • Enforces consistent naming conventions (e.g., PascalCase for types, camelCase for parameters)
  • Applies modern formatting rules aligned with .NET and Roslyn guidelines
  • Supports language features from recent C# versions (e.g., records, pattern matching)
  • Integrates with code analysis tools like Roslyn analyzers

Example prompts

  • "Format this C# class to follow modern coding standards."
  • "Check if this method adheres to current C# best practices."
  • "Enforce naming conventions for all public properties in this file."

Tips & gotchas

  • Ensure your project is targeting a recent version of the .NET SDK for full compatibility.
  • Custom rules may require configuration files or integration with tools like StyleCop or Roslyn analyzers.