Results for “settings”

Use when configuring org-wide platform settings: MFA enforcement, My Domain setup and deployment, session timeout and security settings, password policies, trusted IP ranges (Network Access), and CSP Trusted Sites. Owns these settings as deployable Settings metadata (Security.settings, MyDomain.settings, Company.settings, Language.settings) and the order in which a new org is stood up. Trigger keywords: 'MFA setup', 'My Domain', 'session settings', 'password policy', 'trusted IP ranges', 'CSP trusted sites', 'Security.settings', 'SecuritySettings metadata', 'MyDomainSettings', 'settings-meta.xml', 'enhanced domains', 'deploy org settings', 'new org setup order', 'sessionTimeout enum', 'lockSessionsToIp', 'enableAdminLoginAsAnyUser'. NOT for user-level login restrictions (use user-management), NOT for permission model design (use permission-sets-vs-profiles), NOT for security audit and hardening review (use security/org-hardening-and-baseline-config).

The English summary is being prepared. Showing the original description.

Use when choosing between Custom Metadata Types and Custom Settings, understanding hierarchical vs list settings, deployment behavior, governor limit implications, or accessing either from Apex and Flow. Trigger keywords: 'custom metadata vs custom settings', 'hierarchical settings per user profile', 'deployable config vs runtime settings', 'getValues getInstance in apex', 'flow get records custom settings'. NOT for modelling the CMT itself or protecting packaged defaults — use admin/custom-metadata-types. NOT for records users edit as business data — use admin/object-creation-and-design. NOT for secrets — use integration/named-credentials-setup. More trigger keywords: customSettingsType, customSettingsVisibility, SetupOwnerId, getOrgDefaults, getAll, DUPLICATE_VALUE in test, SeeAllData custom settings, enableAdvancedCSSecurity, customSettingAccesses, org default profile user override.

The English summary is being prepared. Showing the original description.

Upgrade MSTest v1 or v2 projects to v3, including partially completed migrations. Update packages, repair affected assertions and test data, replace legacy settings, and compare test results while preserving the existing test runner.

• Upgrading an MSTest v1 or v2 project to v3
• Fixing compilation errors after a v3 package update
• Repairing DataRow values that mismatch parameter types

Move Python application settings out of code and into environment variables. Use pydantic-settings to check value types and required fields at startup, organize development and production settings, and keep secrets out of version control.

• Replace hardcoded settings with environment variables
• Separate development and production configuration
• Detect missing settings at application startup

Inspect Muse Code’s saved settings and defaults, then make targeted changes when explicitly requested. Explain reasoning and display options while distinguishing persistent configuration from the settings currently active in a running session.

• Check saved settings and defaults
• Change the saved reasoning effort
• Adjust reasoning summaries and output detail

Manage Organization Settings and Platform Settings via the TRES MCP GraphQL API. Use when users ask about org settings, platform settings, configuration, feature flags, enable/disable platforms, balance diff, commit strategy, cost basis, ERP, pricing, sync boundaries, or any setting read/write operation. Trigger phrases include "get settings", "show settings", "update settings", "change settings", "enable platform", "disable platform", "balance diff", "commit strategy", "cost basis strategy", "set min sync date", "configure", "turn on", "turn off".

The English summary is being prepared. Showing the original description.

Get answers about Qwen Code usage, features, configuration, and troubleshooting from its official documentation. The skill also helps inspect and edit user or project settings files when configuration changes are requested.

• Learning Qwen Code features and commands
• Checking how to configure MCP server connections
• Reviewing or changing settings.json

The Matrx user settings system (SettingsShell, useSetting, tab registry). Use when adding a preference or settings tab, binding a Redux slice to settings, wiring a settings deep link, or touching features/settings, components/official/settings, or components/user-preferences.

The English summary is being prepared. Showing the original description.

Read and update application settings through APIs, including system prompts, reasoning limits, IP filters, and login requirements. Also manage proxy and cache settings, with guidance on how reasoning settings affect requests sent to AI providers.

• Review and update system prompts
• Adjust reasoning request settings
• Manage IP filters and login requirements

Helps implement centralized settings management in Java with Azure App Configuration. Covers environment-specific settings, feature flags that control feature availability, and snapshots that preserve settings at a particular point in time.

• Manage settings separately for development and production
• Configure feature flags for gradual rollouts
• Preserve release settings in snapshots

Add project-specific settings to Claude Code plugins using local Markdown files. Learn how to combine structured YAML settings with written context, read them from hooks and commands, and validate configuration values.

