How do I install the Write Dotnet Code skill?

Run npx skillmds@latest add dynamods/write-dotnet-code in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Write Dotnet Code safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write Dotnet Code?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Write Dotnet Code free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Write Dotnet Code?

dynamods (@dynamods) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Write Dotnet Code by dynamods — Agent Skill

Name: Write Dotnet Code
Author: dynamods

Write Dotnet Code

Write and review C#/.NET code in Dynamo following Dynamo coding standards, modern C# patterns, and repo conventions. Use this skill whenever writing C# code, reviewing a PR diff, designing types, managing PublicAPI surface files, choosing patterns, making performance decisions, or refactoring in the Dynamo codebase. Also use when asking about NUnit testing, async patterns, error handling, immutability, or security in Dynamo.

dynamods 8b89abf 2 files · 5.1 KB Updated Sep 17, 2026

File contents

Dynamo dotNET Expert

When to use

Writing or reviewing C#/.NET code in Dynamo.
Designing public APIs, choosing types, or making performance decisions.
Managing PublicAPI surface files.
Refactoring for modern C# patterns.
WPF/UI work in DynamoCoreWpf.

When not to use

Writing NUnit tests -- use the repo-specific dynamo-unit-testing skill instead.
Architecture / onboarding questions -- use the repo-specific dynamo-onboarding skill instead.
PR descriptions -- use the generate-pr-description skill instead.

Inputs expected

A C# file or diff to review, a feature requirement, or a question about .NET patterns in the Dynamo codebase.

Output format

Code suggestions with explanations, or a review with specific file/line references.

Workflow

Read before suggesting — read the relevant file(s) before proposing changes.
Repo conventions win — when repo standards conflict with generic .NET advice, follow the repo.
Check public API impact — any new public member needs a PublicAPI.Unshipped.txt entry.
Run quality checks — before finishing, verify against references/quality-checklist.md.

Quick Decision Guide

Situation	Action
Adding a public member	Update `PublicAPI.Unshipped.txt` — see `PublicAPI` guide in the Dynamo repo
DTO / immutable data	Use `record`
Small value type (< 16 bytes)	Use `readonly record struct`
Class not designed for inheritance	Mark `sealed`
Async in library code	Add `ConfigureAwait(false)`
User-facing string	Put it in a `.resx` file
New node	Add `.dyn`, `.md`, `.jpg` to `doc/distrib/NodeHelpFiles/`
Breaking public API change	File a GitHub issue first

Project Conventions

Dynamo Coding Standards
Dynamo Naming Standards
.editorconfig in the repo root defines indent and encoding — check it before editing.
Security analyzers CA2327/CA2329/CA2330/CA2328 are treated as errors.

Naming

PascalCase for public members, classes, methods.
camelCase for private fields and local variables.
Prefix private fields with underscore only if the file already does so consistently.
XML documentation required on all public methods and properties.

Comments

Comments explain why, not what.

Tech Stack

	Dynamo
TFM	net10.0 (full UI: win-x64 only)
Test framework	NUnit
Build (full)	`msbuild src/Dynamo.All.sln`
Build (core)	`dotnet build src/DynamoCore.sln`
IDE	Visual Studio 2022

Assets & References

references/quality-checklist.md — Anti-patterns, security rules, file constraints, PR checklist
assets/csharp-patterns.md — Modern C#, type design, async, immutability, performance, WPF/UI, examples (lives in the Dynamo repo)
assets/publicapi-guide.md — PublicAPI.Unshipped.txt workflow, breaking changes, extend-only design (lives in the Dynamo repo)

Related Skills: clean-dotnet-code • generate-pr-description

---name: write-dotnet-codedescription: Write and review C#/.NET code in Dynamo following Dynamo coding standards, modern C# patterns, and repo conventions. Use this skill whenever writing C# code, reviewing a PR diff, designing types, managing PublicAPI surface files, choosing patterns, making performance decisions, or refactoring in the Dynamo codebase. Also use when asking about NUnit testing, async patterns, error handling, immutability, or security in Dynamo.---# Dynamo dotNET Expert## When to use- Writing or reviewing C#/.NET code in Dynamo.- Designing public APIs, choosing types, or making performance decisions.- Managing PublicAPI surface files.- Refactoring for modern C# patterns.- WPF/UI work in `DynamoCoreWpf`.## When not to use- Writing NUnit tests -- use the repo-specific `dynamo-unit-testing` skill instead.- Architecture / onboarding questions -- use the repo-specific `dynamo-onboarding` skill instead.- PR descriptions -- use the `generate-pr-description` skill instead.## Inputs expectedA C# file or diff to review, a feature requirement, or a question about .NET patterns in the Dynamo codebase.## Output formatCode suggestions with explanations, or a review with specific file/line references.---## Workflow1. **Read before suggesting** — read the relevant file(s) before proposing changes.2. **Repo conventions win** — when repo standards conflict with generic .NET advice, follow the repo.3. **Check public API impact** — any new public member needs a `PublicAPI.Unshipped.txt` entry.4. **Run quality checks** — before finishing, verify against [references/quality-checklist.md](./references/quality-checklist.md).---## Quick Decision Guide| Situation | Action ||---|---|| Adding a public member | Update `PublicAPI.Unshipped.txt` — see `PublicAPI` guide in the Dynamo repo || DTO / immutable data | Use `record` || Small value type (< 16 bytes) | Use `readonly record struct` || Class not designed for inheritance | Mark `sealed` || Async in library code | Add `ConfigureAwait(false)` || User-facing string | Put it in a `.resx` file || New node | Add `.dyn`, `.md`, `.jpg` to `doc/distrib/NodeHelpFiles/` || Breaking public API change | File a GitHub issue first |---## Project Conventions- [Dynamo Coding Standards](https://github.com/DynamoDS/Dynamo/wiki/Coding-Standards)- [Dynamo Naming Standards](https://github.com/DynamoDS/Dynamo/wiki/Naming-Standards)- `.editorconfig` in the repo root defines indent and encoding — check it before editing.- Security analyzers CA2327/CA2329/CA2330/CA2328 are treated as **errors**.### Naming- PascalCase for public members, classes, methods.- camelCase for private fields and local variables.- Prefix private fields with underscore only if the file already does so consistently.- XML documentation required on all public methods and properties.### CommentsComments explain *why*, not what.---## Tech Stack| | Dynamo ||---|--------|| TFM | net10.0 (full UI: win-x64 only) || Test framework | NUnit || Build (full) | `msbuild src/Dynamo.All.sln` || Build (core) | `dotnet build src/DynamoCore.sln` || IDE | Visual Studio 2022 |---## Assets & References- **[references/quality-checklist.md](./references/quality-checklist.md)** — Anti-patterns, security rules, file constraints, PR checklist- **assets/csharp-patterns.md** — Modern C#, type design, async, immutability, performance, WPF/UI, examples *(lives in the Dynamo repo)*- **assets/publicapi-guide.md** — PublicAPI.Unshipped.txt workflow, breaking changes, extend-only design *(lives in the Dynamo repo)*---**Related Skills:**clean-dotnet-code • generate-pr-description

Frequently asked questions