「io」の検索結果

Tests whether two genomic interval sets overlap (colocalize) more than expected by chance using a permutation test against a structured-genome null model. Covers bedtools fisher (analytic 2x2 screen), bedtools shuffle + jaccard permutation, GAT (isochore/GC-conditioned simulation with FDR), regioneR (flexible permutation, randomizeRegions vs circularRandomizeRegions, localZScore), LOLA (universe-relative Fisher against a region database), and GREAT/rGREAT (regulatory-domain binomial + hypergeometric for ontology-from-regions). Stresses the universe/background choice, matched background, blacklist exclusion, and multiple-testing control. Use when asking whether peaks/regions are enriched at enhancers/TFBS/features, scoring region-set colocalization or region-set enrichment, comparing CNV/SV concordance, or turning an overlap count into a defensible p-value.

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

Quantifies biodiversity from species abundance/incidence tables using Hill numbers (iNEXT) with coverage-based rarefaction-extrapolation (Chao & Jost 2012), asymptotic richness via Chao1/ACE/jackknife as a lower bound, Baselga turnover/nestedness partition with the Podani alternative as sensitivity check, mandatory Hellinger transformation before ordination (Legendre & Gallagher 2001), Faith PD and SES_MPD/SES_MNTD with explicit null-model choice, and Maire 2015 functional-diversity dimensionality optimization. Use when comparing diversity across sites with unequal sampling effort, picking the right richness estimator for singleton-heavy amplicon data, partitioning beta diversity into turnover vs nestedness, reporting Hill-number effective species counts rather than raw entropies, computing SES_MPD with explicit null-model justification, or deciding whether to apply standard metrics to compositional amplicon data. Not for clinical 16S microbiome diversity (see microbiome/diversity-analysis).

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

Resolve the architecture of focal oncogene amplifications — extrachromosomal DNA (ecDNA), breakage-fusion-bridge (BFB) cycles, homogeneously staining regions (HSR), and linear amplification — from whole-genome sequencing with AmpliconArchitect, the AmpliconSuite pipeline, and AmpliconClassifier. Covers copy-number seed selection, breakpoint-graph reconstruction, balanced-flow optimization, ecDNA classification, and the limits of depth-only amplification calls. Use when a focal amplification needs structural characterization, when distinguishing ecDNA from chromosomal amplification, suspecting ecDNA-driven oncogene amplification or therapy resistance, or selecting copy-number seeds for amplicon reconstruction.

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

Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my real database", "seed state per scenario", "it passed but booked the wrong thing", "grade the final state", or wants to stress-test a flow before shipping. Covers generating a baseline with the LiveKit scenario generator and refining it, writing the cases generation misses, phrasing simulated-user instructions so they steer reliably, splitting scenarios into sets across files, and the agent-side code that seeds deterministic state from a scenario and fails a run on its final state. To run them use running-livekit-simulations.

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

Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and interruptions", or wants to check whole-conversation behavior before shipping. Covers text and audio mode and what each catches, running against a local or deployed agent, degraded-audio flags, automating a pre-release run, and triaging failures with list, view and export. For writing the scenarios use writing-livekit-scenarios. Not the default for a bare "test my agent", which goes to debugging-livekit-agents. Use this skill when the user names simulations, scenarios, a run, CI, or shipping.

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

Expert knowledge for Azure IoT Hub development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring IoT Hub/DPS routing, device twins, MQTT/AMQP clients, Device Update, or Cosmos DB event storage, and other Azure IoT Hub related development tasks. Not for Azure IoT (use azure-iot), Azure IoT Central (use azure-iot-central), Azure IoT Edge (use azure-iot-edge), Azure IoT Operations (use azure-iot-operations).

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

Expert knowledge for Azure IoT Operations development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring MQTT/OPC UA data flows, WASM/ONNX processing, Dapr/Fabric RT endpoints, or Arc Kubernetes deployments, and other Azure IoT Operations related development tasks. Not for Azure IoT (use azure-iot), Azure IoT Hub (use azure-iot-hub), Azure IoT Edge (use azure-iot-edge), Azure IoT Central (use azure-iot-central).

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

End-to-end motion-design / animated-ad creation flow on Higgsfield via the MCP connector. Use when the user wants to create motion design, animate a logo, make a video from an image, build an animated ad or brand promo, turn a product into motion, or says 'make a motion', 'motion design', 'animate this', 'make a video from my logo', 'animated brand', 'motion graphics', 'brand motion', 'kinetic graphics', 'promo video', or 'ad video'. Drives a storyboard-first pipeline: brief → storyboard sheet (GPT Image 2) → video (Seedance 2.0) — an AI-generated pixel video clip. Distinct from higgsfield-motion (the named camera/motion preset library) and from higgsfield-vibe-motion (deterministic Remotion code with crisp text); use vibe-motion instead when the text/logo must stay perfectly crisp, editable, and deployable as code.

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