• Add project-specific configuration to a plugin
• Control hook activation through settings
• Store agent state alongside task instructions

View and change shared project settings and personal overrides without editing YAML manually. See which values actually apply, where they come from, which allow personal overrides, and which are stored without affecting behavior.

• Checking effective settings and their sources
• Changing settings shared by the team
• Applying personal overrides

Read and change a running CARLA server’s timing, physics substeps, and rendering settings. Switch between client-controlled steps and automatic progression, keep Traffic Manager synchronization aligned, and read back the settings to verify each change.

• Setting a fixed simulation rate for sensor capture
• Keeping Traffic Manager aligned with synchronous mode
• Disabling rendering or adjusting physics substeps

Change DeepChat preferences through conversation, including theme, interface language, font size, sound effects, and whether copied text includes COT details. Dedicated tools apply supported changes, while other requests open the relevant settings section with guidance.

• Switch DeepChat to a dark theme
• Change the interface language or font size
• Turn off DeepChat sound effects

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a deployment-settings.json file with per-stage override values. Use when asked to: "configure environment variables", "add env vars", "set up deployment variables", "make site settings environment-specific", "configure ALM variables", "set up env-specific settings", "add deployment settings", "configure per-environment settings".

The English summary is being prepared. Showing the original description.

Registers a custom settings tab in the JetFormBuilder admin Settings page using the official JFB API — PHP-side Base_Handler subclass for persistence, JS-side wp.hooks filter for the Vue tab component, native cx-vui field components for the UI. Use when a plugin needs its own configuration tab inside JFB Settings (API credentials, defaults, debug flags, third-party integrations) and the developer must NOT roll their own admin page. Triggers on mentions of "JetFormBuilder settings tab", "JFB settings page", "Base_Handler", "register-tabs-handlers", "jet.fb.register.settings-page.tabs", "cx-vui-input", or when a JFB-companion plugin is being scaffolded.

The English summary is being prepared. Showing the original description.

Claude Code 設定の表示・更新・ローカル更新を統合管理する。「Claude 設定管理」「設定を表示」「settings を更新」「local settings を更新」「権限設定を変更」「設定ファイル管理」「claude settings」などで起動。引数があれば優先し、なければ発話内容から view/update/local-update を判定。

The English summary is being prepared. Showing the original description.

Make Claude Code plugin behavior configurable per project using local Markdown files. Learn to store structured settings and notes, read them from hooks or commands, and handle defaults, validation, and user-local configuration.

• Adding per-project settings to a plugin
• Controlling whether hooks are enabled
• Saving agent task details and progress state

Move useful memory notes and MCP server settings from Claude Code or Codex into Muse Code. MCP servers connect agents to external tools; the skill checks compatibility and reports settings that need attention.

• Bring saved preferences into Muse Code
• Import useful project memory notes
• Move MCP server settings to Muse Code

Read and change Superset desktop preferences through its command-line tool, without opening settings. Adjust fonts, terminals, notifications, and Git options, or create and install custom color themes from JSON files, with local operation and no login required.

• Switching themes and increasing terminal text size
• Creating and installing a custom color theme
• Adjusting notification volume and sounds

Build reusable React components that save settings in browser storage and support keyboard selection. The patterns cover settings dialogs and command palettes, with guidance on TypeScript types, storage keys, and managing keyboard focus.

• Keeping app settings across page reloads
• Building command selection with arrow keys and Enter
• Creating reusable settings dialogs

permission-ledger hook が記録した permission prompt と各リポの .claude/settings.local.json から allow 昇格候補を集計し、ユーザーが選んだものだけを ai-agents/settings/claude/settings.json に反映する。 「許可ルールを見直したい」「permission prompt を減らしたい」「承認した操作を allow に入れたい」 「permission review」などと言われたときに `/permission-review` で使う。

The English summary is being prepared. Showing the original description.

Manage command-line tools connected to OmniRoute through its API. Inspect tool status, read or change settings, manage Codex profiles and backups, and invoke tool plugins for automation tasks.

• Reviewing settings across connected tools
• Managing Codex profiles
• Checking tool status and logs

Helps Claude work in desktop apps by viewing screenshots, clicking, typing, and scrolling. It covers access approval, choosing appropriate tools, and handling app restrictions for tasks in Notes, Finder, settings, and other native apps.

• Organizing notes in Notes
• Working with files in Finder
• Checking settings shown on screen