t1-api-integration-contracts

星标0

分支0

更新时间2026年7月14日 01:00

T1 API and integration contract playbook. Use for HTTP, RPC, events, queues, database boundaries, authentication, or external-service changes.

安装

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

来源

lebobo88

lebobo88/orchestrator

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

下载

API and integration contracts

Identify producer, consumer, trust boundary, data schema, version/compatibility promise, and failure ownership.
Define valid/invalid inputs, outputs, status/error semantics, validation, authN/authZ, sensitive fields, and observability signals.
For side-effecting or retried operations, account for idempotency, ordering, timeout, retry, partial failure, and duplicate delivery where applicable.
Write contract-focused tests before implementation: success, validation/auth failure, dependency failure, and compatibility/regression behavior.
Do not silently introduce an external dependency, migration, credential, protocol, or breaking contract. Return JOB_BLOCKED for approval or researcher context when required.

同仓库更多 Skills

同仓库

browser-validator-core

lebobo88/orchestrator

Screenshot-first visual end-to-end validation policy for browser-rendered UI and webview jobs after verifier approval.

2026-07-180

build

lebobo88/orchestrator

Default engineering workflow. Classify a technical request, route it through the native T1/T2/T3 engineering fleet, and return only independently verified completion to the orchestrator.

2026-07-180

claude-operations

lebobo88/orchestrator

Safely operate Claude Code's opt-in advanced capabilities—sessions, worktrees, agent teams, Skills, MCP, plugins, hooks, Channels, schedules, goals, and Agent SDK integrations—when the user explicitly asks for one. Do not use for an ordinary build request.

2026-07-170

cross-vendor-judging

lebobo88/orchestrator

Routes selective local Codex plan, code, verification, and visual judgment with evidence-backed blocking and strict cost caps.

2026-07-170

design-core

lebobo88/orchestrator

Shared evidence, accessibility, context, and handoff rules for the local design-agent fleet.

2026-07-170

design-direction

lebobo88/orchestrator

Produces contextual creative theses and bounded visual directions without generic model defaults.

2026-07-170

name	t1-api-integration-contracts
description	T1 API and integration contract playbook. Use for HTTP, RPC, events, queues, database boundaries, authentication, or external-service changes.
user-invocable	false

API and integration contracts

Identify producer, consumer, trust boundary, data schema, version/compatibility promise, and failure ownership.
Define valid/invalid inputs, outputs, status/error semantics, validation, authN/authZ, sensitive fields, and observability signals.
For side-effecting or retried operations, account for idempotency, ordering, timeout, retry, partial failure, and duplicate delivery where applicable.
Write contract-focused tests before implementation: success, validation/auth failure, dependency failure, and compatibility/regression behavior.
Do not silently introduce an external dependency, migration, credential, protocol, or breaking contract. Return JOB_BLOCKED for approval or researcher context when required.