Use when reviewing, designing, or modifying Java enterprise systems that may support EU Market Abuse Regulation concerns, market surveillance, suspicious order and transaction reports, insider dealing controls, unlawful disclosure controls, market manipulation detection, inside information disclosure workflows, insider-list evidence, PDMR transaction notifications, alert explainability, model or rule provenance, reviewer decisions, or compliance escalation. This should trigger for requests such as Review a Java trading surveillance system for MAR controls; Design suspicious order and transaction monitoring evidence; Add alert explainability and reviewer-decision audit trails; Assess AI-assisted market-abuse detection before production release. Part of Plinth Toolkit

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

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.

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

Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring. Provides a breach classification taxonomy across confidentiality, integrity, and availability dimensions. Covers detection tool selection, alert tuning, and integration with privacy incident response workflows. Keywords: breach detection, SIEM, DLP, anomaly detection, insider threat, classification.

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

Compare behavior across multiple versions of programs or repositories. Use when you need to analyze how functionality changes between versions, identify regressions, compare outputs and exceptions, or validate upgrades. The skill compares execution behavior, test results, outputs, exceptions, and observable states across versions, generating detailed reports showing behavioral divergences, potential regressions, added/removed functionality, and areas requiring validation. Supports multiple programming languages and can work with test suites or execution traces.

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

Explain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories, acceptance criteria), test specifications (assertions, property-based tests), and providing step-by-step traces showing state changes, comparing expected vs actual behavior, identifying root causes, and assessing violation impact. Use when debugging test failures, understanding model checker output, explaining runtime assertion violations, analyzing static analysis warnings, or teaching specification concepts. Produces structured markdown explanations with traces, comparisons, state diagrams, and cause chains. Triggers when users ask why something failed, explain a violation, understand a counterexample, debug a specification, or analyze why a test fails.

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

中医诊疗 — 中医临床医师的认知操作系统 (经典理论 阴阳五行脏腑气血经络六经卫气营血三焦 + 四诊八纲 + 治法 + 方剂学 经方时方 + 中药学 四气五味归经炮制 + 针灸学 经络穴位手法灸法 + 推拿按摩 + 中医各科 内外妇儿骨伤皮肤眼耳鼻喉肛肠老年急症 + 中西医结合 + 循证中医 + NATCM 监管 + 中医诊所备案 + 国家级名老中医 学术继承人 — 不含 道家修炼 / 风水算命 / 中医养生科普 / 中医美容 / 民族医学藏蒙维傣) (Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注).) Master OS — automated mastery of Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「中医」「中医学」「中医药」「中医诊疗」「中医临床」

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

Odoo 19 development knowledge base with 18 specialized guides covering Actions (ir.actions.*, cron jobs, server actions), Controllers (HTTP routing, endpoints, auth types), Data files (XML/CSV records, shortcuts, noupdate), API Decorators (@api.depends, @api.constrains, @api.ondelete, @api.onchange, @api.model, @api.private), SQL Constraints (models.Constraint replacing _sql_constraints), Database Indexes (models.Index), Module development (manifest, wizards, reports), Field types (Char, Text, Monetary, relational fields), Manifest configuration (__manifest__.py, dependencies, asset bundles), Mixins (mail.thread, mail.activity.mixin, mail.alias.mixin, utm.mixin), ORM Model methods (search, CRUD, domain filters, recordsets, CamelCase model naming), Migration scripts (pre/post/end hooks, data migration), OWL frontend components (hooks, services, lifecycle), Performance optimization (N+1 prevention, batch ops, _read_group), QWeb Reports (PDF/HTML, paper formats, barcodes, t-out), Security/ACL (record rules, field permissions, privilege-based groups, @api.private), Testing (TransactionCase, HttpCase, mocking, query count assertions), Transactions (savepoints, UniqueViolation, serialization failures), Translations (i18n, PO files, translatable fields), XML Views (list/form/search, kanban card templates, xpath inheritance, QWeb templates). Use when writing, reviewing, or debugging any Odoo 19 Python or XML code, creating or modifying modules, fixing performance issues, or looking up Odoo 19 API patterns and best practices. Includes CSS/SCSS asset authoring and review for Odoo addons.

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

Use Nexscope (Search Intelligence Framework) data to analyze ASIN traffic source composition and exposure distribution, covering current period/previous period/newly entered/exited period comparisons. Trigger when the user mentions ASIN traffic sources, traffic structure analysis, organic traffic vs paid traffic share, exposure score breakdown, period comparison, new/exited traffic keywords, competitor traffic analysis, SP ad keyword count, brand ad exposure, Amazon's Choice exposure, editorial recommendation exposure, Top Rated exposure, video ad exposure, organic search exposure ratio, PPC traffic sources, promotional deal traffic sources, recommendation slot structure breakdown, ASIN traffic analysis, traffic sources, organic traffic share, ad traffic share, exposure analysis, traffic structure, period-over-period comparison, keyword churn, Nexscope. Even if the user does not explicitly mention "Nexscope", if their need involves analyzing an ASIN's traffic sources, exposure channel distribution, cross-period comparison, or competitor traffic structure comparison, this skill should also be triggered.

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

