scaffold-minimal

Convert ASP.NET controllers to minimal API endpoints with OpenAPI and Scalar support.

1|Updated May 30, 2026
One-click install
npx skills add https://github.com/FixPortal/fixportal-claude-skills --skill scaffold-minimal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-minimal
Source: https://github.com/FixPortal/fixportal-claude-skills/tree/main/skills/scaffold-minimal
Command: npx skills add https://github.com/FixPortal/fixportal-claude-skills --skill scaffold-minimal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert traditional ASP.NET controllers to minimal API endpoints with OpenAPI and Scalar support, simplifying modernization and reducing boilerplate.

Core Features & Use Cases

  • Convert Controller classes to minimal API endpoint groups in an Endpoints/ folder
  • Preserve route templates and HTTP methods, and lift constructor dependencies into endpoint mappings
  • Update Program.cs to enable OpenAPI/Scalar references and remove outdated controller wiring
  • Use when asked to convert controllers, move to minimal APIs, or add OpenAPI/Scalar

Quick Start

Convert an ASP.NET project’s controllers to minimal APIs and enable OpenAPI/Scalar integration.

Frequently Asked Questions about scaffold-minimal

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

FAQPage Schema
How do I convert ASP.NET controllers to minimal APIs?

To convert ASP.NET controllers to minimal APIs, the Skill transforms controller classes into endpoint groups in an Endpoints/ folder. It preserves route templates, HTTP methods, and lifts constructor dependencies into the new endpoint mappings.

What is the best way to add Scalar and OpenAPI to a minimal API project?

Adding Scalar and OpenAPI to a minimal API project involves updating Program.cs. The Skill configures the necessary OpenAPI and Scalar references automatically while removing outdated controller wiring during the migration.

Can I migrate a controller-heavy ASP.NET project to minimal APIs without losing routes?

Migrating a controller-heavy ASP.NET project to minimal APIs preserves your existing routes. The Skill maps route templates and HTTP methods directly to the new minimal API endpoints, ensuring functionality remains intact.

Does converting controllers to minimal APIs delete the original Controllers folder?

Converting controllers to minimal APIs deletes the original Controllers/ folder, but only when it is empty. This ensures a clean project structure after all controller classes have been successfully transformed into endpoints.

When should I migrate from ASP.NET controllers to minimal API endpoints?

You should migrate from ASP.NET controllers to minimal API endpoints when modernizing existing controller-heavy projects to reduce boilerplate. It is also ideal when specifically asked to use minimal APIs or add Scalar documentation.