328건 · 관련도순
Expert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research, implement, modify, and audit behavior inside Bricks Builder sites using the bundled Bricks Academy corpus, stable development workflows, and version-aware verification against an authorized active Bricks installation. Use when the requested outcome concerns Bricks elements, controls, schema, hooks, templates, styling, responsive settings, dynamic data, queries, forms, interactions, custom elements, or page JSON. Do not use merely because Bricks Builder is mentioned, for generic WordPress, PHP, CSS, or JavaScript work, or for maintaining, naming, versioning, documenting, or releasing this Skill repository.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenAPI contract standards for API specification, versioning, and type generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a commit following repository guidelines with proper versioning and changelog updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Semantic versioning and changelog formatting for software releases. Use when: preparing releases, updating version numbers, writing changelogs. Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provision and manage cloud infrastructure using Terraform with HCL modules, remote state backends, workspaces, and plan/apply workflow. Implement infrastructure as code patterns with variable management, output values, and state locking for team collaboration. Use when provisioning new cloud infrastructure, migrating from ClickOps or CloudFormation to declarative IaC, managing multi-environment infrastructure, versioning infrastructure changes alongside application code, or enforcing standards through reusable modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register trained models in MLflow Model Registry with version control, implement stage transitions (Staging, Production, Archived) with approval workflows, and manage model lineage with comprehensive metadata and deployment tracking. Use when promoting a trained model from experimentation to production, managing multiple model versions across development stages, implementing approval workflows for governance, rolling back to previous versions, or auditing model changes for compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Release a new version of an R package including version bumping, NEWS.md updates, git tagging, GitHub release creation, and post-release development version setup. Use when a package is ready for a new patch, minor, or major release, after CRAN acceptance to create the corresponding GitHub release, or when setting up the development version bump immediately after a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a software release cycle with milestones, feature freezes, release candidates, and go/no-go criteria. Covers calendar-based and feature-based release strategies. Use when starting planning for a major or minor version release, transitioning from ad-hoc to structured release cadence, coordinating a release across multiple teams or components, defining quality gates for a regulated project, or planning the first public release (v1.0.0) of a project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evolve an existing skill by refining its content in-place or creating an advanced variant. Covers assessing the current skill, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes, updating version metadata, and synchronizing the registry and cross-references. Use when a skill's procedure steps are outdated, user feedback reveals gaps, a skill needs a complexity upgrade, an advanced variant is needed alongside the original, or related skills are added and cross-references are stale.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evolve an existing agent definition by refining its persona in-place or creating an advanced variant. Covers assessing the current agent against best practices, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes to skills, tools, capabilities, and limitations, updating version metadata, and synchronizing the registry and cross-references. Use when an agent's skills list is outdated, user feedback reveals capability gaps, tool requirements have changed, an advanced variant is needed alongside the original, or the agent's scope needs sharpening after real-world use.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy and configure an API gateway (Kong or Traefik) to handle API traffic management, authentication, rate limiting, request/response transformation, and routing. Covers plugin configuration, upstream services, consumer management, and integration with existing infrastructure. Use when multiple backend services need a unified API endpoint, when centralized authentication or rate limiting is required, when implementing API versioning, or when needing detailed analytics and load balancing for microservices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when debugging shared library load failures, setting RPATH or RUNPATH, applying soname versioning, writing dlopen plugins, or intercepting with LD_PRELOAD. Not for static archives: use binutils.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don't use for single commits or for publishing to a package registry.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design model registries for AI versioning. TRIGGERS - Use when user needs help with ai-model-registry related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain CHANGELOG.md — add new version entries, keep the Unreleased section, cut a release, or restructure the whole file — following the Keep a Changelog format and Semantic Versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate a full Galyarder Framework release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
jjでバージョン管理操作を実行する。jjが有効化されている環境でgitコマンドの代わりに使用。bookmark移動忘れによる変更漏れ・履歴分断を防ぐワークフローを提供。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate CHANGELOG entries following conventional commits format with semantic versioning. Use when finalizing features to maintain proper change history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage ML datasets with the datasets ecosystem — loading, streaming, preprocessing, versioning, and sharing. Use when data handling (not modeling) is the bottleneck.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.