Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    api architect

    1

    Design, review, and evolve REST, GraphQL, and gRPC API contracts with contract-first discipline and security audits.

    $5.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    api architect

    api architect

    Example session with this skill installed

    Review the proposed changes in openapi.yaml for any breaking changes and ensure the new /orders/{id}/refund endpoint follows our existing error response conventions.

    Inspect the existing API specification and implementation where available.

    Identify

    • Breaking changes affecting existing API consumers.
    • Inconsistencies with existing response and error conventions.
    • Missing HTTP status codes and response schemas.
    • Potential security and authorization concerns.
    • Documentation inconsistencies.

    Provide a detailed review with evidence from the project files, a proposed corrected API contract, and a migration recommendation where necessary.

    Do not invent existing endpoints, consumers, or implementation details. Clearly distinguish verified findings from assumptions.

    Do not modify any files until you have presented your findings and recommendations.

    • Read your context and instructions
    • Compiled the api architect

    I have analyzed the diff for openapi.yaml and compared the new /orders/{id}/refund endpoint against your existing patterns in src/middleware/error-handler.ts.

    API Review Report

    FeatureFindingStatus
    Breaking ChangesRemoved tax_identifier from User schema without a major version bump.High Risk
    Error ConsistencyThe refund endpoint uses message field, but project standard is error_code and developer_info.Recommendation
    SecurityMissing 403 Forbidden response definition for unauthorized refund attempts.Verified
    NamingEndpoint uses kebab-case which matches the existing /user-profiles convention.Verified

    Proposed Schema Fix

    /orders/{id}/refund:
      post:
        summary: Refund an order
        responses:
          '400':
            description: Bad Request
            content:
              application/json:
                schema:
                  $ref: '#/components/schemas/ErrorResponse'
          '403':
            description: Forbidden
    

    Compatibility Verdict

    FAILED: The removal of tax_identifier will break the Android mobile client and the Python SDK. I recommend marking this field as deprecated: true instead of removing it.

    Next steps

    1. Revert the deletion of tax_identifier and add a deprecation warning.
    2. Update the refund endpoint error response to use the ErrorResponse component.
    3. Run spectral lint openapi.yaml to confirm structural validity.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stop shipping APIs with breaking changes or inconsistent schemas. This skill handles the rigorous work of designing, reviewing, and documenting API contracts with a focus on stability and security. It prevents spec-to-code drift by inspecting your actual implementation before proposing any changes.

    What it does

    • Contract-first design: Author and evolve OpenAPI, GraphQL SDL, AsyncAPI, and gRPC Protobuf definitions.
    • Security audits: Scans contracts for OWASP API Top 10 vulnerabilities like BOLA and mass assignment.
    • Breaking change detection: Analyzes proposed schema changes for backward compatibility risks.
    • Consistency enforcement: Aligns naming, error models, pagination, and versioning with existing project conventions.
    • Documentation generation: Produces technical docs, changelogs, and usage examples derived from verified code.

    How it works

    1. Understand: The skill inspects your routes, schemas, and existing specs to identify the API style and conventions.
    2. Analyze: It flags inconsistencies, security gaps, and drift between your documentation and implementation.
    3. Design/Plan: It proposes a contract diff and migration steps, explaining the rationale behind architectural choices.
    4. Validate: It runs available linters (Spectral, buf) and validators to confirm structural and behavioral correctness.

    Frameworks & tools

    Works with REST, GraphQL, gRPC, and event-driven architectures. Supports OpenAPI/Swagger, AsyncAPI, Protobuf, and GraphQL SDL. Compatible with linters like Spectral and buf.

    Why this beats prompting it yourself

    Generic prompts often invent endpoints or ignore existing project conventions. This skill enforces an evidence-based workflow that distinguishes between verified facts, assumptions, and recommendations, ensuring your API remains stable for consumers.

    Use cases

    • Add a new resource to a REST API while maintaining existing pagination and error patterns.
    • Review a GraphQL schema for N+1 risks or inconsistent type naming.
    • Draft a migration plan for deprecating a v1 endpoint in favor of v2.
    • Generate an OpenAPI spec for an existing codebase that lacks documentation.

    Known limitations

    Does not handle internal business logic, database migrations, or auth implementation. Restricted to the API contract layer.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    No implementation of business logic or auth internals. Cannot perform behavioral validation without existing project test suites. Limited to contract-layer changes.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    Permissions

    Network Access
    Read Files
    Write Files
    Terminal / Shell
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    The API Architect focuses exclusively on the contract layer, ensuring your OpenAPI, GraphQL, or gRPC definitions are secure and consistent without touching your internal business logic or database schemas.

    It proactively detects breaking changes, such as removed fields or changed types, and audits your contracts against the OWASP API Top 10 to catch vulnerabilities like mass assignment before they reach production.

    The skill is designed for any AI agent with codebase access; it functions by inspecting your existing routes and schemas to ensure any new proposals align with your established naming and versioning conventions.

    Your purchase includes the full API Architect skill definition, integrated support for industry-standard linters like Spectral and buf, and a set of specialized workflows for contract-first design and documentation.

    Unlike generic prompts that may hallucinate endpoints, this skill uses an evidence-based workflow to reconcile your actual implementation with your documentation, effectively eliminating spec-to-code drift.

    Updates are delivered through the marketplace and include the latest security audit patterns and updated support for evolving standards like the latest OpenAPI or AsyncAPI versions.

    New in APIs & Backend