「name」の検索結果

Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and cross-references a rename breaks, and report broken symlinks and stale name references. Use when the user says "organize my skills", "rename these skills", "clean up the skill library", "enforce a skill naming convention", or "fix broken skill symlinks".

日本語の概要は準備中です。原文の説明を表示しています。

Fix silent failures in Fastly Compute@Edge when using send_async for fire-and-forget requests. Use when: (1) Background tasks (migrations, webhooks, notifications) triggered from Compute never complete, (2) send_async PendingRequest is immediately dropped, (3) Fire-and-forget pattern works locally but fails in production, (4) An async trigger "logs as triggered" but the target service never receives the request (especially after renaming backend constants — the URL hostname is cosmetic, the backend name determines routing, so a global rename can silently reroute calls to the wrong service). Also covers silent backend-not-found errors when FALLBACK_BACKENDS or other backend constants reference names not configured in the Fastly dashboard.

日本語の概要は準備中です。原文の説明を表示しています。

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

日本語の概要は準備中です。原文の説明を表示しています。

Sets up {module-name} module in a project. Use when the user requests to 'install {module-code} module', 'configure {module-name}', or 'setup {module-name}'.

日本語の概要は準備中です。原文の説明を表示しています。

Discover and load skills on demand from /mnt/skills/user/. Use when you need a capability but don't know which skill provides it, when the boot-emitted skill list is names-only and you need a full description, or when you want to list the catalog. Verbs are list (names only), search (rank by name/description match against a query), and show (emit the full SKILL.md for a named skill).

日本語の概要は準備中です。原文の説明を表示しています。

ALWAYS start here when the user wants a page OR a doc: page, living page, doc, document, living doc, bongo or bongo doc (the old name; new ones are made here, not by a Bongo connector), shared or collaborative doc, write-up, one-pager, memo, brief, proposal, plan, spec, report, meeting notes, notes, checklist, tracker, or anything to read, edit, comment on and share together — 'write this up', 'put this in a doc', 'draft a brief', 'jot this down somewhere we can share and edit', 'turn this file into a page' — the DEFAULT for any of these when no file format is named; a Word/.docx, PDF, .pptx or .xlsx FILE asked for by name goes to that format's skill instead. Also whenever the pages connector is about to be used to create a page. Not for READMEs, code or docstrings. A lowercase /pages as its own word anywhere in the message (not in a URL, path or longer name) invokes this skill whatever else is asked — a summary, an answer, a comparison, a plan: the page is the reply.

日本語の概要は準備中です。原文の説明を表示しています。

Use when looking up journal or magazine name abbreviations, converting between full names and ISO 4/MEDLINE abbreviations, processing BibTeX files for journal name standardization, or answering questions about 期刊缩写/杂志缩写. Triggers on "journal abbreviation", "abbreviate journal", "journal name", "期刊缩写", "杂志缩写", "ISO 4", "LTWA", "BibTeX journal". PROACTIVELY USE when user mentions citation formatting, reference list preparation, or manuscript submission to specific journals.

日本語の概要は準備中です。原文の説明を表示しています。

Universal dispatcher: run a named taffy workflow (.claude/taffy/<name>.yaml), a skill (/skill-name), or a sub-agent (@agent-name). Falls back to skills.sh registry when a skill is not found locally. Tracks all runs in .claude/state/maple.json so the maple TUI shows live progress.

日本語の概要は準備中です。原文の説明を表示しています。

スライドの中身（シナリオ・構成案）をClaudeとの壁打ちで作成し、SLIDE-SCENARIO-{name}.mdとして出力する。レビュアー視点でのシナリオレビュー、資料を見せる相手のペルソナ定義（PERSONA-{name}.md）の作成にも対応する。slide-deck-builderの前段を担うスキル。「スライドのシナリオを作って」「構成案を壁打ちして」「プレゼンの構成を考えて」「シナリオをレビューして」「ペルソナを作って」「slide-scenario-creator」と言われたときに使用する。Use when user says "create a slide scenario" or "review my presentation outline".

