Free 10-day email course
Claude Code for
.NET Developers
The exact workflow I use to ship production .NET and frontend applications with Claude Code. From a plan file that survives sessions to reviews running in CI. One lesson a day for ten days. This course has a value of $500, but is free!
Free · No credit card · Unsubscribe anytime · Join 25,000+ developers already reading
- 10 lessons
- · one a day
- ~5-10 min each
- · Day 2 will change how you work with AI
- 1 task per lesson
- · on your own codebase
Not a .NET developer? Everything that makes Claude Code work through this course: context management, models and effort, plan mode, permissions, subagents, MCP servers, hooks, headless CI — is identical in every language. Only the examples are C#. Swap dotnet test for your own test command and the whole course transfers.
Where you end up
Before the course: you feel like Claude Code is just another agent that can edit your files. By Day 10, it's a production system — and you built it with me.
Before
- One giant session that gets worse the longer it runs
- Re-explaining your architecture in every new chat
- You run the 10th iteration for Claude to finally understand what you want to build
- Claude leaking your secrets without asking
- Claude writing AI slop code. You can't improve the quality
After
- Plan files that survive sessions, machines, and repositories
- Your conventions loaded automatically, every session
- Steal my process of building production-ready fullstack apps with Claude
- Make Claude respect your security rules and run only allowed commands
- Pick the right model at the right effort for each task
- Hooks and reviews holding the bar without you watching
- Claude writing code, testing and reviewing while you sleep
What you build, in six layers
Each layer sits on the one before it. Nothing is theory — every lesson ends with one task you run on your own solution.
The workflow
Day 2
Ideas become plan files that survive sessions, machines, and repositories — so work is never trapped in one chat.
The rules
Day 3
CLAUDE.md, scoped rule files, and skills, so every session starts with your conventions already loaded.
The habits
Days 4–6
Context hygiene, the right model at the right effort, plan mode and permissions — the difference between a tool and a senior teammate.
The team
Days 7–8
Subagents, dynamic workflows, git worktrees, and MCP connections to your database, GitHub, and browser.
The gates
Day 9
Hooks and reviews that hold your quality bar without you having to watch every diff.
The autopilot
Day 10
Recurring work running in CI and the cloud, with controls you can reach from your phone.
The ten lessons
Here is every lesson, in the order it arrives.
Getting Started with Claude Code for .NET Developers
Learn how to set up Claude Code for .NET development: install the Desktop app, run your first session on a real solution, and stay in control with permissions.
The Production Workflow: Shipping Real Features with Claude Code
Learn the production workflow for Claude Code in .NET: a five-phase process from requirements to deployment, driven by a plan file your whole team can follow.
CLAUDE.md and Skills: Teach Claude Your .NET Architecture
Learn how to configure CLAUDE.md and Claude Skills for .NET projects: project rules, scoped rule files, and reusable skills that generate code your way.
Claude Code Context Management: Why Long Sessions Get Dumber
Learn how the Claude Code context window works and how to manage it: @file references, /clear, /compact, and /context for consistent code quality in .NET projects.
What you actually end up writing
Not prompts you paste once and lose. Small, committed files that make every future session behave — checked into your repository and shared with your team.
CLAUDE.md — your architecture, as rules
Including the patterns you explicitly ban.
.claude/settings.json — trust, scoped
Safe commands run without asking. Irreversible ones never run.
## Tech Stack
- .NET 10, ASP.NET Core Minimal APIs
- EF Core, PostgreSQL
## Architecture
- Vertical Slice Architecture with feature folders
- Endpoints validate, then call one handler per use case
- Result<T> for business errors, never exceptions
## Patterns We Do NOT Use
- AutoMapper or any mapping library
- MediatR or any mediator library
- Repository pattern{
"permissions": {
"allow": [
"Bash(dotnet build)",
"Bash(dotnet test)",
"Bash(git status)",
"Bash(git diff:*)"
],
"deny": [
"Bash(git push:*)",
"Read(./appsettings.*.json)",
"Read(./.env)"
]
}
}What you need before Day 1
A paid Claude plan
Claude Code needs one. The $20 Pro plan covers this whole course and regular daily work on small and medium projects.
A real solution you know well
Not a toy project. The point is that you can judge whether Claude's answers are actually right, which is the skill this course trains.
Solid dev fundamentals
AI amplifies what you already know. The course gives you the workflow; your experience does the rest.
This is not for you if
- You want Claude to write code you will not read
- You are hoping AI substitutes for .NET fundamentals you do not have yet
- You will not run the exercises on a real codebase
Frequently Asked Questions
The course
What you need
Fit
Still have a question? Email me at [email protected].
Day 1 lands in your inbox in a few minutes
Ten lessons. One task each. Free, and yours to keep.
Free · No credit card · Unsubscribe anytime
By Anton Martyniuk · Microsoft MVP · 13+ years in production .NET
