菜单
Create and verify API contracts before endpoint implementation. Use for API routes, service interfaces, validation rules, error shapes, snapshots, and endpoint tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Define UI design specs, route contracts, visual states, accessibility expectations, and UI/API synchronization before frontend implementation. Use for new screens, redesigns, visual QA, or UI contract updates.
Automatically synchronize documentation with code changes across all project phases. Detects file changes, categorizes update types, auto-generates API docs, changelog entries, implementation handoffs, and validates cross-reference integrity. Use after any phase implementation.
Initialize and operate a project planning harness for Codex. Use this skill when the user types /init, asks to create a new project, add a feature, fix a bug, plan work, generate tests first, update docs, track phases, review changes, audit a repository, or manage architecture decisions.
Create premium frontend web designs and usable first-screen experiences for new websites, web apps, dashboards, tools, and landing pages. Use when Codex is asked to design or build a new frontend UI, create a fresh page or app experience, choose a visual direction for a new product surface, or turn a product brief into implementation-ready React, Next.js, Tailwind, CSS, or HTML.
Create decision-complete plans for Codex harness work, including tests, fixtures, contracts, memory updates, verification, and recovery. Use for new features, refactors, bug fixes, audits, or multi-phase autonomous work.
Prepare Codex harness package releases with version checks, package dry-runs, npm publish readiness, release notes, verification evidence, and rollback notes. Use before publishing or tagging releases.
| name | genesis-api-contract |
| description | Create and verify API contracts before endpoint implementation. Use for API routes, service interfaces, validation rules, error shapes, snapshots, and endpoint tests. |
Ensure API behavior is defined by contracts, fixtures, and tests before code.
Use before adding or changing endpoints, request schemas, response schemas, auth, errors, or persistence behavior.
Do not use for UI-only changes that do not touch API behavior.
Endpoint path, method, auth, request body, success response, error cases, and persistence effects.
Contract folder, fixture, success test, validation error test, not found test, and schema validation.
Create contract, integration, and unit tests as appropriate.
Create API fixtures for success and failure cases.
Update contracts/api/ with request, response, schema, example, and error JSON.
Update .codebase/API_CONTRACTS.md and TEST_MATRIX.md.
Load endpoint contract before source files. Open only route and validator modules named by the contract.
Contract tests fail before implementation and pass after the minimum endpoint change.
Implementing validation before schema, changing error shape without a contract, and testing only success.
If endpoint behavior is ambiguous, freeze implementation and create the missing contract first.