~/.claude/skills/ や任意のパスにあるスキルを claude-code-plugin リポジトリの 正しいディレクトリ構造 (<category>/<name>/skills/<name>/SKILL.md) にコピー・配置するスキル。 スキルの構造検証、既存スキルとの重複チェック、配置後の確認も行う。 Use when: スキルをプラグインリポジトリに公開したい、スキルを移動したい、 スキルをパッケージ化したい、スキルを整理したい。 Triggers: "スキルを公開", "プラグインに追加", "skill publish", "スキルを移動", "claude-code-plugin に追加", "スキルをコピー", "パッケージ化"

アプリ名・サービス名の命名を、5つの専門エージェントチームで多角的に評価・決定するスキル。 ブランディング、商標/法的リスク、デジタルプレゼンス(SEO/ASO/SNS)、国際展開(多言語/発音)の 4観点から候補を提案・調査・議論し、コンテキストファイルと議事録で次回セッションへ引き継ぐ。 Use when: アプリ名を決めたい、サービス名を変更したい、プロダクト名を検討したい、 ネーミングブレスト、名前の商標チェック、アプリ名のリネーム。 Triggers: "アプリ名", "サービス名", "プロダクト名", "ネーミング", "名前を決め", "リネーム", "rename", "app name", "naming", "ブランド名", "商標チェック"

Top username lists for enumeration: common usernames, default credentials, names. Curated essentials for authorized testing.

日本語の概要は準備中です。原文の説明を表示しています。

Fuse all of a contributor's named skills into a single fusion node (suite capstone) in the registry. Use when the user says "fuse <contributor>'s skills", "create a suite for <contributor>", "build a capstone for <user>", "fuse all of <user>'s named skills", "create a suite fusion", "consolidate <contributor> into one skill", or explicitly types /gaia-fuse-full-suite. Also triggers when a contributor has accumulated 3+ named skills and the user asks what to do next with them, or when someone asks "can we make a suite from these?". This skill: collects component IDs from registry/named/<contributor>/, verifies nodes exist, researches evidence and appraises Trust Magnitude, runs `gaia dev fuse` to write the fusion node and suite manifest, validates, and opens a PR on a review/meta/ branch.

日本語の概要は準備中です。原文の説明を表示しています。

Use this whenever a new file/folder is created or renamed in this Vue project, when reviewing a module for consistency, or when the right path for a file is unclear. Also triggers on "what should I name this?", "is this file named correctly?", "audit module naming". Enforces kebab-case folders, dot-prefixed `{module}.{name}.{type}.vue|js` files, multi-entity rules, singular vs plural for views, and the layered structure UI → Store → API.

日本語の概要は準備中です。原文の説明を表示しています。

Use when configuring OmniStudio at the org level: enabling Standard Runtime, selecting the Runtime Namespace, assigning Permission Set Licenses, toggling feature settings, and granting Experience Cloud community access. Trigger keywords: OmniStudio Settings, Standard OmniStudio Runtime, managed package runtime, runtime namespace, OmniStudio Permission Set, OmniStudio PSL. NOT for moving an org off the vlocity namespace — use omnistudio/vlocity-to-native-omnistudio-migration. NOT for deciding whether to adopt OmniStudio — use architect/omnistudio-vs-standard-decision.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing, reviewing, or troubleshooting Salesforce connected apps, External Client Apps, Named Credentials, External Credentials, and OAuth-based integration access. Triggers: 'connected app', 'OAuth flow', 'client credentials', 'JWT bearer', 'Named Credential', 'External Credential', 'integration user', 'IP restrictions', 'connectedApp-meta.xml', 'ExternalClientApplication', 'ExtlClntAppOauthSettings', 'isAdminApproved', 'refreshTokenPolicy', 'ipRelaxation', 'consumer key', 'consumer secret', 'permittedUsersPolicyType'. NOT for OAuth error codes you are already seeing — use admin/connected-app-troubleshooting. NOT for External Credential principal-type setup steps — use integration/named-credentials-setup.

日本語の概要は準備中です。原文の説明を表示しています。

Detects app name violations including names exceeding 30 characters, beta labels, Apple trademark terms, and version numbers in the display name, enforcing Guideline 2.3.7.

日本語の概要は準備中です。原文の説明を表示しています。

