csharp-docs
Ensure that C# types are documented with XML comments and follow best practices for documentation.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- C# Documentation Best Practices
- Guidance for all APIs
- Methods
- Constructors
- Properties
- Exceptions
Public members should be documented with XML comments. It is encouraged to document internal members as well, especially if they are complex or not self-explanatory. Use to provide a brief, one sentence, description of what the type or member does. Start the summary with a present-tense, third-person verb. Use for additional information, which can include implementation details, usage notes, or any other relevant context. Use for language-specific keywords like null, true, false, int, bool, etc. Use for inline code snippets. Use for usage examples on how to use the member. Use for code blocks. tags should be placed within an tag. Add the language of the code example using the language attribute, for example, . Use to reference other types or members inline (in a sentence). Use for standalone (not in a sentence) references to other types or members in the "See also" section of the online docs. Use to inherit documentation from base classes or interfaces. Unless there is major behavior change, in which case you should document the differences. Use to describe method parameters. The description should be a noun phrase that doesn't specify the data type. Begin with an introductory arti
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- community/csharp-docs/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:54.117Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.