'update' 검색 결과

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

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

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

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

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

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

Progressively activates todo tests one at a time, updates implementation code until each passes (verified via Wallaby), checks off matching design doc progress, then moves to the next—following the design doc as the single source of truth.

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

When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

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

Extract title, summary, steps, related links, and last updated date from a public help center article.

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

Incremental re-specialization — re-scans the project and updates only auto-generated zones in CLAUDE.md and agents

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

既存の .claude/ 体系（CLAUDE.md・Agents・Rules・Skills・hooks）を診断し、理想形との差分を提示して ユーザー承認後に追補・充実させる。「.claude 充実させて」「CLAUDE.md 充実させて」「Agent 整備して」 「claude 体系アップデート」「Rules 追加して」などで使用。新規セットアップは init-claude を使用。 npx skills add 不足分の補完・implement-issue-tree の前提確認・既存資産の破壊なし差分更新が特徴。

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

プロジェクトアイテムのフィールド値 (Status/Priority/Size 他) をクエリフィルタやアイテム指定で絞り込んで一括更新する。SINGLE_SELECT/TEXT/NUMBER/DATE のフィールドタイプに対応。「Status を In Progress に変更」「優先度を一括更新」「Todo を全部 In Progress に」などで使用。

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

既存の GitHub Issue ツリーを棚卸し・更新するスキル。「ツリーを棚卸しして」「イシューツリーを更新して」「トラッキング issue を整理して」で使用。 ルートのトラッキング issue 番号を受け取り、sub_issues API でツリー全体を再帰取得 → closed 親下の残置 open issue 付け替え・孤児の再配置・新 Phase 親の新設・phase ラベル同期 → ルート issue 本文は既存本文を保持し、Phase 別表・棚卸し履歴の管理ブロックのみ更新する。 ツリー新規作成は create-issue-tree、実装消化は implement-issue-tree を参照。

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

OpenAI API (developers.openai.com) の Responses API リファレンス。 text generation, embeddings, gpt-6-astra / gpt-6.1-sol / gpt-6-luna, structured outputs, streaming, function calling, programmatic / async tool calling, conversation state, prompt caching, prompt cache diagnostics, reasoning (configuration_update), background mode, compaction, multi-agent, WebSocket mode (mid-turn steering, stream_id), webhooks, error codes, rate limits, Realtime server controls, 公式 SDK (Python / JS / .NET / Java / Go / Ruby), openai CLI, Chat Completions / Assistants 移行, deprecations。

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

Next.js App Router 専用 API リファレンス（Pages Router / getStaticProps 等は非対応）。 Server Components, Server Actions, layout/page/loading/error ファイル規約, dynamic / parallel / intercepting routes, Metadata API (generateMetadata), Cache Components, use cache, Partial Prefetching, revalidatePath/revalidateTag/updateTag, catchError, next/root-params, ensureStatic, next/image・next/font・next/link, cookies/headers, useRouter, next.config.js, proxy（旧 middleware）。 プラットフォーム実行基盤・CDN・ISR インフラは vercel スキル参照。

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

TanStack Query (React Query) v5 (@tanstack/react-query) の API リファレンス。 useQuery, useQueries, useInfiniteQuery, useMutation, useSuspenseQuery, QueryClient, QueryClientProvider, queryOptions, HydrationBoundary, invalidateQueries, prefetchQuery, skipToken, keepPreviousData, placeholderData, staleTime, gcTime, optimistic updates, SSR / hydration, persistQueryClient, eslint-plugin-query。 kubb（フック生成側）とは別。

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

モデル世代交代の手順（model-roster.md 更新 → ADR-0001 確認 → drift 検査 → agents 更新 → 再測定 → カタログ追記）

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

