# Add Catalyst Relay HTTP Endpoints

Adding endpoints can become inconsistent when route files, validation, handlers, and docs follow different patterns. This skill gives Claude, Codex, and Claude Code a clear Catalyst-Relay checklist for consistent HTTP endpoint work.

## Install

```bash
npx skillstore add artisan-edge/add-endpoint
```

## Metadata

- - Slug: artisan-edge-add-endpoint
- - Version: 1.0.0
- - Author: Artisan-Edge
- - GitHub username: Artisan-Edge
- - License: MIT
- - Repository: https://github.com/Artisan-Edge/Catalyst-Relay/tree/main/.claude/skills/add-endpoint
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: external\_commands, filesystem
- - Quality score: 78
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/artisan-edge-add-endpoint
- - Manifest: https://skillstore.pages.dev/api/skills/artisan-edge-add-endpoint/manifest

## Capabilities

- Defines the route file pattern under src/server/routes/\{category\}/\{endpoint\}.ts.
- Shows colocated Zod request schemas, response types, and handler factories.
- Explains how to register Hono routes in src/server/routes/index.ts.
- Specifies the standard success and error response envelope.
- Lists endpoint documentation requirements for docs/endpoints/\{category\}.md.
- Maps HTTP endpoints to ADTClient library methods when needed.

## Use Cases

- Add a New API Route: Create a route file with validation, response typing, and a Hono handler that matches Catalyst-Relay conventions.
- Standardize Endpoint Documentation: Produce endpoint docs with request tables, response tables, examples, errors, use cases, and library usage notes.
- Expose Core Features Through HTTP: Connect core functionality to an HTTP endpoint and add a matching ADTClient method when library mode needs it.

## Prompt Templates

### Create a Basic Endpoint

```
Use the add-endpoint skill to add a simple Catalyst-Relay endpoint for [feature]. Include the route file, request validation, response type, and route registration steps.
```

### Add Validation and Responses

```
Use the add-endpoint skill to design an endpoint for [operation]. Follow the standard Zod schema pattern and success or error response envelope.
```

### Document an Endpoint

```
Use the add-endpoint skill to create documentation for [endpoint]. Include request details, body fields, response fields, errors, use cases, and library usage.
```

### Add HTTP and Client Support

```
Use the add-endpoint skill to add [endpoint] and map it to an ADTClient method. Ensure route wiring, validation, response format, docs, and typecheck guidance are covered.
```

## Limitations

- It is specific to the Catalyst-Relay server structure.
- It does not implement endpoint business logic for the developer.
- It does not define authentication or authorization policy.
- It does not run tests or type checks by itself.

## Best Practices

- Keep each endpoint in its own route file with colocated schema, types, and handler.
- Use the standard response envelope for both success and error cases.
- Update route registration, documentation, and ADTClient mappings in the same change when applicable.

## Anti Patterns

- Do not add handlers without Zod request validation.
- Do not return ad hoc response shapes that bypass the success and error envelope.
- Do not leave endpoint documentation or client mappings for a later unrelated change.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T10:28:15.676\+00:00
- - Summary: Static analysis flagged Markdown backticks, relative import examples, and documentation text as command execution, path traversal, weak crypto, and reconnaissance. Review found only instructional TypeScript examples and endpoint documentation guidance, with no executable skill code, network access, secret handling, or prompt injection attempts.

## Stats

- - Views: 209
- - Downloads: 6
- - Favorites: 0
- - Popularity score: 0