Claude config: rules and guardrails for Claude Code on .NET + Angular projects

I work on.NET and Angular projects with Claude Code. For every new project I kept writing the same instructions again: which stack to use, how to handle Git, what Claude must never do on its own, how to ask questions. So I put all of it in one place: claude-config, a public template of rules plus a small Claude Code plugin.

Repository: https://github.com/AngeloDotNet/claude-config

Claude Code loads the files under.claude/rules/ by itself, so the rules are copied into each project and nothing is installed globally. The modules are:

Optional modules (email, infrastructure, feature workflow) live in.claude/rules-optional/ and are switched on only when a project needs them.

The rules are written in Italian, because that is the language I work in, while code, identifiers and commit messages stay in English. You can change that to suit your own team.

A few of the rules in core.md shape almost every session:

Written rules are only a suggestion, so the plugin turns the most important ones into hooks:

claude plugin marketplace add AngeloDotNet/claude-config claude plugin install kit-config@claude-config Enter fullscreen mode Exit fullscreen mode The current version is 1.8.0.

The documentation covers three situations:

The CLAUDE.md in each project holds only what is specific to that project. Choices such as architecture, ORM, database, multi-tenancy or the ASVS level are never assumed: the template asks for them and they are recorded once. The copia-regole.bat script copies the rules and root files into a project folder and can update the rules already present.

This is my own opinionated setup, not a universal standard. Some details are not yet verified against their sources, and the changelog says so openly. For example, the exact PostgreSQL row-level security syntax and passkey support in ASP.NET Core Identity on.NET 10 are marked to be checked the first time they are used. Treat the rules as a starting point and adapt them to your projects.

If you try it on a real project, I would like to hear what breaks first.