4,968 件 ・ 関連度順
概要と使いどころ
Create and optimize Claude Code subagent files (.claude/agents/*.md) following official best practices. Use when user asks to create a subagent, agent file, custom agent, or needs help structuring agent files with YAML frontmatter.
日本語の概要は準備中です。原文の説明を表示しています。
Generates Agent definitions (.md files) based on user intent and standard templates.
日本語の概要は準備中です。原文の説明を表示しています。
Add new learning resources (books, articles, courses, papers) to the appropriate resources.md file. Use when user mentions adding, saving, or tracking learning materials.
日本語の概要は準備中です。原文の説明を表示しています。
One line — used in CLAUDE.md system-reminder and the skill catalog.
日本語の概要は準備中です。原文の説明を表示しています。
Многотуровый диалог писателя (Claude) с одним или несколькими напарниками (любой набор из kimi/codex/hermes/claude-headless) по задаче пилота (DP.SC.154). Ведёт turn-loop (2 участника) или round-loop (3+, WP-509), обнаруживает CONSENSUS/ESCALATE, после консенсуса — Decision Gate (зафиксировать vs реализовать → ревью → проверить → задеплоить), синтезирует report.md через Agent tool.
日本語の概要は準備中です。原文の説明を表示しています。
Аудит пользовательской инсталляции IWE. Запускает scripts/iwe-audit.sh + MCP healthcheck + smoke-test ритуала через sentinel-механику (контракт dry-run-contract.md), передаёт отчёт subagent'у в роли VR.R.002 Аудитор (context isolation) → verdict ✅/⚠️/❌ по 6 компонентам (Inventory, L1 drift, {{GOVERNANCE_REPO}}, L3 customizations, MCP, ритуал). Используй после restore из бэкапа, после update.sh, или при еженедельной сверке.
日本語の概要は準備中です。原文の説明を表示しています。
Сверка журнала гипотез (hypotheses-log.md) по запросу вне ритма week-close. Фильтрует записи со статусом «на сверке» и наступившей датой, сверяет критерий фальсификации с доступной фактурой, предлагает вердикт, пилот подтверждает, вердикт пишется новой записью. Вызывать на явную фразу пилота, не автоматически.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new IWE skill with proper frontmatter, gates, scaffold and verification. Use when the pilot says: /skill-creator or «создай скилл <name>». The skill enforces WP Gate precondition, Routing Gate, IntegrationGate hard-check, collects parameters in 4 short steps, generates a scaffold SKILL.md from a template, shows a draft, writes files, and reminds about verify-skill.sh.
日本語の概要は準備中です。原文の説明を表示しています。
Стратегическая сессия — диспетчер. День-0 (маркер IWE-INITIAL-NEEDED или нет Strategy.md/WeekPlan) → initial flow (цели, неудовлетворённости, первый WeekPlan). Первая сессия календарного месяца → полный monthly flow (стратегическая сверка + линза калибра). Остальные дни → короткий weekly flow (требует черновик от session-prep). Триггеры — «проведём стратегическую сессию», «первая стратегическая сессия», «strategy session», «давай стратегировать».
日本語の概要は準備中です。原文の説明を表示しています。
Run deep research on a single competitor. Produces a dossier with executive summary, position + messaging, status-quo alternatives, key differentiators, pricing position, where-they-win / where-they-lose, threat assessment, and what to watch. Writes to marketing/competitors/MMYY-{competitor-slug}.md. Triggers - "competitor research", "competitive analysis", "research competitor X", "battlecard prep", "analyze [competitor name]
日本語の概要は準備中です。原文の説明を表示しています。
Build structured ICP documentation by scraping case studies, testimonials, and solutions pages from your website. Produces firmographics, champion + economic buyer personas, pain points, decision criteria, anti-ICP, customer proof points, and voice-of-customer synthesis. Writes to marketing/icp/ICP.md as the canonical ICP every downstream skill reads. Triggers - "icp research", "ideal customer profile", "persona research", "customer segments", "who are our customers", "build ICP"
日本語の概要は準備中です。原文の説明を表示しています。
Synthesize multiple per-competitor research files (produced by /competitor-research) into a single canonical threat matrix. Writes to marketing/competitors/aggregate.md as the locked canonical version every downstream skill reads. Triggers - "competitor aggregate", "synthesize competitors", "competitor matrix", "threat matrix", "lock competitor canonical"
日本語の概要は準備中です。原文の説明を表示しています。
Analyze sales-call transcripts to extract why deals are won and lost across six dimensions — product, messaging, GTM/sales, pricing, competition, and customer context. Produces aggregated patterns with verbatim buyer quotes, frequencies, and recommendations. Writes to marketing/win-loss/win-loss.md as the evidence base under positioning, messaging, and ICP. Triggers - "win loss analysis", "why are we losing deals", "why do we win", "analyze sales calls", "churn analysis", "deal review"
日本語の概要は準備中です。原文の説明を表示しています。
Extract voice patterns from existing content (website, blog, social, sales-call transcripts) and codify into voice rules. Produces voice analysis + voice guidelines (rules per pattern + violation pattern + fix template). Writes to marketing/brand/brand-voice.md as the canonical voice rules every content skill reads. Triggers - "tone of voice", "brand voice", "voice guidelines", "TOV audit", "writing rules", "extract voice"
日本語の概要は準備中です。原文の説明を表示しています。
Build a 10-component messaging library from your positioning + ICP + competitor aggregate. Produces positioning statement, value propositions, key differentiators, taglines, CTA variants, proof points, messaging hierarchy, status-quo alternatives. Writes to marketing/messaging/messaging.md as the canonical messaging library every downstream content / paid / outbound / lifecycle skill reads. Triggers - "product messaging", "messaging library", "value props", "messaging framework", "build messaging", "messaging components"
日本語の概要は準備中です。原文の説明を表示しています。
Extract a founder's or expert's point of view — core beliefs, contrarian takes, origin stories, taste — and synthesize a recommended "one big idea" (OBI) that anchors thought leadership and brand voice. Writes to marketing/expert-pov/expert-pov.md. Triggers - "expert pov", "founder point of view", "thought leadership angle", "one big idea", "OBI", "founder beliefs", "founder narrative"
日本語の概要は準備中です。原文の説明を表示しています。
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The heavy multi-model plan-gate panel runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
日本語の概要は準備中です。原文の説明を表示しています。
Planning specialist that breaks a VNX feature or track into small, independently-shippable PRs with dependencies and per-PR task-class routing. USE THIS when the user wants to break a feature down into PRs, sequence the work, or turn a plan into a PR queue. Delegated to by @horizon (formerly @pm — @pm still resolves via alias). Works from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generated generic example, not the source.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate panel is proportional (0-5 seats, by governance weight) and runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
日本語の概要は準備中です。原文の説明を表示しています。
Turns a feature request into a full implementation-plan requirements document matching docs/plan/_TEMPLATE.md. Use when the user asks for requirements, a spec, an implementation plan, or wants to flesh out a feature before building. Also use for /requirements or "write requirements for X".
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, modifying, or reviewing Qwik docs content or docs-site code under packages/docs, including docs routes, MDX content, generated LLM outputs, docs build behavior, or docs-specific e2e tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when modifying or reviewing Qwik Router code under packages/qwik-router, including runtime routing, buildtime route generation, middleware, adapters, SSG, markdown/MDX handling, or router tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the `@claude` CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what to leave for the actual review. Report-only — does not edit files.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions.
日本語の概要は準備中です。原文の説明を表示しています。