'develop' 검색 결과

Develop independent solutions to a defined problem, compare them against shared requirements, and combine useful contributions into a coherent recommendation. An independent assessment and evidence checks support the selection, while unresolved tradeoffs and verification needs remain explicit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing concrete solutions to a defined problem
• Developing rough options before choosing an approach
• Comparing architectural or product proposals

Reserve remote Android devices on Google's Developer Device Platform and connect through ADB, Android's device control tool. Check session status and expiration, extend usage time, or cancel sessions and release resources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find and reserve a remote Android device
• Connect to a reserved device through ADB
• Check session status and expiration

Operate Agent Zero projects, chats, and tasks, or develop new tools, extensions, and API features. The skill guides work through existing APIs, relevant documentation, current source code, and checks appropriate to the change.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Manage Agent Zero projects and chats
• Develop custom tools and extensions
• Add API endpoints or WebUI features

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a screen to the OpenShell terminal interface
• Fixing log following and scrolling behavior
• Implementing background data updates

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning an agent's requirements and architecture
• Running and debugging an agent locally
• Evaluating responses and tool use before deployment

Carry a software project from requirements and design through implementation, testing, debugging, and deployment. Tracks progress in files, works through features incrementally, and resumes interrupted development, supporting new projects and broad refactoring efforts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a new project from a specification
• Resuming an interrupted development project
• Developing features across multiple implementation steps

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drafts Area Development Agreements granting exclusive multi-unit franchise territory rights with phased development schedules. Use when drafting area development agreements, multi-unit franchise expansions, territorial franchise grants, or phased development commitments. Enforces FTC Franchise Rule compliance and state registration requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Flox로 개발 도구와 데이터베이스의 구성 및 버전을 설정 파일에 정의합니다. macOS와 Linux에서 재현할 수 있는 개발 환경을 만들고 팀과 공유합니다.

• 팀의 개발 환경 통일
• 언어 도구와 시스템 의존성 관리
• PostgreSQL과 Redis 로컬 실행

새 기능이나 제안을 PM, 설계, 개발, QA의 네 관점에서 동시에 검토합니다. 역할별 우려와 첫 행동을 정리하고 공통점과 의견 충돌을 요약합니다.

• 새 기능을 네 역할의 관점에서 검토
• 구현 전 제안의 우려 사항 확인
• 새로운 업무의 첫 행동 정리

개발자용 제품의 문서와 도입 절차를 직접 따라 하며 소요 시간, 오류 메시지와 CLI 도움말을 확인합니다. 증거를 첨부한 평가표로 사용 편의성을 점검합니다.

• 문서와 도입 절차 직접 따라 하기
• 최초 도입에 걸리는 시간 측정하기
• 오류 메시지와 CLI 도움말 점검하기

조사·개발·테스트·시스템 분석을 여러 AI 에이전트에 분담합니다. 역할과 작업 순서를 설계하고 병렬 실행, 진행 상황 확인, 결과 취합까지 다룹니다.

• 병렬 조사 결과를 보고서로 취합
• 앱 설계·구현·검토 연계
• 여러 종류의 테스트를 병렬 실행

실제 소스 코드를 읽고 프로젝트 규모에 맞춰 설치 절차와 사용 예시가 있는 README, API 문서, 구성도, 개발자 가이드와 변경 이력을 정리합니다.

• 설치 절차와 사용 예시가 있는 README를 만듭니다
• 공개 함수의 매개변수와 반환값을 문서화합니다
• 신규 개발자용 구성도와 기여 안내를 만듭니다

요구 사항 정리부터 설계, 테스트 우선 구현, 검토, 배포까지 단계별로 진행합니다. Claude Flow로 여러 에이전트의 역할을 나누고 개발 전반을 관리합니다.

• 요구 사항부터 새 기능 개발
• 테스트와 함께 기존 코드 개선
• 버그 조사와 재발 방지 테스트 추가

Review recent Claude Code chats to identify development strengths, recurring difficulties, and learning priorities. Receive a personalized report with practical recommendations and relevant HackerNews articles, delivered to your own Slack direct messages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing development habits from recent chats
• Prioritizing recurring technical difficulties
• Finding learning articles relevant to current work

Design mock APIs, simulated services that reproduce expected responses, authentication, errors, and delays. Define scenarios and repeatable test data to support frontend development, integration testing, and realistic demos before the real backend is ready.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Developing a frontend before the backend is ready
• Simulating a partner or third-party API
• Preparing a demo with realistic API responses

Plan and develop Android apps with guidance on technology choices, app structure, screen design, testing, debugging, performance, and releases. Covers native Kotlin and Java development alongside Flutter, RN, KMM, and hybrid approaches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing an Android development stack
• Planning app structure and screen design
• Investigating crashes and memory issues