api-endpoint

Solid

Use when creating an API endpoint or HTTP route handler — detects the project stack and routes to the matching carve-out (laravel-api-endpoint, nextjs-patterns, symfony-workflow).

AI & Automation 7 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# api-endpoint > **Grounded corpus:** endpoint-shape decisions (pagination, error shape, > idempotency, rate limits) ground via the > [`api-design`](../api-design/SKILL.md) corpus — `./scripts-run > <skills-root>/corpus-grounding/scripts/ground search > --manifest <skills-root>/api-design/data/manifest.json "<concern>"`. ## When to use Use this skill when the user asks to create a new API endpoint, REST route, or HTTP handler. Do NOT use when: - Modifying existing endpoints — use the code-refactoring skill. - API design decisions (versioning, deprecation, contract shape) — use [`api-design`](../api-design/SKILL.md). ## Stack routing Detect the stack, then hand off to the matching carve-out skill for the framework-specific procedure (file layout, validation primitive, response-shaping convention). | Detected stack | Carve-out skill | |---|---| | Laravel (`artisan` + `composer.json` with `laravel/framework`) | [`laravel-api-endpoint`](../laravel-api-endpoint/SKILL.md) | | Symfony (`bin/console` + `composer.json` with `symfony/framework-bundle`) | [`symfony-workflow`](../symfony-workflow/SKILL.md) | | Next.js (`next` in `package.json`) | [`nextjs-patterns`](../nextjs-patterns/SKILL.md) | | Express / Fastify / NestJS / plain Node | follow project conventions in `agents/` + `package.json scripts` | | FastAPI / Django / Flask | follow project conventions in `agents/` + `pyproject.toml` | | Go (`net/http`, `gin`, `echo`, `fiber`) | follow project conventions in `agents/` + `...

Details

Author
event4u-app
Repository
event4u-app/agent-config
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

api-design

Use when designing APIs, planning endpoints, REST conventions, versioning, or deprecation — even when the user just says 'expose this as an endpoint' without naming API design.

7 Updated today
event4u-app
API & Backend Listed

api-surface

Maps the entire API surface of a codebase -- route definitions, middleware chains, auth requirements, request/response types, deprecated endpoints, orphaned endpoints, and cross-endpoint inconsistencies. USE THIS SKILL WHEN: - You need a complete inventory of all API endpoints in a project - Someone asks "what endpoints do we have?" or "what does our API look like?" - You are onboarding to a new backend codebase and need to understand its API - You need to find orphaned, undocumented, or deprecated endpoints - Someone asks about API inconsistencies (different response shapes, auth gaps) - You are preparing for an API review, documentation sprint, or versioning migration - You need to understand endpoint dependencies before refactoring - A project has no OpenAPI spec and you need to generate one from code - You suspect there are endpoints without authentication or rate limiting TRIGGER PHRASES: "API surface", "list all endpoints", "API inventory", "endpoint map", "orphaned endpoints", "API inconsistencies", "u

8 Updated 1 weeks ago
tinh2
API & Backend Solid

api-designer

Designs clean, consistent REST and GraphQL APIs covering resource modeling, URL structure, versioning, pagination, filtering, error formats (RFC 9457 Problem Details), idempotency, authentication, rate limiting, and machine-readable contracts (OpenAPI 3.1 / GraphQL SDL). Use this skill when designing a new API or endpoint, reviewing an API design, choosing REST vs GraphQL, deciding on versioning or pagination strategy, defining error responses, adding idempotency keys, writing or critiquing an OpenAPI/GraphQL schema, or establishing API style guidelines and naming conventions.

3 Updated today
JayRHa