cad-todo-api

Guides learners through building an ASP.NET Core Web API exposing TODO CRUD endpoints over HTTP.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/jay-steenbergen/MSSAMentorAgent --skill cad-todo-api-jay-steenbergen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cad-todo-api
Source: https://github.com/jay-steenbergen/MSSAMentorAgent/tree/main/.github/skills/tracks/cloud-app-dev/cad-todo-api
Command: npx skills add https://github.com/jay-steenbergen/MSSAMentorAgent --skill cad-todo-api-jay-steenbergen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives mentors a structured, phase-by-phase build recipe for teaching learners how to create a working REST API in ASP.NET Core, turning abstract concepts like controllers, routing, and dependency injection into a running application the learner can test with curl or Swagger. ## Core Features & Use Cases - Five-phase build progression: Scaffold a webapi project, add a Todo model with an in-memory singleton store, build GET endpoints, add POST and DELETE, then smoke-test all four endpoints with expected status codes. - Concept naming and after-action reviews: Each phase lists concepts to name out loud (REST, DI, model binding, status codes), common gotchas, and reflection prompts aligned with the ride-along teaching method. - Use Case: A mentor guiding a learner who finished a console TODO app uses this recipe to move the same model behind HTTP, ending with a 4-endpoint API the learner can explain layer by layer. ## Quick Start Ask the mentor to start the cad-todo-api project and walk you through building a TODO REST API in ASP.NET Core step by step.

Frequently Asked Questions about cad-todo-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a REST API with ASP.NET Core controllers?

Scaffold a project with dotnet new webapi --use-controllers, create a model and an in-memory store registered as a singleton, then add a controller with GET, POST, and DELETE actions. The skill walks through this in five phases ending with a smoke test of all endpoints.

How do I add CRUD endpoints to an ASP.NET Core Web API?

Create a TodosController with [ApiController] and [Route] attributes, inject the store via the constructor, and implement GET /todos, GET /todos/{id}, POST /todos with [FromBody], and DELETE /todos/{id}. Return CreatedAtAction for POST and 204 No Content for DELETE.

Why does my ASP.NET Core project have no Controllers folder?

The default .NET 8 webapi template uses minimal APIs, which do not create a Controllers folder. Re-scaffold with dotnet new webapi --use-controllers to get the controllers-based project structure this skill uses.

Should I use a static class or dependency injection for an in-memory store?

Register the store as a singleton in the DI container with builder.Services.AddSingleton rather than using a static class. DI keeps the design testable and supports multiple instances later, and the controller receives the store through constructor injection.

What are the limitations of an in-memory TODO store?

All data is lost when the app restarts because state lives only in memory. For persistence across runs, the follow-on project cad-todo-api-ef adds EF Core with SQLite, and cad-deploy-app-service covers cloud deployment.