一键在 Manus 中运行任何 Skill

status-code-decision-matrix

星标0

分支0

更新时间2026年5月20日 20:18

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

kwkraus

kwkraus/edgefront-builder

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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.

同仓库更多 Skills

同仓库

api-contract-design

kwkraus/edgefront-builder

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-200

api-test-strategy

kwkraus/edgefront-builder

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-200

data-schema-migration

kwkraus/edgefront-builder

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-05-200

delegated-data-sync-pipeline

kwkraus/edgefront-builder

Design and implement the delegated Graph sync pipeline from fetch through normalization, upsert, and metrics recompute. Use for user-initiated registrations or attendance sync, idempotency, and atomic recomputation.

2026-05-200

deployment-safety-and-rollback

kwkraus/edgefront-builder

Define deployment safeguards, environment protections, and rollback readiness for CI/CD releases. Use when adding or reviewing release jobs, promotion controls, or recovery plans.

2026-05-200

domain-metrics-computation

kwkraus/edgefront-builder

Apply email and domain normalization plus session and series metric rules, including W1/W2 warm-account logic and internal-domain exclusion. Use for domain logic changes, recompute behavior, and mandatory unit-test coverage.

2026-05-200

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.

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.