'dev' 검색 결과

Manage the AI models offered through OpenWork, including model additions, removals, aliases, and pricing discounts. Validate configuration consistency and trigger the GitHub workflow that refreshes models from models.dev, then report its merge or failure result.

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

• Adding or removing models offered through OpenWork
• Changing the charged price fraction for specific models
• Checking consistency between model lists and aliases

Investigate crashes, out-of-memory errors, and device initialization failures on GKE TPU v6e nodes. The skill checks logs and custom metrics collection for conflicting operations, then guides temporary mitigation by disabling an identified collector.

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

• Investigate vbar_control_agent crashes and memory exhaustion
• Check tpu-device-plugin metrics checksum errors
• Inspect conflicts with custom TPU metrics collectors

Add and configure an inspection panel for Vue json-render apps. This skill guides setup and troubleshooting so you can inspect UI definitions, edit state, review action and stream timelines, browse catalogs, and select page elements.

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

• Adding an inspection panel to a Vue app
• Inspecting UI definitions and editing state
• Reviewing action and stream timelines

Add and troubleshoot the json-render inspection panel in SolidJS applications. This skill covers panel setup for examining specifications, editing state, reviewing action and stream timelines, browsing component catalogs, and selecting page elements for inspection.

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

• Add an inspection panel to a SolidJS app
• Inspect JSON specifications and edit application state
• Review action and stream timelines

Set up an inspection panel in React json-render apps to examine UI definitions, edit state, and review action and stream timelines. The skill also covers opening or toggling the panel and recording events from React code.

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

• Adding an inspection panel to a React app
• Inspecting UI definitions, state, and action history
• Opening or toggling the panel from React code

Create and run KubeSphere DevOps pipelines connected to Jenkins to automate builds and tests. Covers branch-specific workflows, required input parameters, private repository credentials, execution monitoring, logs, and downloading build output files.

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

• Create a pipeline that builds and tests a Go application
• Run builds for individual repository branches
• Configure credentials for a private repository

Manage credentials for Git access and deployments in KubeSphere DevOps. Covers SSH keys, passwords, API tokens, and Kubernetes connection settings, including their use in Jenkins pipelines and troubleshooting synchronization failures.

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

• Register credentials for private Git repositories
• Use deployment credentials in Jenkins pipelines
• Investigate credentials missing from Jenkins

Assess Bluetooth Classic devices such as older car kits, industrial sensors, and audio accessories. The skill guides device discovery, service inspection, authentication checks, and known vulnerability assessment, helping document exposed functions and device-specific findings.

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

• Assessing older in-car Bluetooth devices
• Checking authentication on industrial device services
• Reviewing exposure to BlueBorne and KNOB

Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

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

Expert knowledge for Azure DevTest Labs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing lab VM images, ARM/CI-CD automation, RBAC/Key Vault security, hub-spoke networking, or quotas, and other Azure DevTest Labs related development tasks. Not for Azure Lab Services (use azure-lab-services), Azure Dev Box (use azure-dev-box), Azure Virtual Machines (use azure-virtual-machines), Azure Virtual Desktop (use azure-virtual-desktop).

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

Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".

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

Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

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

Use when an admin or partner needs to package an Experience Cloud (Community) site as a reusable Lightning Bolt Solution for distribution — covers the export workflow from Experience Builder, what gets bundled (ExperienceBundle, custom apps, flow categories, theme, layouts, navigation menus) versus what does NOT (data, CMS content, files), choosing Bolt vs managed package vs unlocked package vs cloning a site, sandbox-to-production promotion, multi-org distribution, AppExchange listing as a Bolt, and template versioning via the LightningBolt metadata `versionNumber`. Triggers: 'turn this community into a reusable template', 'package an Experience Cloud site to ship to multiple orgs', 'export Experience Builder template for AppExchange', 'should we use a Bolt or a managed package for this community', 'create an industry-specific community starter', 'how do we version our partner portal template', 'distribute branded Experience site across business units'. NOT for general Experience Cloud site build, content, or member setup (use admin/experience-cloud-site-setup, admin/experience-cloud-cms-content, admin/experience-cloud-member-management). NOT for shipping Apex / LWC / data-model functionality as a product (use devops/managed-package-development, devops/second-generation-managed-packages, devops/unlocked-package-development). NOT for moving a single Experience site between sandbox and prod as a one-off (use devops/experience-cloud-deployment-admin, devops/cicd-for-experience-cloud).

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

