status-code-decision-matrix

Choose HTTP status codes and response payload behavior for ASP.NET Core minimal APIs. Use for success and error branch semantics, problem details, conflicts, and compatibility exceptions.

Ir para a instalação

Repositório: kwkraus/edgefront-builder
Última atividade na origem: 20 de maio de 2026 às 20:18
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/kwkraus/edgefront-builder --skill status-code-decision-matrix

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

data-schema-migration

Design EF Core schema changes, constraints, and migrations for the backend data model. Use for entity updates, indexes, uniqueness rules, cascade behavior, and migration planning.

2026-06-04

api-contract-design

Design ASP.NET Core minimal API request and response contracts. Use for DTO shapes, route and verb decisions, OpenAPI metadata, and compatibility planning before implementation.

2026-05-20

api-test-strategy

Define focused tests for ASP.NET Core minimal APIs. Use for endpoint branch coverage, contract assertions, regression planning, and choosing the narrowest useful verification command.

2026-05-20

Ver todas deste repositório

Status Code Decision Matrix

When to Use

Endpoint behavior design or review in src/backend

Inconsistent status code handling across endpoints

PR review focused on HTTP semantics

Quick Checklist

Classify operation type and expected outcomes.

Assign canonical success status.

Assign specific 4xx/5xx statuses per failure cause.

Document and justify compatibility exceptions.

Deep Workflow

Classify operation type: read, create, replace, partial update, delete, command/action.

Enumerate all outcomes: success, validation failure, authz/authn failure, not found, conflict, transient dependency failure.

Select success status:

Read single/list: 200
Create: 201 with location when resource URI is available
Delete with no body: 204
Command accepted async: 202

Select client-error status:

Validation/input errors: 400 with problem details
Authn/authz: 401/403
Missing resource: 404
State/version conflict: 409

Select server/dependency status when applicable (500/503) and ensure no sensitive details leak.

Verify endpoint metadata and tests assert status + payload shape.

Decision Rules

Prefer specific 4xx statuses over generic 400 when cause is known.

Use 404 for unknown identifiers, not for authorization failures.

Use 409 when request is valid but current resource state prevents execution.

When existing clients depend on non-canonical behavior, keep compatibility and annotate a migration plan.

Completion Checks

Every expected branch maps to one status code.

Success paths and failure paths are both testable and documented.

Status behavior is consistent with existing endpoint patterns.

name	status-code-decision-matrix
description	Choose HTTP status codes and response payload behavior for ASP.NET Core minimal APIs. Use for success and error branch semantics, problem details, conflicts, and compatibility exceptions.
argument-hint	Describe the operation type, expected success result, known failure modes, and any client-compatibility constraints.