Debrief a finished Otameshi Tenshoku trial from the employer's side: set the observed facts against the completion criteria agreed before the start, keep expectations added afterwards, second-hand or off-the-job observations and the company's own late or missing support apart, settle the hours actually worked separately from any evaluation, and draft feedback to the candidate that states facts, support gaps and what happens next without promising a hire or continuation the company has not decided. Use when a hiring manager, recruiter or small-business owner wants to review a trial, decide what to tell the candidate, or work out the settlement after a shortfall; do not use to judge the candidate's aptitude or predict a hire, to cut pay or demand unpaid rework because of dissatisfaction, to compare candidates, or to send the feedback, pay, or update records on the user's behalf.

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

Help job seekers use Otameshi Tenshoku to prepare profiles and applications, clarify trial conditions, plan learning visits or paid trial work, and reflect on the experience. Use when a candidate wants to apply for, prepare for, negotiate the scope of, or review an otameshi work experience; do not use to predict whether they will be hired or to judge their aptitude, to state fees, contract terms, or service conditions from memory, or to submit an application, update a profile, or send a message on their behalf. Employer-side requests belong to the employer skills (trial-work-design, trial-listing-draft, applicant-reply and others).

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

Draft or review an employer's Otameshi Tenshoku listing so a candidate can decide whether to apply: check item by item that the work, deliverable, out-of-scope tasks, required experience, support, hours, schedule, location, compensation, contract form and payment timing are stated, find open-ended, unpaid-company-work, guarantee, personal-attribute and unverifiable wording, and confirm that the hours, weekly availability, period, rate and budget hold together. Use when a hiring manager, recruiter or small-business owner wants a listing written from a plan, wants an existing draft or published listing reviewed before or after posting, or wants to know why applications are not coming; do not use to design the work itself (trial-work-design), to reply to applicants (applicant-reply), to state market rates, legal, tax or service conditions from memory, or to post or update the listing on the user's behalf.

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

Reply to an applicant for an employer's Otameshi Tenshoku listing: match the application against the listed requirements item by item on what the applicant actually stated, list the questions still open, and draft an invitation, a request for clarification, a hold notice or a decline that sticks to the listed conditions, keeps other applicants and internal notes out, and presents any new work or dates as a proposal rather than an agreed term. Use when a hiring manager, recruiter or small-business owner has applications to answer, wants to know what to ask before inviting, or has to decline; do not use to judge an applicant's aptitude or predict hiring outcomes, to screen on personal attributes unrelated to the work, to design the work (trial-work-design) or the listing (trial-listing-draft), or to send the message or update applicant records on the user's behalf.

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

Create an implementation plan and a GitHub Issue based on the task description provided as an argument. Use this when the user supplies a natural-language task description (not an issue number) and wants a new implementation-ready Issue. If the input is an existing issue number, use create-issue-from-issue-number (re-analyze) or update-issue (reflect comments) instead.

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

直近N日（デフォルト1日）のPRレビューで繰り返し指摘されている観点のうち「実際に修正すべき」と判断できるものを集約し、リポジトリルートのCODING_GUIDELINES.mdを生成・更新したうえで、commit-push + create-prでPRを作成する。サイズが膨らみすぎないよう既存ルールとの統合・圧縮も行う。

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

Write the merged Pencil design reference back into a UI implementation Issue's description. Takes the Issue number as argument, resolves the merged design PR on the `cc-ui-design-<Issue number>` branch, collects the `.pen` and snapshot paths it added, and appends (or replaces) the `## UIデザイン` section at the end of the Issue body using a lost-update-safe edit.

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

Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), turn the issue into an Epic and split it into sub-issues when its work should ship as separate PRs (cc-epic-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.

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

直近N日（デフォルト1日）に更新された `cc-triage-scope` / `cc-pr-created` ラベル付きGitHub Issueのdescriptionとコメントを横断し、繰り返し現れる仕様判断・要件決定のロジックを再利用可能なルールとして抽出して `.claude/requirements/` 配下のタイプ別マークダウンへ集約・統合・圧縮したうえで、commit-push + create-prでPRを作成する（`cc-triage-scope`ラベル + 自分自身をAssignee）。作成したルールは create-issue / create-issue-from-issue-number / answer-issue-questions が仕様作成・判断の材料として読み込む。

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

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

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