codegen
Skill54 starsChanged 2 months agoApache-2.0View on GitHub
Use for .NET code generation work with Roslyn, Microsoft.OpenApi, Razor templates, DTO/manager/controller generation, REST API generation, C# HttpClient generation, Angular/Axios TypeScript request clients, generated formatting, and deterministic output.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- vercel-labs/json-rendertheir own version, first seen Oct 29, 2026
- NVIDIA/nvcftheir own version, first seen Oct 13, 2026
- rsicarelli/fakttheir own version, first seen Oct 9, 2026
- s3s-project/s3stheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- vercel-labs/json-render★ 19ksame name
- s3s-project/s3s★ 315same name
- NVIDIA/nvcf★ 261same name
- rsicarelli/fakt★ 67same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Prefer Roslyn APIs for C# syntax, symbols, namespaces, usings, attributes, and type analysis.
- Very specific: line 18
Prefer Microsoft.OpenApi APIs for OpenAPI traversal, schemas, and operations.
- Distinctive: line 19
Keep parsing/model extraction in helpers and emitted output composition in generators or templates.
- Distinctive: line 20
Avoid brittle string parsing when a structured API is available.
- Distinctive: line 21
Keep generated output deterministic: stable ordering, whitespace, using lists, and no machine-specific paths.
- Distinctive: line 22
Use raw string literals for embedded multi-line generated source.
- Very specific: line 27
Add focused tests under tests/StudioMod.Tests/Generate.
- Very specific: line 28
Use fixture OpenAPI files under tests/StudioMod.Tests/Generate/Fixtures.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Generation
Workflow
- Inspect the relevant generator in
src/CodeGenerator/Generate. - Inspect helpers in
src/CodeGenerator/Helperbefore adding parsing logic. - Inspect templates in
src/CodeGenerator/Templateswhen output text changes. - Inspect regression tests in
tests/StudioMod.Tests/Generate.
Conventions
- Prefer Roslyn APIs for C# syntax, symbols, namespaces, usings, attributes, and type analysis.
- Prefer
Microsoft.OpenApiAPIs for OpenAPI traversal, schemas, and operations. - Keep parsing/model extraction in helpers and emitted output composition in generators or templates.
- Avoid brittle string parsing when a structured API is available.
- Keep generated output deterministic: stable ordering, whitespace, using lists, and no machine-specific paths.
- Use raw string literals for embedded multi-line generated source.
- Be careful around nullable values, enums, file uploads, path/query/body parameter placement, and special OpenAPI names.
Tests
- Add focused tests under
tests/StudioMod.Tests/Generate. - Use fixture OpenAPI files under
tests/StudioMod.Tests/Generate/Fixtures. - For Roslyn helpers, use small source snippets that exercise the syntax or semantic case.
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
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.