Balancing chemical equations, reaction classification, stoichiometric calculations, acid-base chemistry, oxidation-reduction (redox) reactions, and thermochemistry. Covers conservation of mass, mole ratios, limiting reagents, percent yield, Bronsted-Lowry and Lewis acid-base theory, pH calculations, oxidation states, half-reaction balancing, enthalpy, Hess's law, and calorimetry. Use when solving quantitative chemistry problems involving reactions, energy changes, or solution chemistry.

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

Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit - `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.

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

"Corporate innovation-governance toolkit integrating Stage-Gate process, 3 Horizons model, innovation portfolio management, open innovation, corporate venture capital (CVC), innovation KPIs, and intrapreneurship. Use for innovation-portfolio design, second-curve planning, innovation-project review gating, open-innovation evaluation, CVC setup, innovation-KPI design, or managing tension between core and new businesses. Triggers: 『第二曲線』『創新專案怎麼管』『新事業孵化』『收購投資新創』『Stage-Gate』『研發投資組合』『內部創業』『開放式創新』『CVC』『3 Horizons』『創新 KPI』. For Taiwan EMBA innovation-management/strategy/technology-management cases (台大／中山). Startup basics: use Asgard `ux-lean-startup`; innovation theory: use Asgard `grad-disruptive-innovation`, `grad-ambidexterity`; 家族二代接班治理: use `biz-corporate-governance` 或 `ops-talent-strategy`; ESG/淨零策略結合: use `biz-net-zero-transition`.".

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

Use when designing, implementing, or reviewing frontend interaction motion, page transitions, scroll animation, Framer Motion, GSAP, Lottie, CSS animation, motion intensity, animation performance, reduced-motion behavior, or cinematic but accessible UI motion. Do not use for SVG-only path drawing, Canvas/WebGL rendering, or ordinary hover states; Chinese triggers include motion design, interactive effects, page transitions, scroll animation, Framer Motion, GSAP.

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

Product-led growth and customer-base growth for B2B SaaS. Use this skill for self-serve funnel work (activation, time-to-value, free trial vs freemium, PQL definition, in-product upgrade moments, sales-assist triggers), for the self-guided interactive product demo that runs in front of the login wall (demo portfolio and flow design, gated vs ungated policy, demo seed data and privacy, keeping a published demo in sync with the shipping product, step-level demo analytics), and for growing revenue from existing customers (adoption, expansion, churn-save, the self-serve cancel flow and failed-payment recovery, renewal marketing, net revenue retention, and champion tracking: watching the people who bought and used you at each customer, confirming a job change from evidence, and running both plays a move fires, the seat they left and the account they joined). Also triggers on: PLG, product-led growth, activation, aha moment, time to value, free trial, freemium, PQL, product qualified lead, onboarding, self-serve, customer marketing, expansion revenue, upsell, cross-sell, churn, retention, NRR, renewal, cancel flow, cancellation flow, save offer, exit survey, pause subscription, dunning, failed payment recovery, involuntary churn, people keep canceling, champion tracking, job change signals, job change alerts, our champion left, our champion changed jobs, customer alumni, former customers who moved to a new company, interactive demo, self-guided demo, product tour, click-through demo, demo automation, demo library, should our demo be gated, ungated demo, demo without a sales call, our demo is out of date, demo shows the old UI, put a demo on our homepage, demo completion rate, demo drop-off, try before you talk to sales.

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

Use when writing, auditing, or troubleshooting Salesforce Validation Rules. Triggers: 'validation rule', 'required field formula', 'rule fires unexpectedly', 'integration failing validation', 'data quality', 'errorConditionFormula', 'errorDisplayField', 'errorMessage 255 characters', 'ValidationRule metadata', 'validationRule-meta.xml', 'deploy validation rule inactive', 'bypass custom permission', 'FIELD_CUSTOM_VALIDATION_EXCEPTION', 'validation rule on custom metadata type', 'compound field validation rule', 'require at least one child record before a stage', 'HasOpportunityLineItem'. NOT for Flow-based validation — use admin/flow-for-admins for that.

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

Configure and troubleshoot Salesforce Billing revenue recognition rules, schedules, and GL transaction generation under ASC 606. Triggers: 'revenue schedule not generated after order activation', 'blng__RevenueSchedule__c missing', 'blng__RevenueRecognitionRule__c on a product', 'Finance Periods not set up', 'performance obligation allocation for bundled products', 'distribution method', 'ASC 606 in Salesforce Billing'. NOT for billing schedules, invoice plans and invoice runs - use admin/billing-schedule-setup. NOT for invoice-to-payment mismatches at month-end close - use data/billing-data-reconciliation.

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

Use when designing or refactoring Salesforce access architecture around minimal profiles, permission sets, permission set groups, muting, and assignment governance. Triggers: 'profile sprawl', 'permission set strategy', 'PSG architecture', 'access bundle design', 'least privilege', 'how to slice permission sets', 'permission set naming convention', 'permission set license restriction', 'PSG status Outdated', 'permissionset-meta.xml'. NOT for PSG muting mechanics and recalculation order — use admin/permission-set-group-composition. NOT for record-sharing model design — use admin/sharing-and-visibility. NOT for time-boxing an assignment — use admin/permission-set-expiration.

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