'get started' 검색 결과

Verify which process actually owns a TCP port before assuming your fresh restart succeeded. Use when: (1) you killed an old server and started a new one but behaviour matches the OLD code/data, (2) `pkill -f pattern` returned 0 but old behaviour persists, (3) you embedded a new asset/binary but the served version is stale, (4) any "I just restarted X but I'm getting old results" situation. `pkill -f` matches against the process command line — if the live old process was started with `--port 0` (auto-assigned) and got the port you now want, the pattern won't match it. Always verify with `lsof -i :PORT` before debugging deeper.

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

A zero-risk first Cowork experience for discovering what Cowork does differently. Use when onboarding to Cowork, for getting started safely, during first-time exploration, when starting fresh with a new AI tool, or when the user says "I am new to Cowork", "first task", "show me what Cowork does", "what can you do that Chat cannot", "help me get started", or "safe first task".

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

Provides instructions for integrating the Google Mobile Ads (GMA) SDK. Use this skill when the user wants to get started with, install, integrate, set up, or configure the SDK for AdMob or Ad Manager, GMA Next-Gen SDK or mobile ads framework in an Android, iOS, or Unity application.

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

This skill should be used when the user asks for body doubling, ADHD focus sessions, accountability while working, help getting started on a task, pomodoro-style work sessions, or says things like 'I can't focus', 'I'm stuck', 'help me start', 'I need accountability', 'body double with me', 'I keep procrastinating', 'I can't get started', or 'focus session'. Provides punk-style ADHD body doubling with micro-step protocols, frequent check-ins, dopamine resets, and session history tracking. Part of the ADHD-founder.com ecosystem.

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

Get started with your Open SaaS project — fetches docs, checks Wasp installation, and helps you start your database and app.

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

Analyze the current repo structure, build system, test setup, and conventions to provide a practical onboarding guide. Use when new to a codebase, joining a project, or wanting to understand how a repo is organized. Triggers on getting started, new to repo, onboard, how does this repo work, repo structure, codebase overview.

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

Get started with your Open SaaS project — fetches docs, checks Wasp installation, and helps you start your database and app.

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

Guide users through the get started setup and Chrome DevTools demo.

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

Generates Getting Started guides for PHP projects. Creates step-by-step tutorials for first-time users.

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

.NET testing fundamentals overview and navigation center. Triggered when users ask about "how to write .NET tests", ".NET testing getting started", "required testing tools", "testing best practices", "learn testing from scratch", and other general testing needs. Recommends appropriate sub-skills based on specific requirements, covering testing fundamentals, test data, assertions, mocking, special scenarios, and other 19 fundamental skills. Keywords: dotnet testing, .NET testing, testing getting started, how to write tests, testing best practices, unit test, unit test, xunit, 3A pattern, FIRST principle, assertion, assertion, mock, stub, NSubstitute, test data, AutoFixture, Bogus, validator, FluentValidation, TimeProvider, IFileSystem, code coverage, ITestOutputHelper, test naming

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

Create and render TanStack Table v9 tables in Ember using tracked data and dedicated rendering components. Covers table construction, template access, lifecycle cleanup, and guidance for reusing defaults and UI across tables.

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

• Building a basic table in Ember
• Connecting tracked data updates to a table
• Rendering cells and headers in templates

Create and render Table v9 tables in Svelte 5. Covers basic setup and directs work on reusable components, TanStack Query data integration, and TanStack Virtual rendering, which limits displayed rows or columns for large tables.

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

• Build a basic Table v9 table in Svelte 5
• Organize reusable table components
• Connect tables to TanStack Query data

Create and render Table v9 tables in Solid while preserving reactive data updates. Get guidance on reusable components, Query data integration, and virtualization, which renders only part of a table at a time.

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

• Build a basic table in Solid
• Keep table data reactive
• Reuse table settings and components

Create and render Table v9 tables in Preact, including headers and cells. Get guidance on reusable components, Query data integration, and virtualization, which renders only part of a table at a time.

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

• Build a basic table in Preact
• Reuse table features and components
• Connect server data through TanStack Query

Build and render TanStack Table v9 tables in Alpine, with data updates reflected in the interface. Covers table setup, Alpine markup, cell rendering, and guidance for sharing defaults and reusable UI across tables.

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

• Building a basic table in Alpine
• Reflecting replaced data arrays in a table
• Adding buttons and inputs to table markup

Automate the cmux workspace where an agent was started. It guides explicit targeting of terminals and tabs, reuses helper panes for previews or logs, and reports progress while preserving the user's current focus.

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

• Opening previews or logs in a helper pane
• Running commands in the caller's terminal
• Showing task progress in the sidebar

Set up a new iii backend from engine installation to a working HTTP endpoint. Guides project creation, SDK installation, a first worker in TypeScript, Python, or Rust, and adding existing workers.

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

• Installing iii and creating a new project
• Installing an SDK for the chosen language
• Writing and testing a first HTTP worker

Use for CUDA-Q setup, simulation targets, QPU access, and @cudaq.kernel authoring guidance.

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

Use when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits. Covers payment setup, policy, session budgets, and troubleshooting. Triggers on: "my agent hit a 402 while calling an API", "a tool call returned 402 Payment Required", "my agent needs to pay for x402-protected content", "let the agent pay for content, capped at $5 per session", "set a spend limit for the agent", "ProcessPayment failed", or "why did my agent refuse to pay". Not for BUILDING payment capability for end users, including wallets and framework middleware; use agents-build and references/payments.md. For non-paid APIs via Gateway use agents-connect. For inbound auth use agents-harden. For project scaffolding use agents-get-started.

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

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

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

Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and getting first value, and between upgrading Lattice and adopting its newest conventions. Use when the user says 'lattice init', 'set up lattice', 'initialize lattice', 'get started with lattice', 'configure lattice for this project', 'check for lattice upgrades', or 'upgrade lattice conventions'.

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

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.

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

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.

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

Write a developer quickstart — minimal steps from zero to first successful API call. Use when asked to "write a quickstart", "get users from zero to first API call", or "write a getting started guide".

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