6,837 件 ・ 関連度順
概要と使いどころ
Select the right pharmacologic agent for a child aged 12+ with obesity using the CMAJ 2025 guideline — choosing between GLP-1 receptor agonists, metformin, or orlistat with monitoring guidance. Trigger when a clinician asks which medication to use for pediatric obesity, whether to start semaglutide or metformin in a child, or how to manage obesity pharmacologically in adolescents.
日本語の概要は準備中です。原文の説明を表示しています。
Teaches AI patients about stress-dosing and emergency glucocorticoid administration; instructs to obtain emergency card/bracelet/necklace and kit with injectable high-dose GC. Triggers when counseling any patient with adrenal insufficiency (e.g., "Use when counseling patient with adrenal insufficiency...").
日本語の概要は準備中です。原文の説明を表示しています。
Guides comorbidity-stratified selection of initial and further glucose-lowering medicines for adults with type 2 diabetes using the NICE NG28 (2026) framework, covering six clinical profiles: no relevant comorbidity, heart failure, atherosclerotic cardiovascular disease, early onset, obesity, chronic kidney disease, and frailty.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow Phase 7 — Mechanical cleanup pass over the branch diff, followed by a `code-structure` review pass and a `verify` re-stamp. Shadows the global `simplify` skill at project scope; the cleanup pass is performed inline rather than via Skill self-call.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap the central system spec at `docs/system/` for a repository that has never had one. Scans the governed surface, proposes a concept map clustered by directory, and materializes elements + shards ONLY after a human confirms that map. Use when adopting the baseline on an existing project, or when the corpus needs re-deriving from scratch. Re-runnable. Requires `memory.architecture_map.enabled` and a declared `governed_surface`.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a Workflow Phase 4 technical spec from an intake (and optionally a BRD + scout + research memo). The spec defines how the system will change: design (C4 + UML + dependency graph in PlantUML), data, APIs, tests, rollout, rollback. Output lives at `docs/specs/<slug>.md`. Never self-approves — approval happens via `/approve-direction`.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates `impeccable` for every design task inside a workflow phase. Captures intent in natural language, classifies it (design / development / copy), translates design intents into a sequence of impeccable subcommand invocations, runs them in main context with state persistence at `.claude/state/design/<slug>.json`, and returns a structured report. ALWAYS invokes `impeccable` under the hood for the underlying design move; never picks aesthetic direction itself; never writes product code directly. Per CLAUDE.md Article X.2, all design tasks in workflow phases route through this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Run an org-team workflow — a flat pod of up to four peer Claude Code sessions claims lane-tagged slices of an approved spec over the baseline MCP channel and implements them concurrently, each in its own git worktree. Each peer DECIDES its own in-lane implementation choices in its own main context (Article X); only un-decidable or cross-lane forks escalate peer→lead→human (yield_fork for task-bound forks, ask_lead for free-form queries). Opt-in and OFF by default (velocity.org_mode.enabled). Graduates the retired sprint-dispatch prototype into the constitutionally-sanctioned org-team model (Article X — Multi-session coordinated workflows). Requires git.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze credential pooling operations and API reseller business models — economics, risks, detection patterns, and sustainability
日本語の概要は準備中です。原文の説明を表示しています。
Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Deep enrichment for community-sourced enterprise PROSPECTS (the 🎯 Prospective enterprise customers subsection). For each prospect, resolve their LinkedIn from their GitHub self-linked accounts FIRST (search only if none is self-linked), verify the employer matches, capture their full name, then list the company website + company size (ARR / latest funding round / employee count). Runs as a general-purpose subagent (many web searches) so the orchestrator's context stays small. Invoked by weekly-report (enterprise section) and the enterprise skill.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level evolutionary biology covering natural selection, genetic drift, molecular evolution, phylogenetics, speciation, macroevolution, and the modern synthesis.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level green chemistry knowledge. Use when working with sustainable synthesis, atom economy, solvent selection, catalysis, renewable feedstocks, waste reduction, life cycle assessment, or the 12 principles of green chemistry. Also use when the user mentions 'atom economy', 'E-factor', 'green solvent', 'catalysis', 'renewable feedstock', 'waste minimization', 'sustainable chemistry', 'life cycle assessment', 'PMI', 'solvent selection guide', or 'benign by design'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
日本語の概要は準備中です。原文の説明を表示しています。
Assess bounded Codex software development requests before choosing direct work or TaskBelay, then prepare confirmed TaskBelay Tasks in new local branches by default, current branches, or dedicated Git worktrees. It may be selected implicitly or explicitly with $taskbelay-codex:taskbelay; the selector never skips assessment. Explicit Task resume and receipt-backed confirmed bootstrap bypass duplicate assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer criar ou otimizar paywalls in-app, telas de upgrade, modais de upsell ou feature gates. Use também quando o usuário mencionar "paywall", "tela de upgrade", "modal de upgrade", "upsell", "feature gate", "converter free para paid", "conversão freemium", "tela de expiração de trial", "tela de limite atingido", "prompt de upgrade de plano" ou "preço in-app". Distinto de páginas de preço públicas (veja page-cro) — esta skill foca em momentos de upgrade in-product onde o usuário já experimentou valor.
日本語の概要は準備中です。原文の説明を表示しています。
Orientação de liderança executiva para tomada de decisões estratégicas, desenvolvimento organizacional e gerenciamento de stakeholders. Inclui analisador de estratégia, modelagem de cenários financeiros, frameworks de governança corporativa e playbooks de relações com investidores. Use ao planejar estratégia, preparar apresentações para conselho, gerenciar investidores, desenvolver cultura organizacional, tomar decisões executivas, ou quando o usuário menciona CEO, planejamento estratégico, reuniões do conselho, atualizações de investidores, liderança organizacional ou estratégia executiva.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when planning, redesigning, or reviewing Xiaohongshu carousel visuals, covers, 3:4 image posts, page-by-page visual direction, image-generation prompts, style selection, layout critique, or XHS captions. It acts as a senior visual director for 小红书图文, not a generic copywriting assistant.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.
日本語の概要は準備中です。原文の説明を表示しています。
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style). Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay, subgrid bands, 8px baseline lock, and runtime optical alignment. Triggers: "magazine spread", "grid system", "Swiss design", "editorial layout", "show the grid", "align everything to the grid".
日本語の概要は準備中です。原文の説明を表示しています。
The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, or quarterly planning.
日本語の概要は準備中です。原文の説明を表示しています。
Review+fix protocol with optional pre-core git diff review and safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "/tw-fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal. Stop only after self-review exhausts actionable changes, each full cycle reaches post-self-review rerun plus terminal diff-review closure, and two consecutive zero-edit full cycles are clean.
日本語の概要は準備中です。原文の説明を表示しています。
7 層構造プロンプトを生成・更新するとき、owner_agent 向けに Prompt Templates/Self-Evaluation を充填するときに使う。