菜单
REST, GraphQL, and gRPC API governance, versioning strategy, rate limiting, and developer experience design. Trigger: "API architecture", "API design", "REST", "GraphQL", "gRPC", "API governance", "developer experience".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or update a CONSTITUTION.md that defines project governance — establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking. Use when defining project rules, setting up coding standards, establishing quality gates, configuring TDD requirements, or creating non-negotiable development principles.
Create a feature specification from a natural language description — generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements for a product idea.
Generate Gherkin .feature files from requirements before implementation — produces executable BDD scenarios with traceability tags, computes assertion integrity hashes, and locks acceptance criteria for test-driven development. Use when writing tests first, doing TDD, creating test cases from a spec, locking acceptance criteria, or setting up red-green-refactor with hash-verified assertions.
Validate cross-artifact consistency — checks that every spec requirement traces to tasks, plan tech stack matches task file paths, and constitution principles are satisfied across all artifacts. Use when running a consistency check, verifying requirements traceability, detecting conflicts between design docs, or auditing alignment before implementation begins.
Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.
Generate quality checklists that validate requirements completeness, clarity, and consistency — produces scored checklist items linked to specific spec sections (FR-XXX, SC-XXX). Use when reviewing a spec for gaps, doing a requirements review, verifying PRD quality, auditing user stories and acceptance criteria, or gating before implementation.
| name | api-architecture |
| author | JM Labs (Javier Montaño) |
| description | REST, GraphQL, and gRPC API governance, versioning strategy, rate limiting, and developer experience design. Trigger: "API architecture", "API design", "REST", "GraphQL", "gRPC", "API governance", "developer experience". |
| allowed-tools | ["Read","Glob","Grep","Bash","Agent"] |
Design and govern APIs across the stack: REST/GraphQL/gRPC protocol selection, versioning strategies, rate limiting, security, documentation, and developer experience optimization.
"APIs are the product — every endpoint is a contract, every breaking change is a trust violation, every missing doc is a support ticket."
