「connect」の検索結果

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

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

Use this skill when designing, generating an MVP blueprint for, auditing, troubleshooting, refactoring, or explaining an agentic harness for any domain. Covers provider-neutral agent architecture for OpenAI, Anthropic, and OpenAI-compatible APIs: agent loops, tool design, record provenance, interactive presentation, user-memory lifecycles, environment-adaptive tools, speculative tool execution, late-bound capabilities, permissions, system prompts, planning, goals, always-on agents and durable runtime, adaptive agent teams, context compaction, memory, skills, MCP/external connectors, public-board communications, realtime voice agents, hardware agents and board deployment, self-refining recursive harnesses, programmable context, continual refinement, observability, evals, prompt caching, agent-legible environments, feedback loops, and safety.

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

When the user wants to design, deploy, or measure Apple Custom Product Pages (CPP) — the alternate App Store product pages with different screenshots, preview videos, and promo text shown to users coming from specific URLs (typically ad campaigns or social posts). Use when the user mentions "Custom Product Page", "CPP", "alternate product page", "App Store URL variant", "ASA CPP", "campaign-specific landing page", "product page per audience", "App Store Connect CPP", "ppoUrl", "?cpp=" parameter, or "show different screenshots to different ad audiences". For App Store A/B tests on the default page, see ab-test-store-listing. For paid ad campaigns that route to CPPs, see apple-search-ads or ua-campaign.

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

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

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

On-demand provisioning guide for a Memmy GUI task that fully connects an explicitly named local Agent: discover its active history store, install or remove its rendered Memmy Skill, bootstrap a scan boundary, persist a validated automatic-sync recipe, and verify GUI-visible readiness.

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

Two stages: first a single-page sheet of numbered panels from an image model, then that sheet fed to Seedance as the reference. The sheet owns order, framing and timing, and the video prompt only has to connect the panels. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Storyboard grid to video; 中文触发词: 分镜网格转视频, 分镜图, 九宫格, 故事板), or asks how published cases of this type were prompted. Read references/cases.md before drafting.

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

Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.

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

Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.

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

Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.

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

Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.

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

Install, configure, and add MCP servers to the OpenAkita system. Use when the user needs to install MCP packages (npm/pip/uvx), connect remote HTTP/SSE MCP services, set up custom local MCP servers, or manage MCP server configuration and lifecycle.

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

Structures and writes discussion sections for academic papers and research reports. Use when writing a discussion section, interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions, or drafting any part of...

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

Designs QTL colocalization studies that connect eQTL, pQTL, sQTL, or related molecular QTL signals with GWAS loci. Always use this skill whenever a user wants to plan, scope, or structure a locus-level study asking whether a GWAS association and a molecular QTL association may reflect the same underlying causal signal. Covers locus definition, QTL/GWAS source architecture, ancestry and LD alignment, single-locus vs multi-locus strategy, candidate-gene prioritization, optional fine-mapping, linked MR/SMR follow-up, and functional annotation. Always output four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, stepwise workflow, method rationale, evidence hierarchy, figure plan, minimal executable version, and strictly verified literature guidance with no fabricated references. Never equate colocalization with causality proof, mediation proof, or automatic target validation. Always include the mandatory Dataset Disclaimer immediately before any workflow section that mentions datasets, repositories, consortia, or public resources.

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

Gregor Mendel — genetics mentor, patient experimenter, and gardener-monk. Trigger this skill when users ask about genetics, heredity, inheritance patterns, Mendelian laws, dominant/recessive traits, gene segregation, independent assortment, Punnett squares, classical genetics, or evolution-genetics connections. Also trigger when discussing the philosophy of science, how great ideas get ignored, the relationship between faith and science, or the virtue of patient long-term observation. Even if the user doesn't say "Mendel" explicitly, trigger this skill for questions touching genetics, breeding, trait inheritance, or genomics history. Part of the AIPOCH Science Mentor Skill Hub.

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

Finds translational opportunities that connect basic-research discoveries to clinically meaningful use cases such as diagnosis, stratification, prognosis, treatment response prediction, monitoring, or therapeutic development. Use this skill when a user wants to turn a mechanism finding, pathway signal, cellular phenotype, experimental observation, or omics discovery into a stronger translational research direction. Always separate mechanistic relevance from translational usability, and never present a basic finding as clinically actionable unless the evidence supports that level.

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

Composes a Discussion around key findings, mechanisms, clinical relevance, and limitations. Use when writing or improving a Discussion section for any biomedical manuscript — including interpreting results, connecting to prior literature, addressing unexpected findings, framing limitations, and writing the conclusion. Also triggers on "write my discussion", "help me discuss my findings", "how do I compare to prior studies", "write the limitations paragraph", or "draft a discussion for my paper".

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

Keep Figma and code in sync — map the 3-tier DTCG tokens to Figma Variables (collections + modes), sync in either direction, use the Figma MCP when connected, and verify component parity (variants/states). Use when the user wants to push tokens/components to Figma, pull a design into code, set up token↔Variable sync, or check design-code drift.

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

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.

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

Design any process, idea, problem, or body of knowledge into an ICM (Interpretable Context Methodology) workspace — folder structure as agent architecture — or restructure an existing folder, repo, or vault into one. Use when the user wants to (1) turn a recurring workflow into an agent-runnable folder pipeline, (2) organize scattered notes, files, or knowledge into a library one AI agent can walk, (3) map a team or company as connected context ("context map", "second brain", "team brain", "knowledge base for AI"), (4) audit a codebase or mixed folder into a walkable edit map (objects, processes, change-impact) so later agents can change it without slurping the tree, (5) audit or restructure an existing workspace to ICM conventions, or (6) says "make this an ICM", "ICM this", "map this repo", "audit this folder", "what would a change hit", "build me a workspace", or "structure this for agents".

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

Emulated Microsoft Entra ID (Azure AD) OAuth 2.0 / OpenID Connect for local development and testing. Use when the user needs to test Microsoft sign-in locally, emulate Entra ID OIDC discovery, handle Microsoft token exchange, configure Azure AD OAuth clients, work with Microsoft Graph /me, or test PKCE/client credentials flows without hitting real Microsoft APIs. Triggers include "Microsoft OAuth", "Entra ID", "Azure AD", "emulate Microsoft", "mock Microsoft login", "test Microsoft sign-in", "Microsoft OIDC", "local Microsoft auth", or any task requiring a local Microsoft OAuth/OIDC provider.

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

Emulated Google OAuth 2.0, OpenID Connect, Gmail, Calendar, and Drive for local development and testing. Use when the user needs to test Google sign-in locally, emulate OIDC discovery, handle Google token exchange, configure Google OAuth clients, work with Gmail messages/drafts/threads/labels, manage Calendar events, upload or list Drive files, or work with Google userinfo without hitting real Google APIs. Triggers include "Google OAuth", "emulate Google", "mock Google login", "test Google sign-in", "OIDC emulator", "Google OIDC", "Gmail API", "Google Calendar", "Google Drive", "local Google auth", or any task requiring a local Google API.

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

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate 1–5a). DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion — route those to officecli-pptx base or officecli-pitch-deck.

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

Use this skill when the user is building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate). DO NOT invoke for a generic board review, sales deck, all-hands, or product launch — route those to officecli-pptx base.

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

Model OR-Tools paired pickup-and-delivery routing problems, including PDPTW, dial-a-ride, paratransit, patient transport, and courier jobs with same-vehicle pairing, precedence, capacity, optional connected service, rider time windows, and vehicle shifts.

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