How do I install the Azmankudus Style Eden Blueprint Webapi skill?

Run npx skillmds@latest add tomevault-io/azmankudus-style-eden-blueprint-webapi in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Azmankudus Style Eden Blueprint Webapi skill do?

Web API Blueprint (Platform-Agnostic) It is listed under Integrations & APIs on SkillMD.

Is Azmankudus Style Eden Blueprint Webapi safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Azmankudus Style Eden Blueprint Webapi?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Azmankudus Style Eden Blueprint Webapi free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Azmankudus Style Eden Blueprint Webapi?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Azmankudus Style Eden Blueprint Webapi by tomevault-io

Name: Azmankudus Style Eden Blueprint Webapi
Author: tomevault-io

File contents

Web API Blueprint (Platform-Agnostic)

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.

Dependency Note

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 Reference

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

1. Agent Anti-Hallucination Guardrails

Before finalizing any strategy or code generation for an API (regardless of language), the agent MUST verify against these strict rules:

API Contract First: Do not generate controllers, routers, or DTOs without an explicitly defined and agreed-upon OpenAPI contract. The contract is the master specification.
No Auto-magic Endpoints: Never invent or implement an endpoint that does not exist in the defined OpenAPI contract.
RFC 7807 Errors: Never hallucinate custom error structures. All HTTP errors MUST map exactly to RFC 7807 (Problem Details for HTTP APIs).
Universal JSON Standards: Always output standard JSON (application/json). Use camelCase for properties and kebab-case for paths.

Reference Files

Requirements & Governance

File	Description
`references/requirement/api-contract.md`	API synchronization and strict governance (OpenAPI source of truth)

Design Standards

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

Testing

File	Description
`references/testing/api-testing.md`	Guidelines for contract testing and schema validation

Source: azmankudus/style-eden — distributed by TomeVault.

---name: azmankudus-style-eden-blueprint-webapidescription: Web API Blueprint (Platform-Agnostic)---# Web API Blueprint (Platform-Agnostic)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.## Dependency NoteOther 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 Reference| 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 |---## 1. Agent Anti-Hallucination GuardrailsBefore finalizing any strategy or code generation for an API (regardless of language), the agent MUST verify against these strict rules:* **API Contract First**: Do not generate controllers, routers, or DTOs without an explicitly defined and agreed-upon OpenAPI contract. The contract is the master specification.* **No Auto-magic Endpoints**: Never invent or implement an endpoint that does not exist in the defined OpenAPI contract.* **RFC 7807 Errors**: Never hallucinate custom error structures. All HTTP errors MUST map exactly to RFC 7807 (Problem Details for HTTP APIs).* **Universal JSON Standards**: Always output standard JSON (`application/json`). Use `camelCase` for properties and `kebab-case` for paths.---## Reference Files### Requirements & Governance| File | Description ||---|---|| `references/requirement/api-contract.md` | API synchronization and strict governance (OpenAPI source of truth) |### Design Standards| 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 |### Testing| File | Description ||---|---|| `references/testing/api-testing.md` | Guidelines for contract testing and schema validation |---> Source: [azmankudus/style-eden](https://github.com/azmankudus/style-eden) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Azmankudus Style Eden Blueprint Webapi