325건 · 관련도순
Design and review REST APIs with consistent URLs, HTTP status codes, error responses, and pagination, which divides results into smaller batches. Covers authentication, access limits, and versioning to help define clear behavior for API users.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assists with managing versioning and changelogs in JavaScript/TypeScript monorepos using Changesets. Use when automating semantic versioning, generating changelogs from PRs, coordinating multi-package releases, or publishing to npm. Trigger words: changesets, versioning, changelog, npm publish, monorepo release, semver.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API migration strategies, deprecation workflows, and header/URL/content versioning. Activate on: API versioning, backward compatibility, deprecation, breaking change, API migration, v1 v2, sunset header. NOT for: schema evolution in data (use schema-evolution-manager), gateway routing (use api-gateway-reverse-proxy-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API migration strategies, deprecation workflows, and header/URL/content versioning. Activate on: API versioning, backward compatibility, deprecation, breaking change, API migration, v1 v2, sunset header. NOT for: schema evolution in data (use schema-evolution-manager), gateway routing (use api-gateway-reverse-proxy-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and review REST APIs with consistent resource names, HTTP status codes, error responses, and pagination, which splits lists into smaller results. It also guides filtering, authentication, request limits, and versioning for public or internal APIs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Choose between REST, GraphQL, and tRPC based on who uses an API and how it is deployed. Define consistent responses, pagination, authentication, and versioning, supported by concrete request examples and failure cases.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Choose how an API, the interface software uses to exchange data, should work. Covers REST, GraphQL, and tRPC selection, consistent responses, pagination, versioning, authentication, request limits, documentation, and security review considerations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is running in prod right now?", when a deploy must be reproducible months later, or when an incident needs a clean rollback. The core reframe: an LLM app artifact is NOT an ML model — it is a manifest over many independently-mutable parts, not one weights file. Do NOT activate for one-off prompt edits with no deploy, for a single-component demo, or where a vendor owns the whole prompt lifecycle. For versioning ONE compiled prompt use [[agentsop-per-model-artifacts]]; for the CI comparison mechanism use [[agentsop-regression-gate]]. Search keywords: prompt versioning, reproducible deploy, what is running in prod, rollback LLM app, model pinning, prompt registry, version prompts and config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages AI model retention and machine unlearning requirements. Covers training data deletion verification, model versioning for compliance, machine unlearning techniques (SISA, gradient-based), and retraining triggers. Keywords: AI retention, machine unlearning, model versioning, training data deletion, retraining, storage limitation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan, implement, or review git workflow and versioning work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests git workflow and versioning work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert at designing clean, consistent, and developer-friendly APIs. Covers RESTful conventions, versioning strategies, error handling, pagination, rate limiting, and OpenAPI documentation. Designs APIs that are intuitive to use and easy to evolve. Use when "API design, REST API, RESTful, API versioning, API documentation, OpenAPI, Swagger, API error handling, pagination, rate limiting, api, rest, http, versioning, pagination, openapi, swagger" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design specialist for REST, GraphQL, gRPC, versioning strategies, and developer experienceUse when "api design, rest, graphql, grpc, openapi, swagger, versioning, pagination, rate limiting, endpoint, api, rest, graphql, grpc, openapi, swagger, versioning, pagination, rate-limiting, ml-memory" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes before tagging, evaluating whether a change constitutes a breaking change, adding pre-release identifiers, or resolving disagreement about what version bump is appropriate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure API/contract changes specify versioning strategy, backward compatibility, deprecation plan, and migration guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage API versioning and evolution with URL/header/query strategies, deprecation workflows, breaking change classification, sunset headers, and consumer-driven contract testing. Use when designing versioning strategy, deprecating endpoints, or evolving API contracts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert en versioning d'agents IA (git-based, rollback, canary deployments, changelog, migration)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the `changelog` skill calls for a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.