「dd」の検索結果

Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).

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

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

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

Measure whether a change made the tree simpler, on numbers rather than impressions — line counts, branching, coupling, interface width, rule count, standing exemptions and model-visible prose — across one diff or a whole stack of pull requests. Use before claiming a pass reduced complexity, when deciding which pull request in the stack added the machinery, and to read a function's branch count, which no v2 gate reports.

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

Draft replies to comments on your Facebook Page's posts, in your Page voice. Use when the user pastes the comments under one of their Page posts and wants on-brand replies that earn more comments and shares. Drafts 1-3 variants per comment using proven templates (answer, thank plus add value, handle the complaint, turn it into a share). Publora has no Facebook comment endpoint, so every draft returns as a copy-paste block to post yourself. Not for writing top-level posts (use fb-post-writer).

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

Set up Claude Tag for oncall for a team, from that team's standing (public) oncall / monitoring channel. Two things: it sets the channel up for monitoring, so alerts and incident posts here (from a person or another Slack bot) get triaged and acted on automatically, and it finds and sets up the connectors, plugins and skills Claude uses for oncall. A workspace can have several such channels; run once in each, by anyone, and every run adds or updates that team's section in the one oncall memory in shared workspace memory. Use on "set up oncall", "init oncall", "configure Claude for on-call". Surveys the agent connectors an admin configured for Claude, proves one with a read-only pull so access is verified, explores tools, Slack, repos and docs to learn how oncall works here, then recommends what's missing and walks the team through setup. The result goes into the indexed oncall memory every channel reuses; the other skills (incident init, investigation, handoff) pick it up automatically.

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

Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

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

Read, search, and manage Confluence Cloud pages, spaces, blog posts, comments, attachments, and labels. Use this whenever the user wants to find a page, read a doc, search the wiki with CQL, create or update a page, add a comment, list pages in a space, pull an attachment, or ask "what does the wiki say about X" — even if they don't say "API". Also use it for any *.atlassian.net/wiki URL, or a CQL string when the context is wiki content rather than tickets. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

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

Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add a comment, check a project or cycle, look up a team, or ask "what's on my plate in Linear" — even if they don't say "API" or "GraphQL". Also use it for any linear.app URL or an issue identifier like "ENG-123". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

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

Search, read, and write Notion pages, databases, and blocks. Use this whenever the user wants to find a page in Notion, read a database, add a row, create or append content to a page, or asks "what's in my Notion" — even if they don't say "API". Also use it for any URL under notion.so or a mention of a Notion page/database ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

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

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

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

Generate a topic-focused briefing in HTML from public news sources. Use when user asks for a briefing / observation / digest / 简报 / 观察 on any subject — region (Middle East, ASEAN, India), industry (semiconductors, EV supply chain, AI), policy issue (AI regulation, critical minerals, cross-border payments), institution (Fed, ECB, IMF), or theme. Output is a single self-contained HTML file with blue-color "TOPIC BRIEF" branding, optimized for both browser viewing and direct copy-paste into 微信公众号 / WeChat Official Account editor. Walks through 5 steps with one user confirmation midway. Do NOT use this skill for short summaries (<1000 字), single-piece news commentary, or already-defined report templates.

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

One file, one job, and short enough to hold in your head. Covers the size policy (hard-split over 300 lines, split 200 to 300 at a seam, aim for 150), what a natural seam is and where to cut, the exemptions, the dependency rules that decide where the split lands, and the signals that a file is already two files. Use before adding to a file that is already long, when naming a new file, when a function has nowhere obvious to live, or when a review says a file is doing too much. Triggers - "this file is too long", "where should this go", "split this file", "is this file too big", "one responsibility".

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

Write cargo tests. A test name is a sentence, the body is setup, mock, test and verify blocks separated by blank lines with no comments, and shared setup lives in a named test-support module rather than in each test. Covers naming, the block shape, where a test file goes, async and time, workspaces, and running one crate or one filter. Use when adding or changing any #[test] or #[tokio::test], or when Rust coverage has to come up. Triggers - "write a rust test", "cargo test", "test this crate", "cover this handler".

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

Multi-agent adversarial code review. Spawns three reviewer subagents (Auditor, Adversary, Pragmatist) on a single model, runs a cross-examination round, then deterministically synthesizes a single ranked report. Use this for non-trivial PRs, security-sensitive changes, refactors that touch many files, or any change where one perspective has obvious blind spots. Trigger phrases include "adverse review", "adversarial review", "multi-perspective review", "review my changes from multiple angles", "panel review". NOT suitable for trivial diffs (typos, dependency bumps, formatting).

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

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 runs one seat, a second on BLOCK, 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`.)

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

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 (one seat, a second on BLOCK) 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`.)

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

SQLite database expertise for migrations, multi-tenant patterns, transactional safety, FTS5 virtual tables, and schema evolution. Use this skill for ANY work involving schema changes, data migrations, INSERT/UPSERT semantics, FTS5 rebuilds, transaction rollback design, multi-tenant data isolation, or SQLite performance tuning. Triggers include: writing migration SQL, modifying `_import_table`-style importers, designing UNIQUE/PK constraints, adding indexes for JOINs, debugging "rows missing" / "wrong count" / "stuck for hours" symptoms in SQLite-backed systems.

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

Scout a topic on YouTube. Searches YouTube Data API v3 for the most relevant videos, ranks them by views (or engagement, likes, recency, momentum, breakout), and writes a research workbook in the OWT-Social-Ads layout with Videos, Channels, and Summary sheets, plus optional Comments and Transcripts (hooks, replay hotspots) sheets. Can also append into an existing sheet. Use when the user says "scout <topic>", wants a spreadsheet of top YouTube videos on a topic, wants creator or hook research, or wants YouTube rows added to their social ads sheet.

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

Evaluate an open source project's AGENTS.md and produce a corpus entry for the /agents-md directory. Use when adding a project to the directory, refreshing an existing entry, or running a batch of candidate repositories.

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

Use when adding a new model or pipeline to diffusers, setting up file structure for a new model, converting a pipeline to modular format, or converting weights for a new version of an already-supported model.

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

Build and review Remix 3 applications using the `remix` npm package and subpath imports. Use when working on Remix app structure, routes, controllers, middleware, validation, data access, auth, sessions, file uploads, server setup, UI components, hydration, navigation, or tests.

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

How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.

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

Write unit and E2E tests for Grafana visualization panels and viz utilities to the conventions this repo expects. Use when adding, backfilling, or reviewing tests for panels (barchart, timeseries, table, xychart, heatmap, canvas, etc.), grafana-ui viz components (Table, uPlot, VizLegend, VizTooltip), or grafana-data viz utils; when a panel test only asserts "it rendered" or "it's defined"; when reviewing AI-generated panel tests for slop; or when a canvas/rendering test is flaky.

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

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.

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