「platform」の検索結果

Expert guidance for the cross-platform Tabular Editor CLI (the `te` binary, currently in preview) that manages Power BI / Analysis Services semantic models from the terminal on macOS, Linux, and Windows. Use when the user mentions the `te` CLI or "Tabular Editor CLI" (not the "2"), or runs a `te <command>` to scaffold, inspect, edit, validate, run BPA on, query, deploy, refresh, test, or migrate a semantic model. Not for the legacy Windows-only `TabularEditor.exe` (TE2).

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

Guidance for Power BI Project (PBIP) structure, thick and thin reports, project renames, forks, and validation. Use for .pbip, .pbism, .platform, definition.pbir, PBIP vs PBIX, or cross-cutting project operations.

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

When the user wants to optimize for AI search visibility (ChatGPT, Claude, Perplexity, AI Overviews). Also use when the user mentions "GEO," "AEO," "generative engine optimization," "AI search visibility," "LLM optimization," "GitHub GEO," "Grokipedia," "optimize for ChatGPT," "AI Overviews," "Bing Copilot," "Yandex AI," "Perplexity optimization," "GEO strategy," or "AI search optimization." For third-party publishing strategy (which platforms to use), use parasite-seo. For GitHub repos, README, and Awesome lists, use github. For Medium.com only, use medium-posts. For Grokipedia edits, use grokipedia-recommendations. For traditional Google SERP strategy, use seo-strategy.

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

When the user wants to run native ads on Taboola, Outbrain, or similar platforms. Also use when the user mentions "native ads," "Taboola," "Outbrain," "content recommendation," "sponsored content," or "in-feed ads." For strategy, use paid-ads-strategy.

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

When the user wants to create X (Twitter) post copy, threads, or optimize for X platform. Also use when the user mentions "X post," "X thread," "Twitter post," "Twitter thread," "tweet," "tweet copy," "thread," "X marketing," "X content," "post to X," "create X post," or "X post copy." For long-form source, use article-content.

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

When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.

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

When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.

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

When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.

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

When the user wants to write, publish, republish, or optimize posts on Medium.com (canonical tags, distribution, Medium SEO). Also use when the user mentions "Medium," "Medium article," "Medium story," "Medium publishing," "canonical Medium," or "publish on Medium." Not for general parasite SEO when Medium is not the target platform—use parasite-seo. For AI search visibility strategy, use generative-engine-optimization.

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

When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For multi-platform parasite SEO strategy, use parasite-seo. For broad AI search visibility, use generative-engine-optimization.

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

Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the pcf plugin to the GitHub repository.

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

Builds, tests, diagnoses, upgrades, deploys and verifies Power Apps component framework (PCF) code components for model-driven apps and Power Pages — field and dataset controls, standard and virtual (React) — from Microsoft-maintained templates and recipes pinned to a tested version matrix. Runs quality gates (manifest and host lint, source checks, lint, unit tests, production build), deploys with pac pcf push, verifies registration and form bindings, and guides Power Pages enablement, with guided setup for canvas apps. Use when the user wants to build, fix, upgrade, deploy or check a PCF control or code component, or asks why one fails to build, import, update or render. For a whole page use /model-apps:genpage; for a whole app use /model-apps:app-builder.

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

Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of pcf telemetry or its usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".

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

Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.

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

Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.

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

Use when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.

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

Use when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.

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

Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.

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

Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.

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

Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.

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

Use when a Process Mining overview, initial process selection, or an analytical follow-up needs routing.

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

Use when analyzing interacting object types, object-centric processes, leading-object executions or cross-object delay.

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

Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.

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

Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.

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