pen.dev CLI（`pencil` / `pen`コマンド）だけを使って.penファイル（pen.devで作成されたデザインファイル）を`execute`による決定論的な編集操作で修正・更新・新規作成するスキル。.penファイルの編集、ボタン追加、レイアウト変更、UIデザインの調整、pen.devデザインの更新、新しい.penデザインの作成などの依頼で必ず使用する。有料の`--prompt`（エージェントモード）は使わず、編集・新規作成はすべてインタラクティブモード（`pencil interactive`）の`execute`（`Insert` / `Update` / `Delete` など）で行い、最後に`save()`する。`Insert` / `Update` に渡すNodeデータは`references/pen-format.md`の.penフォーマット定義に従う。既存ファイルは`-i`と`-o`に同一パスを指定して上書き、新規作成は`-i`を省略して`-o`に新しいパスを指定する。編集・作成後は「**編集・作成したコンポーネントのNodeだけ**」を`execute`の`Export` / `TakeScreenshot`でPNG出力し、`.pen`と同階層の`snapshots/`ディレクトリに保存する。pen.dev MCPには依存せず`pencil`コマンドのみで完結する。.penファイルのgitコンフリクト解消・破損復旧は本スキルではなく`resolve-pencil-conflict`スキルの担当。

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

DevinへのGitHub作業の委譲と成果をCodex内ブラウザで確認し、レビュー・修正依頼・PRマージ・環境提案の採用・ローカル同期まで進める。画面での確認や操作を含むDevinへの依頼・成果採用に使う。送信や回答の取得には公式Devin MCPを優先し、相談だけ・PR作成まで等の指定を守る。

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

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

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

プロダクトアイデアをJTBD分析→競合調査→SLC仕様書に構造化。 dev:storyの上流で使用し、何を作るべきかを明確にする。 「アイデアを整理」「/dev:ideation」で起動。 Trigger: アイデア整理, プロダクト企画, /dev:ideation, ideation, 何を作るべきか

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

여러 Claude Code 에이전트에 개발 작업을 나누고 독립된 작업 환경에서 병렬로 실행합니다. 작업 의존성과 진행 상황, 변경 사항과 오류 보고서를 관리합니다.

• 의존성을 포함한 개발 계획 나누기
• 독립된 작업 환경에서 병렬 개발하기
• 여러 개발 작업의 진행 상황 확인하기

Review plans for APIs and developer tools through the eyes of their users. Explore developer needs, compare competitors, and identify onboarding friction, with modes for competitive differentiation, detailed refinement, or critical gaps.

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

• Reviewing an API or SDK plan
• Finding friction in developer onboarding
• Comparing developer experience with competitors

Test browser interfaces through Chrome DevTools MCP, a connection that lets an agent inspect a live browser. Check screenshots, errors, network traffic, accessibility, and performance to diagnose problems and verify fixes.

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

• Diagnosing layout and styling problems
• Investigating browser errors and failed API requests
• Comparing screenshots before and after a fix

Review JavaScript written directly in HTML and move suitable code into external files. Replace inline event handlers with addEventListener, clarify browser verification steps, and explain how separating code supports maintenance, caching, and security.

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

• Moving JavaScript out of HTML markup
• Replacing onclick handlers with addEventListener
• Reviewing script separation for caching and maintenance

Create, review, migrate, or troubleshoot Azure Developer CLI projects. Align application settings, infrastructure definitions, deployment environments, secrets, and automated delivery workflows while checking that configuration files and deployment requirements agree.

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

• Creating an Azure Developer CLI project structure
• Reviewing azure.yaml against Bicep or Terraform definitions
• Organizing environment settings and secret handling

Prepare medical device regulatory work for the US FDA. Compare submission routes, organize required documents, review quality management requirements, assess patient data safeguards under HIPAA, and plan device cybersecurity documentation and controls.

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

• Compare 510(k), PMA, and De Novo submission routes
• Organize required 510(k) documents and submission milestones
• Review quality documentation against QMSR and ISO 13485:2016

Set up and run Happy components locally, including its CLI, server, mobile app, and desktop app. The guide covers building, testing, checking logs, and separating development data using pnpm, the project's package management tool.

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

• Setting up a local Happy development environment
• Rebuilding the CLI and checking its daemon
• Running the server and app locally