Skill

be-api

Create a REST/RPC endpoint with Zod validation, OpenAPI spec, and RFC 9457 error handling

Install

npx claudepluginhub justn-hyeok/harness-for-yall --plugin be-experts

Tool Access

This skill uses the workspace's default tool permissions.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.9k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 7, 2026

Actions

View Source View Plugin View on GitHub View README

Workflow

Architecture (be-architect): Design the endpoint

Resource modeling and URL structure
Middleware chain (auth, validation, error handling)
Request/response schema shapes
Write spec to .claude/specs/be-{resource}.md

Implementation + Validation (be-implementer + be-validator in parallel):

be-implementer: Route handler, service layer, DI wiring
be-validator: Zod schemas, OpenAPI generation, RFC 9457 error factories

Testing (be-tester): HTTP contract tests

Happy path + error cases
Validation error format verification
Auth/authz checks

Execution

Start by spawning be-architect with:

Design a REST API endpoint for resource: $ARGUMENTS.resource Methods: ${ARGUMENTS.method || "CRUD"} Framework: ${ARGUMENTS.framework || "hono"} Requirements: - Zod validation on all inputs - OpenAPI spec auto-generated - RFC 9457 Problem Details for errors - pino logging Provide the endpoint spec, then delegate: 1. be-implementer for route/handler/service implementation 2. be-validator for schemas/OpenAPI/error factories (in parallel with implementer) 3. After both complete, be-tester for contract tests

Create Backend API Endpoint

Build a complete backend endpoint through the Expert Pool pipeline.

Workflow

Architecture (be-architect): Design the endpoint
- Resource modeling and URL structure
- Middleware chain (auth, validation, error handling)
- Request/response schema shapes
- Write spec to .claude/specs/be-{resource}.md
Implementation + Validation (be-implementer + be-validator in parallel):
- be-implementer: Route handler, service layer, DI wiring
- be-validator: Zod schemas, OpenAPI generation, RFC 9457 error factories
Testing (be-tester): HTTP contract tests
- Happy path + error cases
- Validation error format verification
- Auth/authz checks

Arguments

resource: $ARGUMENTS.resource — The resource name
method: $ARGUMENTS.method — HTTP method(s) or "CRUD" for full resource (default: CRUD)
framework: $ARGUMENTS.framework — hono (default) or express

Execution

Start by spawning be-architect with:

Design a REST API endpoint for resource: $ARGUMENTS.resource
Methods: ${ARGUMENTS.method || "CRUD"}
Framework: ${ARGUMENTS.framework || "hono"}

Requirements:
- Zod validation on all inputs
- OpenAPI spec auto-generated
- RFC 9457 Problem Details for errors
- pino logging

Provide the endpoint spec, then delegate:
1. be-implementer for route/handler/service implementation
2. be-validator for schemas/OpenAPI/error factories (in parallel with implementer)
3. After both complete, be-tester for contract tests