api-endpoint
SolidUse 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).
Install
Quality Score: 82/100
Skill Content
Details
- Author
- event4u-app
- Repository
- event4u-app/agent-config
- Created
- 5 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
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.
using-api-platform-skills
Route API work to the right API Platform skill. Use when the user mentions APIs, OpenAPI, versioning, breaking changes, deprecation, webhooks, idempotency, contract tests, ship-check, or is unsure which skill to load. Also when they say "/api-ship-check", "which API skill", "api platform", or in Chinese "接口审查", "兼容性", "破坏性变更", "弃用", "幂等", "Webhook", "变更日志", "该用哪个 skill". Do NOT use for pure REST naming/style (plural nouns only).
api-design
This skill should be used when designing or building an API — endpoints, routes, request/response shapes, error formats, pagination, versioning, or deciding REST vs GraphQL. Trigger phrases include "design the API", "build an endpoint", "REST or GraphQL", "how should I structure my routes", "API error format", "paginate results", "version my API", "validate env vars", "idempotency", "what should this endpoint return". It applies proven REST conventions and a clear REST-vs-GraphQL decision, with env-config validation.