원클릭으로 Manus에서 모든 스킬 실행

backend-api

스타0

포크0

업데이트2026년 2월 7일 10:02

Design, implement, and maintain RESTful API endpoints following industry best practices for resource-based URLs, HTTP methods, versioning, query parameters, and status codes. Use this skill when creating API routes in Express, Fastify, Next.js API routes, TanStack Router API endpoints, or any backend API framework; when defining RESTful resources with GET, POST, PUT, PATCH, DELETE operations; when implementing API versioning strategies; when adding query parameters for filtering, sorting, pagination, or search; when determining appropriate HTTP status codes (200, 201, 400, 404, 500, etc.); when structuring nested resources and endpoint naming conventions; when implementing rate limiting headers; or when working with API contract design and backend routing in TypeScript, JavaScript, Python, Ruby, or any server-side language.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

shynlee04

shynlee04/idumb-v2

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Backend API

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle backend API.

When to use this skill

When creating RESTful API endpoints with resource-based URLs
When defining HTTP methods (GET, POST, PUT, PATCH, DELETE) for API routes
When implementing API versioning strategies (URL path or headers)
When adding query parameters for filtering, sorting, pagination, or search
When determining appropriate HTTP status codes for responses
When structuring nested resources and endpoint URLs
When implementing rate limiting headers and response metadata
When working with API frameworks like Express, Fastify, Next.js API routes, TanStack Router, or similar

Instructions

For details, refer to the information provided in this file: backend API

이 저장소의 다른 Skills

같은 저장소

agent-browser

shynlee04/idumb-v2

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-02-070

gap-analysis

shynlee04/idumb-v2

Systematically identify what's missing, unknown, or needs investigation before making changes or decisions. Use proactively when proposing features, implementing changes, or making technical decisions to ensure all critical areas are covered. This skill catches overlooked dependencies, edge cases, and integration points before they become problems. Examples: - "Implement user authentication" → trigger gap analysis (what's the current auth system?) - "Add caching to API" → trigger gap analysis (what caching infrastructure exists?) - "Migrate to TypeScript" → trigger gap analysis (what's the build pipeline?) - "Refactor this module" → trigger gap analysis (what depends on this module?) - "Add new API endpoint" → trigger gap analysis (what endpoints exist, what patterns?)

2026-02-070

intent-clarification

shynlee04/idumb-v2

Detect ambiguous or underspecified research requests and guide through structured clarification questions before executing any research. Use proactively when user requests are vague, lack specificity, missing context, or have unclear goals. This skill prevents wasted research by ensuring intent is crystal clear before any web searches, file reads, or data gathering. Examples: - "Research the codebase" → ❌ Too vague, trigger clarification - "Why is this slow?" → ❌ Missing context (what is "this"?), trigger clarification - "Add a feature" → ❌ Not research, this is implementation - "Investigate authentication flow" → ❌ What specifically about it? Trigger clarification - "Compare React and Vue" → ✅ Specific enough, but still validate dimensions

2026-02-070

multi-aspect-assessment

shynlee04/idumb-v2

Evaluate requests, proposals, or decisions from multiple dimensions (technical, business, UX, security, performance, maintainability, etc.) to ensure holistic understanding before proceeding. Use proactively when making technical decisions, choosing solutions, or proposing changes. This skill prevents single-minded thinking and uncovers trade-offs, risks, and opportunities across all relevant aspects. Examples: - "Use Redis for caching" → assess multiple aspects (performance, cost, complexity, ops) - "Add AI to our app" → assess aspects (technical feasibility, user experience, data privacy) - "Refactor to microservices" → assess aspects (benefits, costs, migration complexity, team readiness) - "Implement authentication" → assess aspects (security, UX, integration effort, maintenance) - "Switch to React 19" → assess aspects (benefits, migration cost, breaking changes, learning curve)

2026-02-070

opencode-primitive-selector

shynlee04/idumb-v2

Choose the right OpenCode primitive (Command, Skill, Tool, Prompt, CustomTool, Plugin hook) for a given task or workflow. Use proactively when deciding which OpenCode capability to use, or when trying to understand what's available. This skill maps research and development needs to appropriate OpenCode mechanisms, ensuring optimal use of the platform's capabilities. Examples: - "How do I search the codebase?" → select tool (read/grep) - "I need a reusable workflow for feature development" → select command - "How do I intercept file writes?" → select plugin hook - "What primitive should I use for systematic debugging?" → select skill - "I need a custom tool for X" → select CustomTool (if innate tools insufficient)

2026-02-070

research-workflow-planner

shynlee04/idumb-v2

Create structured, executable research plans with clear phases, checkpoints, and validation criteria. Use proactively when research intent is clear but execution plan is missing. This skill transforms research goals into actionable workflows with defined deliverables, time estimates, and success metrics, ensuring research is systematic and produces useful outputs. Examples: - "Research how to add OAuth" (intent clear, need plan) → trigger workflow planner - "Investigate performance bottlenecks" (intent clear, need plan) → trigger workflow planner - "Analyze codebase architecture" (intent clear, need plan) → trigger workflow planner - "Find best practices for X" (intent clear, need plan) → trigger workflow planner - "Compare technology options" (intent clear, need plan) → trigger workflow planner

2026-02-070

name

Backend API

description

Backend API

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle backend API.

When to use this skill

When creating RESTful API endpoints with resource-based URLs
When defining HTTP methods (GET, POST, PUT, PATCH, DELETE) for API routes
When implementing API versioning strategies (URL path or headers)
When adding query parameters for filtering, sorting, pagination, or search
When determining appropriate HTTP status codes for responses
When structuring nested resources and endpoint URLs
When implementing rate limiting headers and response metadata
When working with API frameworks like Express, Fastify, Next.js API routes, TanStack Router, or similar

Instructions

For details, refer to the information provided in this file: backend API