「geo」の検索結果

Use when authoring, reviewing, or maintaining Salesforce DevOps operational documents — runbooks, environment matrices, deployment guides, and post-deploy validation checklists. Triggers: 'runbook', 'environment matrix', 'deployment guide', 'pre-deploy checklist', 'post-deploy validation', 'how do I document a deployment', 'rollback procedure template'. NOT for what actually belongs on the pre-deploy gate — use devops/pre-deployment-checklist. NOT for release calendar, versioning, or go/no-go governance — use devops/release-management. Also covers: the devops-process YAML artefact (environment ladder, change-request state machine, deploy contract, deploy order, RACI), the deployOptions the runbook must record (checkOnly, testLevel, rollbackOnError, ignoreWarnings, purgeOnDelete, singlePackage, runTests), destructiveChangesPre/Post ordering, and the change-request emergency path.

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

Ocean science expert covering physical, chemical, biological, and geological oceanography

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

Crystal and gemstone expert covering traditional associations, chakra systems, and metaphysical properties alongside geological facts

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

Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

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

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

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

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

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

Build data-driven compensation structures that attract talent without overpaying. Covers base salary bands, equity/bonus frameworks, geographic differentials, and total rewards packaging.

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

Ask Claude, ChatGPT, and Gemini a question and capture the full trace behind the answer (the search queries each engine ran, the pages it retrieved, and the sources it cited, span by span). Use when asked to "trace an AI answer", "see what AI engines cite", "check AI citations", "which sources does ChatGPT/Claude/Gemini use", "why does the AI recommend X", or for any GEO (Generative Engine Optimization) measurement.

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

Map the most influential Reddit venues for a brand's AI visibility using Xpoz. Finds which subreddits and threads AI engines actually cite when answering buyer questions, where those questions get asked, and which live threads are worth answering. Use when asked to "get cited by AI through Reddit", "which subreddits matter for my brand", "Reddit influence map", "where should we engage on Reddit", or "why does ChatGPT cite Reddit for my category".

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

Use when facing SEO algorithm questions, content strategy decisions, Threads growth planning, GEO optimization, AI tool selection for SEO, or evaluating SEO vendors. Triggers on any algorithm or content marketing decision — even without mentioning darkseoking. Every insight is backed by patent numbers or tested data.

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

风水堪舆 · 阳宅/阴宅选址与布局建议。用户提供**地点**（最好是准确经纬度）、**周边环境描述或图片**、 以及**阳宅或阴宅**（可选朝向/坐向、建造或入住年、居者生辰性别、所求何事）→ 先用脚本**确定性**地 定位经纬度、查周边山水路(砂水)与地势、定坐向二十四山、排三元九运玄空飞星、八宅游年 → 再参《葬书》 《青囊经》《撼龙经》《雪心赋》等古籍，以**形势派(峦头)·理气派(玄空/八宅)·现代建筑学**三层解读 → 最后给出「藏风聚气·背山面水·明堂开阔·阴阳平衡·五行调和」的交叉对照表与**可执行、非破坏性**的改善建议。 Use this skill whenever the user asks about 风水、堪舆、看风水、阳宅、阴宅、选址、坐向、朝向、 住宅/办公室/店铺/墓地风水、玄空飞星、八宅、命卦、龙脉、砂水、四神砂、藏风聚气、明堂、财位、 文昌位、穿堂煞、户型点评、装修布局、买房看风水. Triggers: "看风水", "风水建议", "这房子风水", "阳宅", "阴宅", "选址", "坐向", "朝向", "玄空飞星", "八宅", "财位", "办公室风水", "墓地风水", "feng shui", "geomancy", "house feng shui", "office feng shui", "site selection". 即使用户只是随口问「帮我看看这房子风水好不好」「大门朝这边行不行」，也应主动使用本技能。

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

占事吉凶 · 测吉凶：针对**某一件具体事、某一天、某一刻**的吉凶研判与择吉建议。 运用「黄历择日 + 四柱命理本命喜忌 + 阴阳五行天时地利 + 天人感应/梅花心易」四层独立推演， 再交叉汇聚成【吉 / 平·宜谨慎 / 凶·宜改期】的整体倾向与可执行建议。 当用户问：测吉凶、占吉凶、这事能不能做、今天适不适合出门/旅行/搬家/开业/签约/求医、 出行吉凶、看日子、择日、挑个好日子、黄历、老黄历、今天宜不宜、宜忌、冲煞、起一卦、 算算这件事顺不顺、"临出发前忽然心悸/心慌，是不是预兆"、"我有种不好的预感" 时使用。 English triggers: "is today auspicious", "is it a good day to travel/move/sign", "should I go today", "pick an auspicious day", "Chinese almanac / huangli", "divination for a decision", "I have a bad feeling about going out today". 内置离线脚本：公历→农历+完整四柱+十神（bazi.py）、黄历宜忌/建除/值神/廿八宿/彭祖百忌/ 冲煞/吉神凶煞/逐时辰吉凶+梅花时间起卦（almanac.py）、经纬度定位+当天当地天气（geoweather.py）。 边界：要**批一生八字/大运流年**请用 `bazi` 技能；要**解梦**请用 `zhougong-dream-interpretation`。 即使用户只是随口问「今天出门好不好」「这事顺不顺」，也应主动使用本技能。

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

Research historical news events that moved (or are moving) an asset's price and plot them as data points directly on the chart. Click a marker in the Historic News tab to zoom the chart to that event and read the article. Useful for identifying the fundamental drivers behind price action — earnings, regulation, product launches, macro shocks, geopolitical events.

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

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

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

Diagnose agent operational failures through default-policy checks, multi-gap analysis, explicit service ownership, request-context lifetime, and degradation-versus-correctness checks.

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

Mandatory 3-phase explore-reason-act workflow before code modification. Enforces read-before-write, root cause hypothesis formulation, minimal change application. Triggered by "explore" ("탐색"), "reason" ("추론"), "read before write", "root cause" ("근본 원인") keywords.

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

Automated Git PR review — diff analysis + quality checks.

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

Auto-search and summarize latest AI/agent papers.

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

Docs 사이트 (`site/` Next.js) 의 본문/JSX/markdown 링크 audit. broken 내부 링크 탐지, build-time copy 인지, 옵트인 HTTP probe. 신규 페이지 추가 / slug 이전 / chapter 삭제 후 회귀 방지. Triggered by "broken link", "404", "docs link", "hyperlink", "링크 점검", "링크 깨짐", "audit links", "link checker" 키워드.

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

Audit agent runtimes and their tests for lifecycle inference, capability overload, context pollution, correlated verification, prompt-only control, false success, dead compatibility paths, test-only seams, and complexity without contribution. Use for whole-repository agent audits, slop or dead-code triage, test contribution reviews, large refactors, tool/context simplification, and cleanup requests that need proof before deleting code or tests.

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

A radically minimal, blank-canvas interface built as a pure edge-to-edge surface, with almost no color and typography carrying the visual weight. Black serves as the only filled color, the only divider, and the sole surface tone cards.

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

Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".

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

Verification checklist to prevent fake success. Detects test deletion/disabling, coverage regression, lint bypass, secret exposure. Triggered by "deception", "fake" ("가짜"), "fake success", "verification" ("검증"), "checklist" ("체크리스트"), "deletion detection" ("삭제 탐지"), "regression" keywords.

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

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.

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