'getting-started' 검색 결과

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

邀请加入后的第一次对话，或记忆里还没有你的偏好时使用：了解需要、补齐必要连接，尽快交付第一份结果。

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

Designs a resilience program: how to structure and standardize resilience policies across an organization, team, or portfolio (tiered policy model with availability/RTO/RPO targets and DR approach selection), and how often to run resilience activities (operational cadence). Applies when the user asks how to structure policies org-wide, what tiers/targets to set, which DR approach fits a tier, or how frequently to run assessments, FIS experiments, GameDays, or autoshift practice. Does not apply to creating or configuring a specific policy or resource for a single workload (use resilience-hub-getting-started), to step-by-step lifecycle execution (see aws-resilience-lifecycle), or to service-specific setup.

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

Runs and interprets AWS Resilience Hub v2 failure mode assessments. Covers starting assessments, understanding findings (severity, categories, recommendations), triaging by achievability, working with AI-generated service functions, and resolving findings. Applies when the user wants to run an assessment, review findings, or understand failure modes, or has a specific finding and asks how to resolve, remediate, or fix it. Does not apply to initial setup (use resilience-hub-getting-started) or FIS experiments.

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

Sets up AWS Resilience Hub v2 from scratch: creates resilience policies with SLO targets, registers systems and user journeys, onboards services with input sources, and runs a first failure mode assessment. Applies when the user wants to get started with Resilience Hub v2, create a policy, onboard a service, or run an assessment — including creating one concrete policy with specific availability/RTO/RPO targets and a DR approach for a single service (even a tier-1 one). Does not apply to FIS experiments or ARC routing controls.

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

Prove the smallest safe Attio REST connection by listing objects and validating the response envelope without changing CRM data. Use when checking a new token, workspace, or integration path. Trigger with "Attio hello world", "first Attio request", or "test Attio connection".

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

Create a minimal Algolia JavaScript v5 indexing and search proof using a disposable index. Use when verifying credentials, learning the client boundary, or proving first connectivity. Trigger with "Algolia hello world", "first Algolia search", or "test Algolia setup".

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

Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill to use. Never manually edit website docs without cross-validating flags against Go source first.

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

House style for user-facing documentation — voice, scope, structure, and what to leave out. Use this skill whenever writing, editing, or reviewing anything a user reads to learn how to use a tool — help center articles, getting-started guides, tutorials, feature docs, README usage sections, in-app help, release notes, or FAQ entries. Trigger it even when the request is phrased plainly — "document this feature", "write docs for X", "explain this to users", "write a README for this library", "turn these notes into a guide" — and even when no style guidelines are mentioned. Also use it to review existing docs for tone, bloat, or leaked implementation detail. Do not use it for internal engineering docs, architecture write-ups, RFCs, or code comments.

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

Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.

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

Validates the user's environment for SageMaker AI operations — checks SDK version, AWS region, and execution role. Use when the user says "set up", "getting started", "check my environment", "configure SDK", or as the first step in any plan involving SageMaker/Bedrock training, evaluation, or deployment.

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

First-run setup. Detects configured API keys, points to the local setup-keys script for secure key entry, and shows sample prompts scaled to available tools.

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

当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论（constitution → specify → clarify → plan → tasks → write → analyze）

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

When the user needs to create help center articles, FAQs, troubleshooting guides, API documentation, or getting-started guides for customers.

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

The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.

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

Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.

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

Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building a notebook or app, or running the full onboarding pipeline. Time budget ≤15 min autonomous, ≤90 min HITL. Does NOT cover Cypher query authoring — use neo4j-cypher-skill. Does NOT cover driver upgrades or Cypher migration — use neo4j-migration-skill. Does NOT cover CLI/admin tasks on an existing DB — use neo4j-cli-tools-skill.

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

Migrates Neo4j driver code and Cypher queries from older versions (4.x, 5.x) to current (2025.x/2026.x, Cypher 25). Covers Python, JavaScript/Node.js, Java, .NET, and Go drivers — package renames, removed APIs, version requirements, diff-ready fixes. Also handles Cypher syntax migration — QPE paths, CALL subqueries, id() → elementId(), PERIODIC COMMIT → CALL IN TRANSACTIONS, and all Cypher 25 removals. Does NOT write new Cypher queries — use neo4j-cypher-skill. Does NOT cover DB administration or server ops — use neo4j-cli-tools-skill. Does NOT provision new Neo4j instances — use neo4j-getting-started-skill.

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

Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs, scaffold a /trigger directory with a first task, wire tsconfig and .gitignore, set TRIGGER_SECRET_KEY, and run the dev server. Load this when a project has no trigger.config.ts yet and the user asks to "add Trigger.dev", "set up Trigger.dev", "initialize Trigger.dev", or get a first task running, including in a monorepo. Once the project is set up and you are writing task code, switch to the trigger-authoring-tasks skill.

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