/dotnet-run-file
Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
$ npx -y skills add NikiforovAll/claude-code-rules --skill dotnet-run-file --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/dotnet-run-file
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
SKILL.md
dotnet-run-file.SKILL.mdname: dotnet-run-file
description: Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
.NET Run Files
Run C# code directly without creating project files using .NET 10's `dotnet run file.cs` feature.
When to Use This Skill
Use this skill when the user wants to:
- Execute C# code quickly without creating a project
- Write one-liner scripts via stdin (ideal for Claude Code)
- Learn about run file directives (`#:package`, `#:sdk`, `#:property`)
- Create executable shell scripts in C#
- Convert a run file to a full project
Guide
For detailed examples and directives reference, load `references/guide.md`.
Quick Reference
Basic Execution
# Run a .cs file
dotnet run app.cs
# Run from stdin
echo 'Console.WriteLine("Hello");' | dotnet run -
# Multi-line via heredoc
dotnet run - << 'EOF'
var now = DateTime.Now;
Console.WriteLine($"Time: {now}");
EOFDirectives
#:package Humanizer@* // NuGet package (version required, wildcards ok)
#:sdk Microsoft.NET.Sdk.Web // SDK selection
#:property LangVersion preview // MSBuild property
#:project ../src/MyLib // Project reference
Convert to Project
dotnet project convert app.cs
Core Operations
1. Run a C# File
**Steps**: 1. Create a `.cs` file with your code (top-level statements supported) 2. Add directives at the top if needed (packages, SDK, properties) 3. Execute: `dotnet run filename.cs`
**Example**:
// hello.cs
Console.WriteLine("Hello from .NET!");dotnet run hello.cs
2. Execute via Stdin
**Purpose**: Run C# code without creating files - ideal for quick scripts and AI-assisted workflows.
**Patterns**:
# Simple one-liner
echo 'Console.WriteLine(Math.PI);' | dotnet run -
# With package
dotnet run - << 'EOF'
#:package Humanizer@*
using Humanizer;
Console.WriteLine(TimeSpan.FromMinutes(90).Humanize());
EOF
# Heredoc for multi-line
dotnet run - << 'EOF'
using System.Text.Json;
var obj = new { Name = "Test", Value = 42 };
Console.WriteLine(JsonSerializer.Serialize(obj));
EOFInteractive Flow
When user asks to run C# code without specifics:
1. Ask what they want to accomplish 2. Determine if stdin one-liner or file-based is better 3. For simple tasks → use stdin pattern 4. For complex tasks → create a `.cs` file 5. Add necessary directives based on requirements 6. Execute and show results
Claude Code Integration Tips
**For AI-assisted workflows**:
- Prefer stdin for quick calculations, data transformations, API calls
- Use heredoc syntax for multi-line code
- Output JSON for easy parsing: `dotnet run script.cs | jq .`
Read more
name: dotnet-run-file description: Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
.NET Run Files
Run C# code directly without creating project files using .NET 10's `dotnet run file.cs` feature.
When to Use This Skill
Use this skill when the user wants to:
- Execute C# code quickly without creating a project
- Write one-liner scripts via stdin (ideal for Claude Code)
- Learn about run file directives (`#:package`, `#:sdk`, `#:property`)
- Create executable shell scripts in C#
- Convert a run file to a full project
Guide
For detailed examples and directives reference, load `references/guide.md`.
Quick Reference
Basic Execution
# Run a .cs file
dotnet run app.cs
# Run from stdin
echo 'Console.WriteLine("Hello");' | dotnet run -
# Multi-line via heredoc
dotnet run - << 'EOF'
var now = DateTime.Now;
Console.WriteLine($"Time: {now}");
EOFDirectives
#:package Humanizer@* // NuGet package (version required, wildcards ok) #:sdk Microsoft.NET.Sdk.Web // SDK selection #:property LangVersion preview // MSBuild property #:project ../src/MyLib // Project reference
Convert to Project
dotnet project convert app.cs
Core Operations
1. Run a C# File
**Steps**: 1. Create a `.cs` file with your code (top-level statements supported) 2. Add directives at the top if needed (packages, SDK, properties) 3. Execute: `dotnet run filename.cs`
**Example**:
// hello.cs
Console.WriteLine("Hello from .NET!");dotnet run hello.cs
2. Execute via Stdin
**Purpose**: Run C# code without creating files - ideal for quick scripts and AI-assisted workflows.
**Patterns**:
# Simple one-liner
echo 'Console.WriteLine(Math.PI);' | dotnet run -
# With package
dotnet run - << 'EOF'
#:package Humanizer@*
using Humanizer;
Console.WriteLine(TimeSpan.FromMinutes(90).Humanize());
EOF
# Heredoc for multi-line
dotnet run - << 'EOF'
using System.Text.Json;
var obj = new { Name = "Test", Value = 42 };
Console.WriteLine(JsonSerializer.Serialize(obj));
EOFInteractive Flow
When user asks to run C# code without specifics:
1. Ask what they want to accomplish 2. Determine if stdin one-liner or file-based is better 3. For simple tasks → use stdin pattern 4. For complex tasks → create a `.cs` file 5. Add necessary directives based on requirements 6. Execute and show results
Claude Code Integration Tips
**For AI-assisted workflows**:
- Prefer stdin for quick calculations, data transformations, API calls
- Use heredoc syntax for multi-line code
- Output JSON for easy parsing: `dotnet run script.cs | jq .`
A collection of Claude Code recommendations and practices. Learn practical techniques to enhance your AI-assisted development workflow with Claude Code.
Other skills on claude-code-rules.
- /update-component-reference
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the website.
Open skill - /version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
Open skill - /spec-driven
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Open skill - /subagent-review
Review changed code for reuse, quality, and efficiency using three parallel disposable subagents. This skill should be used when the user says "review", "simplify", "code review", or wants a one-shot code review without persistent reviewers.
Open skill - /team-review
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to
Open skill - /handbook-discover
This skill should be used when users want to discover, browse, or audit cc-handbook marketplace plugins. Shows all available plugins with installation status, versions, and component breakdown (skills, agents, commands, MCP/LSP servers, hooks). Trigger phrases include "discover
Open skill

