6.6천건 · 관련도순
Develop and fix OpenShell’s keyboard-driven terminal interface using guidance on screen structure, background data fetching, themes, and navigation. Follow existing implementation patterns to add features that fit the interface’s established behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
List, switch, or reload maps on a running CARLA server, or generate a world from road files. Preserve simulation settings when needed and verify the resulting map name, timing settings, and rendering mode.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Laravel applications with authenticated APIs, interactive interfaces, and background jobs. The skill guides database relationships, query optimization, and feature tests, using tools such as Sanctum for authentication and Livewire for interfaces.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turns changelog-scan results into a readable, categorized release notes draft. Places breaking changes and security items at the top and ends with a human review note, providing a proposal for review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Track multiple Claude sessions working on one project, check that changes reached main with screenshots and changelog entries, verify the live site, and identify finished sessions, interrupted work, and questions awaiting the user.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Follow a release workflow for game changes, from screenshots and changelog entries through testing, commits, and live deployment. Verify the published version, measure transfer sizes, and report evidence while applying approval rules for large uploads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare and publish DeepChat releases through its project-specific workflow. Update versions and bilingual changelogs, run release checks, manage release branches and tags, and resume unfinished releases before publishing after release PR approval.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare evidence for a talk about project experience by comparing git history, release notes, and a source summary. Produce commit and contributor metrics, release analysis, and a factual timeline that flags conflicting or unverified information.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn Git commits and pull request details into release notes in three formats: a changelog section, a release PR description, and a user announcement. Group changes, explain user impact, and flag database migrations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide AI agent development from requirements and project setup through implementation, behavior evaluation, deployment, and monitoring. Provides coding rules, debugging steps, and links to specialized skills so each phase follows a defined process.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
LoongCollector E2E Testing Framework Development Guide. Use this rule when you need to understand E2E testing framework architecture, develop new test behavior functions, or extend testing capabilities. Contains detailed BDD testing framework usage, test behavior function development and registration workflows, and comprehensive reference of existing testing capabilities. Example: When adding custom test behaviors for new plugins, use this rule to understand how to write and register new test functions. Example: When developing E2E tests, use this rule to understand the e2e framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate release notes and changelogs from git commits, feature lists, or project updates. Use when a user asks to generate a changelog, create release notes, summarize recent changes, draft a CHANGELOG entry, or prepare release documentation from git history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to using LLMs throughout the game development lifecycle - from design to implementation to testingUse when "ai game development, llm game dev, claude game, gpt game, ai coding games, vibe coding game, prompt game development, llm, ai, game-development, workflow, prompting, coding, prototyping, claude, gpt, cursor" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Avalonia Zafiro Development workflow skill. Use this skill when the user needs Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI Agent Development Workflow workflow skill. Use this skill when the user needs AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "update the changelog", "add a changelog entry", "write a CHANGELOG entry", or when preparing a git commit in StreamFlow that requires updating the `## [Unreleased]` section of `CHANGELOG.md`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify document completeness for each bureaucratic step of an EU/DACH relocation, flagging missing items and translation requirements. Use after creating a relocation plan and before beginning bureaucratic procedures, when preparing for a specific appointment (Buergeramt, Finanzamt), when unsure which documents need certified translation or apostille, after receiving a rejection or request for additional documents, or as a periodic check during the relocation process to ensure nothing has been overlooked.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.