「communication」の検索結果

Applies an ASD-STE100-derived register to operator and procedural text. Use when writing runbooks or steps. Do not use for docstrings, ADRs, or rationale.

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

Compresses verbose responses by removing filler and framing to save 200-400 tokens. Use when responses feel bloated or context is filling fast.

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

Casual but professional tone for team communication. Uses company-specific terminology with scannable format.

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

Create brand-safe content for athletes. Personal branding strategy, engagement optimization, crisis communication, sponsor integration.

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

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

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

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

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

Executive communication style for all-hands emails. Balances transparency with appropriate messaging.

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

从传播心理和受众感受检查成稿是否真正有共鸣，定位受众不明确、主张过多、立场漂移和分享动机不足等问题。用户担心内容不打动人、没流量，或发布前想检查共鸣结构时使用。 English: Review a finished draft for audience resonance and communication psychology, identifying vague audiences, too many claims, shifting positions, and weak sharing motives. Use when content may not connect, may underperform, or needs a pre-publish resonance check.

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

把账号链接、主页截图、产品说明和历史内容整理成可复用的账号档案，明确调性、人设、受众、产品连接和表达边界。用户要求分析账号定位、建立账号资料，或开始完整内容生产流程时使用。 English: Build and maintain a reusable account profile from account links, screenshots, product details, and past content. Use for account positioning, voice, audience, product fit, communication boundaries, or before a full SDT production workflow.

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

Architecture guide for GDPR-compliant federated learning systems. Covers horizontal and vertical FL, aggregation strategies (FedAvg, FedProx), communication efficiency, secure aggregation, and differential privacy integration. Includes privacy guarantees analysis and deployment patterns for cross-organizational ML without data sharing.

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

Designs and executes tabletop breach simulation exercises for testing organizational breach response capabilities. Covers scenario creation with realistic inject timelines, participant role assignment, communication testing across internal and external channels, decision-point evaluation, and after-action report generation. Keywords: tabletop exercise, breach simulation, incident response testing, scenario design, after-action report.

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

Implements federated learning architecture patterns for GDPR compliance. Covers secure aggregation protocols, differential privacy integration, communication protocols, and privacy-by-design distributed ML training. Keywords: federated learning, distributed training, secure aggregation, differential privacy, privacy-preserving ML.

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

Coordinates credit monitoring and identity theft protection services for individuals affected by a data breach. Covers vendor selection criteria, enrollment logistics, coverage duration (12-24 months), identity theft insurance options, communication to affected individuals, and enrollment rate tracking. Keywords: credit monitoring, identity protection, breach response, Experian, enrollment, identity theft insurance.

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

Remove signs of AI-generated writing from prose, and keep it out of a repo. Use when drafting, editing, or reviewing text to make it sound natural and human, or when auditing a whole docs folder for AI slop. Detects 41 patterns across content, language, style, communication, filler, and rhetoric, including: significance inflation, promotional language, -ing tails, vague attributions, AI vocabulary, copula avoidance, negative parallelisms, false agency, em dash overuse, chatbot artifacts, hedging stacks, staccato drama, and aphorism formulas. Includes voice calibration, a no-fabrication rule, statistical tells, and a draft -> audit -> final rewrite loop.

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

Interact with Microsoft Teams — send and read messages, search conversations, look up people, check calendar, get meeting transcripts, and manage chats. Use this skill whenever the user mentions Teams, MS Teams, Microsoft Teams, wants to send a message, read chat history, search conversations, look up a colleague, check their calendar, find meeting recordings or transcripts, see direct reports or manager, or do anything involving Teams communication. Also trigger when the user asks about scheduling, org chart, people search, or wants to message someone.

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

Contact another agent, exchange work cards, inspect replies, or manage reachable seats through the installed Reach program. Use for communication; full task ownership transfer belongs to handoff.

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

Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.

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

McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.

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

Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping contested ownership and responsibility. The entire repository is a valid scope; no module or directory must be named first. Does not assess architectural coupling, cohesion, or technical debt — use architectural-analysis. Does not design service communication, integration patterns, or deployment topology — use architectural-analysis or plan-a-feature. Does not refactor code, diagnose bugs, or review code quality — use refactor, investigate, or code-review.

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

Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use when responding to customer tickets, escalations, outage notifications, bug reports, feature requests, or any customer-facing communication.

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

Comprehensive product launch planning including GTM strategy, launch checklists, stakeholder communication, beta testing plans, and post-launch analysis. Execute successful product launches with coordinated teams.

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

Implements real-time WebSocket communication with connection management, room-based messaging, and horizontal scaling. Use when building chat systems, live notifications, collaborative tools, or real-time dashboards.

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

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

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

Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.

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