'help' 검색 결과

Get answers about Qwen Code usage, features, configuration, and troubleshooting from its official documentation. The skill also helps inspect and edit user or project settings files when configuration changes are requested.

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

• Learning Qwen Code features and commands
• Checking how to configure MCP server connections
• Reviewing or changing settings.json

Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.

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

• Create a base library of test helpers
• Share repeated test setup and result checks
• Generate object factories for a specific game system

Organize Playwright tests with guidance on Page Object Model, a pattern that groups code by page. Learn how to structure page objects and decide when fixtures or helpers offer a simpler approach.

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

• Organizing Playwright test code
• Choosing whether to introduce page objects
• Comparing POM, fixtures, and helpers

arkcli helper：为 Claude Code / Codex / OpenCode / OpenClaw / Hermes / ZCode 配置火山方舟 Plan 或 Platform Endpoint 的 model/provider，或给支持的 Agent（含 MCP-only Trae）配置 Harness 工具。真人 TTY 运行 `arkcli helper` 可选择模型和 Harness 能力；`helper mcp` 默认保持整组 Agent Plan MCP 行为，传 `--capability datapro|web-search|agent-memory` 只配单项，传 `--capability cua` 只给目标 Agent 安装云电脑 Skill；连 model/provider 一起配置用 `helper configure`，查状态用 `helper list`，移除用 `helper reset`。Agent Plan / Team 还支持专业数据集、豆包搜索、Agent 记忆、AI Native 应用开发底座、Agent 进化与 routing.v1 强制检索路由；上下文出现 ARKCLI ROUTING ENFORCEMENT / routing.v1，或用户要求在豆包搜索、DataPro、OpenViking、Supabase 之间强制分流时也使用本 Skill：调用这四类受管 Provider 前先提交 Route Plan，再调用唯一授权 Provider；原生 WebSearch/WebFetch/WebExtract 位于路由管理范围之外。Platform 只允许本人创建、Running、已验证为文本输出的 Endpoint，不配置 MCP、Supabase 或强制路由。豆包搜索配置成功后默认关闭目标客户端原生 WebSearch；传 `--keep-native-websearch` 可保留，并可用 `helper reset` 完整恢复 ArkCLI 配置。

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

Look up available GSD commands and how to use them. Choose a quick reminder, a one-page overview, a complete reference, or help focused on a single topic.

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

• Get an overview of available GSD commands
• Check command usage with a quick reminder
• Read the complete GSD reference

ponytail의 세 가지 작동 수준과 관련 스킬, 실행 명령을 참조 카드로 확인하고 활성화·해제, 기본 모드 설정과 업데이트 방법을 찾아봅니다.

• 세 가지 작동 수준을 비교합니다
• 관련 스킬의 호출 명령을 확인합니다
• 기본 모드 설정 방법을 확인합니다

Discover the tools, workflows, specialist agents, and hooks available in a configured workspace. Interactive guidance and topic-specific commands help you choose relevant capabilities, inspect usage examples, and understand customization options.

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

• Find workspace capabilities that match a task
• Browse development workflows and specialist agents
• Understand active hooks and their roles

답변을 짧게 만드는 모드와 커밋 메시지, 검토 댓글, 문서 압축 관련 명령을 확인합니다. 현재 모드 조회, 해제, 기본 모드 설정 방법도 안내합니다.

• 답변 모드 명령 확인
• 커밋 및 검토용 명령 확인
• 일반 답변으로 복귀

Review help links, chat controls, phone numbers, and FAQ entry points across related pages. Compare their relative positions and order under matching layout conditions, then identify changes that make support easier to find throughout a task.

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

• Reviewing help placement throughout checkout
• Aligning support links across onboarding steps
• Checking help entry points during account recovery

Find available MemPalace commands, usage tips, and getting started guidance. This skill retrieves the help instructions and follows them step by step to guide users through the basics of using MemPalace.

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

• Getting started with MemPalace
• Checking available commands
• Reviewing usage tips

Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of need), and contextual-when-needed (surfaces help at the moment friction occurs) patterns. Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform. Also triggers when feature adoption is low, when users miss key product capabilities, or when an in-product help system is being scoped for the first time.

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

Write, update, and verify Datagrok help pages (help/, Docusaurus), including GIFs and release updates. Use for user documentation of a platform feature, a GitHub issue, or a Jira ticket, for bringing the help up to date with a release, and for recording or replacing help GIFs.

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

