Patterns, gotchas and small wins from fifteen-odd years of .NET and web work — the Regira packages and modules, entity pipelines, editorial front-ends and everything between.
When an agent builds the app, a framework that owns the plumbing shrinks the review to the part that is your business. What to read first: which questions the API answers, what a save may change, and which rules run every time.
A coding agent built working apps on a framework it had never seen, without inventing a single method. The reason is documentation that lives with the code, is served one piece at a time, and tells the agent what to do next and how to check it worked.
Before an agent builds a bigger app, sort each request into what the framework provides, what the agent must assemble, and what is missing. A plan for a shopping-list app with sign-in, sharing, photos and offline use, and what changes when an app keeps growing after its first run.
Hand a coding agent a six-line brief and get a running .NET and Vue app, with sample data and a clickable UI, in about half an hour. Step by step, with no license and no account.
Know how many people read your site and where they come from, without a third-party script, a cookie or a consent banner. What the blog you are reading records, what it cannot, and how crawlers are kept out of the count.
A quick look at turning a flat collection with parent references into a navigable hierarchy, without writing recursion yourself.
Answer who reported to whom on any past date from the data you already store, with no history tables and no migrations. One dated relationship table and a single filter do it; Westeros supplies three centuries of test data.
A small tool that copies files between local disks, network shares and cloud storage, where a new copy job is a config entry, not new code. Built on one storage abstraction, so adding a backend is one small class.
One table for every customer, supplier and employee, with roles and alliances as dated relationships instead of extra tables. Tested on Westeros, where everyone knows who betrayed whom and when.
Keep file storage behind one interface and let each environment choose disk, network share or Azure in configuration. Tests run without cloud credentials, and moving your files later is a copy job, not a rewrite. Uploads are typed by the server, so none can pose as a page of your site.