新生儿起名/取名：为宝宝取 5 个精选名字备选并给出详细理由。用户提供**姓氏**（必填）、 **性别**（必填）、**期望寓意方向**（必填），可选**出生日期时辰**、**父母姓名**、**辈分字/家族传统**。 流程：交互收集信息 → 有生辰则用脚本排八字五行、判喜用 → 从《诗经》《楚辞》《论语》《周易》、 唐诗宋词、四书道家等古籍素材与取名字库中选字组名 → 按「音韵和谐·避免谐音·书写便利·性别适配· 寓意美好」五大原则用脚本逐项体检 → 有父母姓名则做家族合参/避讳 → 给出 5 个各有侧重的名字及理由。 Use this skill whenever the user wants to name a baby / newborn, pick a Chinese given name, or asks 起名、取名、改名参考、给宝宝起名、取个名字、名字寓意、生辰八字取名、诗经取名、楚辞取名. Triggers: "起名", "取名", "起个名字", "给宝宝取名", "新生儿起名", "婴儿起名", "取名字", "宝宝名字", "按八字起名", "诗经取名", "楚辞取名", "帮我孩子起名", "baby name", "Chinese name". 即使用户只是随口说「帮我娃想个名字」「取个有寓意的名字」，也应主动使用本技能。

日本語の概要は準備中です。原文の説明を表示しています。

Marketing de produto, posicionamento, estratégia GTM e inteligência competitiva. Inclui definição de ICP, metodologia de posicionamento April Dunford, playbooks de lançamento, battlecards competitivas e guias de entrada em mercados internacionais. Use ao desenvolver posicionamento, planejar lançamentos de produtos, criar mensagens, analisar concorrentes, entrar em novos mercados, capacitar vendas ou quando o usuário menciona marketing de produto, posicionamento, GTM, go-to-market, análise competitiva, entrada em mercado ou capacitação de vendas.

日本語の概要は準備中です。原文の説明を表示しています。

Solves complex, open-ended problems using a knockout tournament mechanism. Generates an initial population of diverse candidate answers, pairs them into head-to-head matches, produces a hybrid "child" solution from each pair, and advances the best of the three through a bracket until a winner emerges. Use this skill whenever the user wants to competitively select the best answer from a field of alternatives, asks for a "tournament" or "bracket" style search, wants a faster alternative to full evolutionary search, or uses phrases like: "run a tournament on this", "bracket-style search", "let solutions compete", "knockout search", "find the best answer by elimination", or "which solution wins?". Also trigger when the problem is open-ended and the user wants a clear winner quickly rather than a deep multi-generation refinement.

日本語の概要は準備中です。原文の説明を表示しています。

Claude Code の並列エージェント(agent teams・teammate)の後始末と無応答時の打ち切りルール。`name` を付けて Agent を起動するとき、TeamCreate でチームを組むとき、teammate から `idle_notification` が届いたとき、評価ループ等で次のイテレーションのエージェントを起動する前、エージェントの返信が届かないときに参照する。`name` を付けない通常のサブエージェント起動だけなら対象外。

Find a person, lead, contact or company by name in any spelling: a deterministic search that catches transliteration across alphabets, wrong-keyboard-layout typing and typos. This is the exact-name lane (zero tokens), complementary to semantic vault search. Triggers: "/find <name>", "show everyone named <X>".

日本語の概要は準備中です。原文の説明を表示しています。

Distill an already-built or near-launch product into one incisive brand kernel — the "reveal" already hiding in its name, story, or the product itself — then build the name, voice, visual identity, and a developer-ready handoff kit around it. This is LATE-STAGE branding: use it when there is a real, thought-through product that is about to launch, or already live but not explained in a way people grasp in an instant. Use whenever the user wants to name or rename a product, find a tagline or slogan, create a brand identity / brand kit / style guide / design system, design a logo, wordmark, palette, or type system, mock up a homepage for a launch, or hand brand assets to a coding agent (Claude Code, Codex, Cursor). Trigger even when the user only says their product needs to "land" or "feel like" something, or that they can't explain it simply yet. Do NOT use for half-baked, pre-product ideas with nothing to excavate — this skill extracts a kernel that already exists; it does not invent one from a blank canvas.

日本語の概要は準備中です。原文の説明を表示しています。

Modify or debug s6 services in the OpenAmer Docker image.

日本語の概要は準備中です。原文の説明を表示しています。