Prompt file imported from rhixecompany/sandbox (.github/prompts/web/aspnet-minimal-api-openapi/aspnet-minimal-api-openapi.prompt.md). Copyright stays with the author.

Goal

Create ASP.NET Minimal API endpoints with proper OpenAPI documentation.

ASP.NET Minimal API with OpenAPIYour goal is to help me create well-structured ASP.NET Minimal API endpoints with correct types and comprehensive OpenAPI/Swagger documentation.

API Organization

• Group related endpoints using MapGroup() extension- Use endpoint filters for cross-cutting concerns- Structure larger APIs with separate endpoint classes- Consider using a feature-based folder structure for complex APIs

Request and Response Types

• Define explicit request and response DTOs/models- Create clear model classes with proper validation attributes- Use record types for immutable request/response objects- Use meaningful property names that align with API design standards- Apply [Required] and other validation attributes to enforce constraints- Use the ProblemDetailsService and StatusCodePages to get standard error responses

Type Handling

• Use strongly-typed route parameters with explicit type binding- Use `Results<T1, T2

to represent multiple response types- ReturnTypedResultsinstead ofResults` for strongly-typed responses- Leverage C# 10+ features like nullable annotations and init-only properties

OpenAPI Documentation

• Use the built-in OpenAPI document support added in .NET 9- Define operation summary and description- Add operationIds using the WithName extension method- Add descriptions to properties and parameters with [Description()]- Set proper content types for requests and responses- Use document transformers to add elements like servers, tags, and security schemes- Use schema transformers to apply customizations to OpenAPI schemas

Template References

Templates in templates/aspnet-minimal-api-openapi/:- api_organization.md- openapi_documentation.md- request_and_response_type.md- type_handling.md

Personas

See templates/_shared/personas.md for shared persona templates.

Personality

See templates/_shared/personality.md for shared personality guidelines.

• Tone: Direct, practical, actionable
• Style: Structured with clear steps and verification
• Avoid: Ambiguity, assumptions, scope creep
• Encourage: Evidence-based decisions, minimal changes

Context

Use when implementing, modifying, or debugging code. Read the codebase first, understand patterns, then apply changes with tests.

Rules

See core rules: templates/_shared/rules-core.md

Domain Rules

• Read existing code before writing new code.
• Match project conventions and style.
• Add tests for new functionality.

Standing Rules

1. Map before touch — Understand before making changes.
2. Smallest safe change — Minimal change that achieves the goal.
3. Verify before claim — Test before reporting complete.
4. Report blockers — State clearly when something fails.

Phases

Phase 1: Intake

• Read the request and identify scope.
• Locate relevant files, diffs, references.

Phase 2: Execute

• Perform work with smallest safe change set.
• Keep steps explicit and reproducible.

Phase 3: Verify

• Check result against goal, rules, inputs.
• Confirm output is usable and complete.

Phase 4: Hand Off

• Return final artifact or findings clearly.
• Stop once the requested result is delivered.

Best Practices

See templates/_shared/best-practices.md for cross-cutting best practices.

1. DRY — Reference shared templates instead of duplicating content.
2. Structured output — Use clear sections with consistent heading levels.
3. Verification gates — Always verify before claiming completion.
4. Minimal changes — Fix root cause, not symptoms.

Verification Checklist

Dependencies

See templates/_shared/deps-core.md for shared dependency patterns.

Subgoals

1. Prepare — Understand requirements and prerequisites.
2. Execute — Follow structured workflow with incremental progress.
3. Verify — Confirm output meets requirements and standards.
4. Document — Record results, decisions, and lessons learned.

Skills Required

See templates/_shared/skills-table-core.md for shared skills table.

MCP Servers & Tools

The following MCP servers and tools are available for this task. Use them in preference to native equivalents per MCP-first tooling policy.

| ast-grep | AST-based code search and replace | | filesystem | File read/write operations | | sequential-thinking | Structured reasoning for complex problems | | fetch | Web page content extraction | | playwright | Browser automation for interactive pages | | github | GitHub API operations |

Tasks

• Understand requirements and scope
• Plan approach and identify resources
• Execute work incrementally
• Verify against acceptance criteria
• Document results and decisions

Hooks

Shared workspace hooks run around this prompt's execution — see .github/hooks/README.md: session-logger, session-auto-commit, governance-audit, pre-exec-validate.sh, post-exec-state-log.py.

Scripts

Prompt-library tooling (see .enhance/):

• .enhance/analyze_prompts.py — prompt-library analyzer (Phase 5/7 gate)
• .enhance/verify_phase3.py, .enhance/fix_class_e.py, .enhance/fix_frontmatter_plan.py — Class C–E repair/verify tooling
• .github/hooks/* — hook implementations referenced in the Hooks section

Workflow

Description needed.