dotnet-sqlserver-pitfalls
Skill0 starsChanged 17 days agoNo licenceView on GitHub
Use when an EF Core / SQL Server / ASP.NET Core behavior looks impossible — retry not replaying a 500, enum value 0 not saved, removed child row still in DB, migration full of unrelated columns, CS0121 on EF.Functions, slow OR with EXISTS, Msg 1934 / 468 / 245 / 102 / 16202, multipart 400 bypassing exception filters, Swagger info leaking between hosts, authorization attribute silently ignored, green tests but 403 in production.
In this repository15 other files it gives its agents.
- clean-architectureSkill
- clean-codeSkill
- code-reviewSkill
- csharpSkill
- design-patternsSkill
- devops-tooling-pitfallsSkill
- gdscriptSkill
- luaSkill
- performanceSkill
- quality-verificationSkill
- reactSkill
- rustSkill
- svelteSkill
- typescriptSkill
- vueSkill
The file
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.

