Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/tomevault-io/skills-registry --skill blueprint-webapiEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | blueprint-webapi |
| description | > Use when this capability is needed. |
Design and architect robust HTTP REST APIs regardless of the underlying language or framework. This blueprint focuses entirely on API Protocol, Contracts, and Governance. It enforces a strict "Design-First / Contract-First" approach.
Other blueprints (like blueprint-web-micronaut or blueprint-web-nodejs) should inherit these rules to ensure any API built by a team complies with a unified standard.
| Command | Phase | Description |
|---|---|---|
/blueprint init | Pre | Start the discovery and planning session for the API |
/blueprint api-spec | Pre | Scaffold an OpenAPI 3.1 specification document |
/blueprint check | During | Validate project code against universally strict API contract standards |
Before finalizing any strategy or code generation for an API (regardless of language), the agent MUST verify against these strict rules:
application/json). Use camelCase for properties and kebab-case for paths.| File | Description |
|---|---|
references/requirement/api-contract.md | API synchronization and strict governance (OpenAPI source of truth) |
| File | Description |
|---|---|
references/design/openapi-standards.md | Rules for URLs, Request/Response shapes, and standard headers |
references/design/schema-contract.md | Strict envelope schemas (client/server) including auth and tracing headers |
| File | Description |
|---|---|
references/testing/api-testing.md | Guidelines for contract testing and schema validation |
Source: azmankudus/style-eden — distributed by TomeVault.