1.7万 件 ・ 関連度順
概要と使いどころ
Manages GKE application onboarding, covering containerization, deployment manifests, and migration. Use when onboarding or deploying an application to GKE for the first time, or containerizing an app for GKE. Don't use for general GKE cluster administration or upgrades (use gke-basics or gke-upgrades instead).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to configure a Lightning Service Console app in Salesforce — Console Navigation (split view), workspace tabs and subtabs, the utility bar with Omni-Channel, Macros and History, Quick Text, keyboard shortcuts, and navigation rules per object. Trigger keywords: Service Console, console app, workspace tabs, subtabs, utility bar macros, Omni-Channel utility, split view, Quick Text, console navigation rules, keyboard shortcuts service console, navType Console, workspaceConfig mappings, WorkspaceMapping fieldName, UtilityBar FlexiPage, tabLimitConfig, listPlacement, MacroInstruction, QuickText Channel multipicklist, isNavTabPersistenceDisabled. NOT for opening or refreshing console tabs from code — use lwc/lwc-console-workspace-api. NOT for Omni-Channel routing setup — use admin/omni-channel-routing-setup.
日本語の概要は準備中です。原文の説明を表示しています。
Configuring Salesforce lead management and conversion in Setup: lead settings, web-to-lead, conversion field mapping, lead queues, auto-response rules, lead processes. Trigger keywords: web-to-lead, lead conversion, lead field mapping, lead settings, lead process, lead queue, lead auto-response. NOT for Apex that controls what conversion creates - use apex/lead-conversion-customization. NOT for lead assignment rule logic - use admin/assignment-rules. NOT for duplicate rule configuration - use admin/duplicate-management. Also covers: LeadConvertSettings objectMapping XML, LeadConfigSettings, LeadStatus StandardValueSet converted flag, lead process BusinessProcess, Database.convertLead bulk conversion limits.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building a Lightning record page in App Builder or when the page users see is not the one you assigned. Trigger keywords: configure lightning record page, lightning app builder, flexipage, record page assignment, org default vs app default, activate lightning page. NOT for page speed - use admin/lightning-page-performance-tuning. NOT for page layout to Dynamic Forms migration - use admin/dynamic-forms-migration. NOT for related list columns - use admin/related-list-configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an admin or partner needs to package an Experience Cloud (Community) site as a reusable Lightning Bolt Solution for distribution — covers the export workflow from Experience Builder, what gets bundled (ExperienceBundle, custom apps, flow categories, theme, layouts, navigation menus) versus what does NOT (data, CMS content, files), choosing Bolt vs managed package vs unlocked package vs cloning a site, sandbox-to-production promotion, multi-org distribution, AppExchange listing as a Bolt, and template versioning via the LightningBolt metadata `versionNumber`. Triggers: 'turn this community into a reusable template', 'package an Experience Cloud site to ship to multiple orgs', 'export Experience Builder template for AppExchange', 'should we use a Bolt or a managed package for this community', 'create an industry-specific community starter', 'how do we version our partner portal template', 'distribute branded Experience site across business units'. NOT for general Experience Cloud site build, content, or member setup (use admin/experience-cloud-site-setup, admin/experience-cloud-cms-content, admin/experience-cloud-member-management). NOT for shipping Apex / LWC / data-model functionality as a product (use devops/managed-package-development, devops/second-generation-managed-packages, devops/unlocked-package-development). NOT for moving a single Experience site between sandbox and prod as a one-off (use devops/experience-cloud-deployment-admin, devops/cicd-for-experience-cloud).
日本語の概要は準備中です。原文の説明を表示しています。
Use when scoring a list of business or solution requirements against the *actual* capabilities of a specific Salesforce org so each row can be classified Standard / Configuration / Low-Code / Custom / Unfit, given an effort tier (S/M/L/XL), a risk tag, and an AppExchange suggestion when applicable. Trigger keywords: fit gap salesforce requirements, score requirements against salesforce capabilities, salesforce capability matrix, classify requirement as standard config custom, fit-gap effort tier, AppExchange alternative for requirement. NOT for requirements elicitation (use admin/requirements-gathering-for-sf). NOT for architecture decisions on the GAP rows (use architect/solution-design-patterns and standards/decision-trees/). NOT for license or edition selection (use architect/license-optimization-strategy and architect/org-edition-and-feature-licensing). NOT for OmniStudio-specific fit-gap (use architect/omnistudio-vs-standard-decision).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when driving adoption of CRM Analytics (Einstein Analytics) across an org — the Analytics Adoption App for measuring who uses which dashboards, embedding analytics into Lightning pages, pinning dashboards to the Analytics home page, self-service personas, and analytics success metrics. Triggers: analytics adoption, dashboard usage tracking, embedded analytics strategy, self-service analytics enablement, CRM Analytics rollout. NOT for building the dashboards — use admin/analytics-dashboard-design. NOT for the app, datasets and lenses — use admin/crm-analytics-app-creation. NOT for non-analytics rollout training — use admin/change-management-and-training.
日本語の概要は準備中です。原文の説明を表示しています。
Detects mismatches between features claimed in App Store metadata and features actually implemented in the codebase, enforcing Guideline 2.3.1 which prohibits misleading app descriptions.
日本語の概要は準備中です。原文の説明を表示しています。
Detects review-blocking configuration issues including sub-1.0 version numbers, beta in app name, staging endpoints, and missing demo credentials that prevent reviewers from evaluating the app, violating Guidelines 2.1 and 2.3.
日本語の概要は準備中です。原文の説明を表示しています。
Detects missing, broken, or placeholder privacy policy links in-app, enforcing Guideline 5.1.1(i) which requires a functional, accessible privacy policy within the app itself.
日本語の概要は準備中です。原文の説明を表示しています。
Detects placeholder content, stub UI, hardcoded test credentials, and non-production endpoints that signal an incomplete app to reviewers under Guideline 2.1.
日本語の概要は準備中です。原文の説明を表示しています。
Detects apps that send user data to third-party AI systems without explicit in-app consent and disclosure, enforcing Guideline 5.1.2(i).
日本語の概要は準備中です。原文の説明を表示しています。
Detects missing or insufficient in-app account deletion functionality required since June 30, 2022 under Guideline 5.1.1(v) for all apps that support account creation.
日本語の概要は準備中です。原文の説明を表示しています。
Detects analytics or tracking SDKs present without the required App Tracking Transparency prompt, enforcing Guideline 5.1.2(i) which requires user consent before any cross-app or cross-site tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Detects apps built with outdated Xcode SDKs or deprecated iOS deployment targets, enforcing Guideline 2.5.10 which requires apps to be built with the current SDK from Xcode.
日本語の概要は準備中です。原文の説明を表示しています。
Detects apps that abuse iOS background execution modes — particularly silent audio used to keep the app alive, location background mode used for non-navigation purposes, and background task implementations that do excessive work — enforcing Guideline 2.5.4.
日本語の概要は準備中です。原文の説明を表示しています。
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts an itemized Bill of Costs on Appeal under FRAP 39 or state equivalent for the prevailing party to recover allowable appellate expenses. Triggers on appellate cost bill drafting, post-judgment cost recovery filings, or prevailing party cost submissions.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts an Appellee's Response Brief defending the trial court's judgment and arguing for affirmance. Covers standard of review analysis, record-based rebuttal, authority distinction, and procedural compliance. Trigger when drafting appellee briefs, response briefs, answering briefs, or defending trial court judgments on appeal.
日本語の概要は準備中です。原文の説明を表示しています。
Generates appellate-filing-ready Tables of Contents, Tables of Authorities, and Certificates of Compliance under FRAP 32(g) and related rules. Produces defensible word-count calculations with transparent exclusions and anti-hallucination guardrails for pagination and citations. Covers federal circuits, state appellate courts, and U.S. Supreme Court variations. Use when building TOC, TOA, compliance certificates, formatting briefs for filing, or when the user mentions word count calculation, FRAP 32 compliance, appellate brief assembly, or page numbering.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite CLI skill. Use when managing Appwrite projects from the command line. Covers installation, login, project initialization, multi-file project configuration, deploying functions/sites/tables/buckets/teams/webhooks/topics, flag-based list queries, non-interactive CI/CD mode, and generating type-safe SDKs.
日本語の概要は準備中です。原文の説明を表示しています。
Apply rapport-based elicitation to resistant or semi-cooperative humans and agents. Use when coercive prompting or brittle handoffs damage cooperation. NOT for routine cooperative tasks, pure technical debugging, or already reliable exchanges.
日本語の概要は準備中です。原文の説明を表示しています。
Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.
日本語の概要は準備中です。原文の説明を表示しています。
What you can build and do with an always-on AI agent that has episodic memory. Covers concrete product ideas, workflows, emergent capabilities from persistence plus memory, and real-world examples of deployed persistent agents. Helps you go from "I have the architecture" to "here's what it actually does for me." Activate on: "what can an always-on agent do", "persistent agent use cases", "agent applications", "proactive agent ideas", "what to build with episodic memory", "always-on agent product", "personal AI assistant ideas", "/always-on-agent-applications". NOT for: building the architecture (use always-on-agent-architecture), designing inputs (use always-on-agent-inputs), safety and privacy (use always-on-agent-safety).
日本語の概要は準備中です。原文の説明を表示しています。