Use this skill when designing the UX and content strategy for a Salesforce-powered self-service portal or help center — pre-deflection article surfacing, Help Center search UX, friction-calibrated case submission forms, community peer support layers, and deflection measurement. Trigger keywords: design self-service portal, case deflection strategy, help center UX design, reduce support volume with self-service, knowledge base search experience. NOT for picking which contact reasons to deflect and through which channel — use architect/case-deflection-strategy. NOT for building the Experience Cloud site itself — use admin/experience-cloud-site-setup. More trigger keywords: article visibility matrix IsVisibleInCsp IsVisibleInPkb, which articles show in the customer portal, case visibility for portal users, CaseComment IsPublished customer visible comment, self-registration profile and account for a portal, Help Center template does not support login, deflection metrics SOQL KnowledgeArticleViewStat, self-service journey map, moderation policy for a support community.

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

Find answers about Codewhale commands, settings, skills, and keyboard shortcuts using the installed help and configuration tools. For environment problems, consult diagnostic output to explain what the current installation actually supports.

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

• Check how to use a Codewhale command
• Find settings and keyboard shortcuts
• Diagnose configuration and credential issues

Help junior developers and AI newcomers understand code through guided questions and progressive hints. Support debugging, concept learning, and critical review of AI-generated code so learners can explain their reasoning and work toward solutions themselves.

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

• Understand errors through guided questions
• Explain AI-generated code in your own words
• Learn with pseudocode and progressive hints

Find the next step in a game development project by checking workflow records, existing documents, and task status. Get one main recommendation with a command, plus a brief view of completed work and upcoming tasks.

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

• Finding the next task after a development milestone
• Resuming work from the previous session
• Checking which unfinished task needs attention first

Build dashboard panels in plain TypeScript with automatic retries, saved panel settings, and clear error states. Keep panel-specific helper functions in the same file to make each component easier to understand and maintain.

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

• Build a panel that retries failed data requests
• Save panel dimensions and expanded or collapsed state
• Keep time and status formatting helpers beside panel code

Helps users get started with Onchain OS, find OKX.AI role registration guidance, or reach support resources. It identifies the purpose of a question and routes it to the appropriate guide.

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

• Getting started with Onchain OS
• Finding OKX.AI role registration guidance
• Finding support for bugs, complaints, or feedback

Find your way around Diverga with a guide to its 24 research agents across nine categories. View commands, example requests, direct invocation syntax, and checkpoints where people review research decisions, with recommendations based on research context.

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

• Explore Diverga's research agents
• Find commands for setup and diagnostics
• Choose an agent for a research task

Guide a setup process one step at a time in plain English. Each response provides the current actions and required values, followed by a short list of remaining stages that updates as the user progresses.

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

• Follow a setup process one step at a time
• See required values for the current form
• Keep track of remaining setup stages

Draft SEO-focused blog posts, landing pages, and website copy from a keyword or topic, or improve an existing page. Follow Google's guidance on helpful content and experience, expertise, authority, and trust.

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

• Draft a blog post from a keyword or topic
• Write landing pages and service pages
• Improve or rewrite existing website content

Generate or improve MATLAB help text (documentation comments) for a function, class, or script file following MathWorks standards (H1 line, syntax paragraphs, See Also, 75-char lines). Read BEFORE writing MATLAB help — default patterns (Inputs:/Outputs: lists, block comments, uppercase See Also) produce non-conforming output. Use when writing, rewriting, fixing, or reviewing MATLAB help comments or function documentation.

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

Provides patterns for testing utility classes, static methods, and helper functions. Validates pure functions, null handling, edge cases, and boundary conditions. Generates AssertJ assertions and @ParameterizedTest for string utils, math utils, validators, and collection helpers. Use when testing utils, test helpers, helper functions, static methods, or verifying utility code correctness.

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

Write or update the CLI `--help` text and README section for a new or changed rezolus feature (a subcommand, flag, mode, or behavior change), then prove the help is usable by dispatching a fresh subagent that has never seen the code. Use this whenever you add or change how rezolus is invoked — new `rezolus <subcommand>`, new flags/args on an existing mode, renamed options, or changed defaults — and any time the user says the help/README is thin, stale, confusing, or "an agent couldn't figure this out." Treats help text as an interface under test, not prose.

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