3,921 件 ・ 関連度順
概要と使いどころ
Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No. 4 of 2013. Covers conditions for lawful processing, data subject rights, cross-border transfer restrictions, Information Regulator enforcement, and responsible party obligations. Keywords: POPIA, South Africa, Information Regulator, responsible party, operator, prior authorisation.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the establishment and management of joint controller arrangements under GDPR Article 26, including determination of joint controllership, allocation of responsibilities, and transparency obligations. Activate when two or more controllers jointly determine purposes and means of processing, or when evaluating shared data platforms. Keywords: joint controller, Article 26, shared responsibility, arrangement, joint determination.
日本語の概要は準備中です。原文の説明を表示しています。
Guides preparation for supervisory authority (DPA) inspections and investigations including document readiness checklists, interview preparation for key personnel, technical demonstration procedures, on-site logistics, response protocols, and post-inspection follow-up. Covers unannounced inspections, formal audits, and complaint-triggered investigations. Keywords: DPA inspection, supervisory authority, investigation, readiness, interview preparation, response protocol.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art. 28, international transfer assessment, encryption requirements, and shared responsibility model evaluation. Activate for cloud adoption, SaaS procurement, or data centre migration projects. Keywords: cloud migration, DPIA, Art. 28, processor, encryption, shared responsibility, SaaS, IaaS, PaaS.
日本語の概要は準備中です。原文の説明を表示しています。
Plans an architecture-driven change to code that already exists: module boundaries, type responsibilities, layering, coupling, and the public surface a revision moves. Produces a buildable change plan that names the types, modules, and methods involved and records the surface delta each change makes. Use when the user wants to plan, scope, or sequence a restructure, extraction, split, consolidation, responsibility shift, or API revision of existing code, including "these responsibilities are wrong, plan the fix". Does not assess an area and stop at findings — use architectural-analysis. Does not specify new behavior — use plan-a-feature. Does not diagnose a bug — use investigate. Does not write the code — use refactor to restructure it or tdd to build it.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Cloudflare Workers Error 1101 "Worker threw exception" caused by Hono sub-app route handlers returning undefined instead of a Response. Use when: (1) Error 1101 on a specific hostname but not others sharing the same worker, (2) "the Promise did not resolve to 'Response'" in wrangler dev logs, (3) Hono sub-app route handler uses bare `return` to skip handling for non-matching hostnames or conditions. The fix is to add `next` parameter and call `return next()` instead of bare `return` in route handlers that conditionally skip.
日本語の概要は準備中です。原文の説明を表示しています。
Fix misleading HTTP response header values when debugging with curl -I or curl -sI. Use when: (1) Response headers differ between curl testing and actual browser/client behavior, (2) Cache-Control or other headers show unexpected values despite correct middleware code, (3) Server-side middleware that only applies to GET requests appears to not work when testing with curl -I. The -I flag sends HEAD requests, and middleware that checks for GET method will skip processing, returning handler-level headers instead of middleware-overridden ones.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub PR のコードレビューコメントに対応する。未 resolve のみを抽出 → 対応方針をユーザー承認 → 1 件ずつ修正＋返信 → AI レビュー由来の指摘はナレッジに反映するワークフロー。「/review-response [PR番号]」「レビュー対応」「レビューに返信」などの依頼時に使用。
Systematic review response strategy guide for RebuttalStudio. Use when developing response strategies for reviewer comments, deciding how to classify concerns, or choosing between Accept/Defend/Clarify/Experiment approaches at any stage of the rebuttal pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Provider-independent production workflow for AI avatar spokesperson videos, including presenter briefs, consent and likeness rights, disclosure and platform labeling, casting, localization, performance direction, brand fit, claims review, lip-sync/audio QA, accessibility, approvals, and delivery packages. Use when creating synthetic presenter videos, corporate explainers, training modules, sales/support avatars, localization spokespeople, product announcements, compliance videos, or social avatar clips.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, querying, or troubleshooting the Financial Services Cloud data model — including managed-package (FinServ__ namespace) and Core FSC (standard objects, no namespace) object structures, household relationship modeling, financial account ownership, and the FSC rollup framework. Trigger keywords: FSC data model, FinancialAccount, FinancialHolding, FinancialAccountRole, FinancialAccountParty, FinServ namespace, household rollup, AssetsAndLiabilities, FinancialGoal, LifeEvent, AccountContactRelation FSC. NOT for setting up financial accounts and roles in Setup — use admin/financial-account-setup. NOT for household membership and rollup scheduling — use admin/household-model-configuration.
日本語の概要は準備中です。原文の説明を表示しています。
The art and science of creating AI-powered digital presenters, avatars, and synthetic spokespersons. This skill covers HeyGen, Synthesia, D-ID, Tavus, and the emerging landscape of photorealistic AI humans that can speak any script in any language. Digital humans aren't replacing human presenters—they're enabling scale that humans can't achieve. A product demo in 50 languages. Personalized video messages for thousands of customers. 24/7 customer support with a friendly face. Training videos that can be updated without reshoots. The practitioners of this skill understand both the power and the responsibility. They know when digital humans enhance experiences and when they feel uncanny. They navigate the ethics of synthetic media thoughtfully. They create AI presenters that feel helpful, not deceptive. Use when "digital human, AI avatar, AI presenter, HeyGen, Synthesia, D-ID, Tavus, synthetic, talking head AI, AI spokesperson, personalized video, video at scale, multilingual video, AI actor, digital-humans, avatar, ai-presenter, synthesia, heygen, d-id, synthetic-media, personalization, multilingual" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
The specialized craft of writing copy that sells—headlines that stop thumbs, body copy that persuades, CTAs that convert. This is copywriting specifically tuned for advertising: paid media, performance marketing, direct response. Ad copy is different from content writing. Every word costs money (CPM/CPC). Every character competes for attention. There's no time for warm-up—you have one chance to hook, persuade, and convert. The best ad copy feels effortless but is engineered word by word. In the age of AI-generated creative at scale, ad copywriting becomes both more important (you need more variations) and more challenging (everyone has access to the same tools). The differentiation is in the strategy, the insight, and the craft that AI assists but doesn't replace. Use when "ad copy, headline, ad text, CTA, call to action, Facebook ad, Google ad, ad variations, direct response, performance copy, primary text, ad headline, ad-copy, headlines, direct-response, performance, conversion, cta, advertising" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
ADVOGADO CRIMINALISTA SENIOR — ESPECIALISTA EM DIREITO PENAL E MARIA DA PENHA workflow skill. Use this skill when the user needs Advogado criminalista especializado em Maria da Penha, violencia domestica, feminicidio, direito penal brasileiro, medidas protetivas, inquerito policial e acao penal and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Draws an activity flow / system architecture diagram as ONE self-contained, INTERACTIVE HTML+SVG page (2-pane app layout — left: diagram, default fit-to-view with zoom/pan; right: sidebar with explainer cards), styled like a real hand-drawn enterprise doc (Stripe/AWS-docs style — real brand logos for MongoDB/Odoo/n8n/etc. from a bundled Simple Icons library, neutral white boxes, sans-serif, no "AI neon" look), scroll-to-zoom, auto light/dark with a toggle button — clicking a flow (a legend chip, a line, or a step badge) highlights that flow with traveling dots along the arrows in their direction, a ping at the destination box, and a sidebar panel that slides out, while everything else dims; two-way arrows (OUT = solid blue / RETURN = dashed green) carry numbered step badges, colored by semantic meaning (red = auth checkpoint, purple = scheduled flow, amber = data pipeline), a small "hop" arc where two lines are forced to cross, dashed group regions, one explainer card per flow in the right sidebar. Use this skill ANY TIME the user wants to "draw a diagram", "draw a flow", "draw a system diagram", "redraw this so it's easier to follow", "interactive diagram", "two-way diagram", "request/response flow", "make a free-form HTML diagram" — even if they never say the word HTML. Especially good when both the request direction AND the response direction need to be shown, or when a templated tool (archify, mermaid) is too rigid. Do NOT use for data charts (bar/line/pie), and do not use when the user asks specifically for archify or mermaid.
日本語の概要は準備中です。原文の説明を表示しています。
Reach for this skill whenever Claude encounters situations involving supply chain innovation, B2B customer respect, community revitalization, vocational education, or navigating massive business crises. Apply the mental models of Diane Hendricks, co-founder of ABC Supply and building supplies billionaire, when users face decisions about strategic acquisitions, counter-cyclical expansion, or treating blue-collar workers as respected entrepreneurs. Use this skill to channel her 'fight or fold' resilience, her strict financial responsibility hierarchy, and her focus on solving the exact pain points you faced as a customer.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect Android network captures and intercept HTTP calls with the Snap-O CLI for a selected device/socket. Use for request/response details, websocket events, API response overrides, mock responses, or delays with Python route handlers.
日本語の概要は準備中です。原文の説明を表示しています。
Design multi-device layouts with Container Queries, clamp() fluid typography, :has() selector, subgrid, and modern CSS units (dvh/svh/lvh). Use when user asks to make a layout responsive, handle mobile/tablet/desktop breakpoints, create fluid typography, or use Container Queries. Do NOT use for full-page layouts (use landing-craft), component design (use component-forge), or animation-specific responsive (use motion-craft).
日本語の概要は準備中です。原文の説明を表示しています。
Produces structured summaries of insurance claims correspondence including coverage letters, reservation of rights (ROR), denial letters, and claim file documents. Extracts policy details, coverage positions, claims chronology, settlement posture, and liability exposure. Use when summarizing claim files, coverage disputes, ROR letters, denial letters, or multi-document insurance correspondence threads.
日本語の概要は準備中です。原文の説明を表示しています。
Classical control and system dynamics for engineered systems — feedback and closed-loop control, transfer functions and block diagrams, poles/zeros and stability, time-domain response (rise time, overshoot, settling time), PID controllers and tuning, and frequency response (Bode plots, gain and phase margin). Traces feedback control from the flyball governor to modern controllers. Use when analyzing feedback loops, designing or tuning a PID controller, assessing stability from poles or margins, or characterizing transient response of a dynamic system.
日本語の概要は準備中です。原文の説明を表示しています。
Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.
日本語の概要は準備中です。原文の説明を表示しています。
Triage SDR replies and turn inbound responses into safe next actions, CRM handoff notes, suppression updates, objection responses, referrals, and meeting prep triggers. Use when "SDR reply", "triage replies", "outbound replies", "interested reply", "objection reply", "not interested", "unsubscribe", "wrong person", "bounce", "sales follow-up", "booked meeting", or any request to classify and respond to sales development replies.
日本語の概要は準備中です。原文の説明を表示しています。