Results for “hierarchy”

Use when designing or maintaining the role hierarchy as a record-access mechanism. Trigger keywords: role hierarchy, manager cannot see subordinate records, grant access using hierarchies, role reparenting, portal role, how deep should the role hierarchy be, design the role hierarchy. NOT for territory models - use admin/enterprise-territory-management. NOT for rule-based grants - use admin/sharing-rules. NOT for the overall model - use admin/sharing-and-visibility.

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

Designing Campaign Hierarchy for program-level ROI tracking, configuring Customizable Campaign Influence (CCI) attribution models, and interpreting multi-touch attribution from MCAE B2B Marketing Analytics. Trigger keywords: campaign ROI, attribution model, campaign hierarchy, first-touch, last-touch, multi-touch, CCI, campaign influence, revenue attribution, campaign member status. NOT for deciding which attribution model and KPIs to adopt before any config - use admin/marketing-reporting-requirements. NOT for MCAE connector setup or the campaign sync that writes Campaign Member records - use admin/mcae-pardot-setup. Also covers: CampaignSettings, enableCampaignInfluence2, enableAutoCampInfluenceDisabled, enableB2bmaCampaignInfluence2, enableAccountsAsCM, CampaignInfluenceModel metadata, isDefaultModel, isModelLocked, recordPreference, AllRecords, RecordsWithAttribution, CampaignInfluence.RevenueShare, ModelType, CampaignMemberStatus IsDefault HasResponded SortOrder, HierarchyActualCost, HierarchyAmountWonOpportunities, TotalNumberofResponses, Opportunity.CampaignId primary campaign source.

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

Analyze a monolithic codebase before splitting it into modules or services. The skill inventories components, examines duplication, hierarchy, and dependencies, then proposes groupings aligned with business domains, with optional checks against business terminology and boundaries.

• Assessing component sizes before splitting a monolith
• Finding duplicated business logic across modules
• Reviewing module hierarchy and dependencies

Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).

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

Unity Prefab / Scene / Asset の壊れた参照・Variant override・配線ミスを構造化応答で診断し、 dry-run → confirm 経路で安全に修復するための MCP ツールリファレンス。 Editor Bridge のセットアップ手順もここに含む。 トリガー: .prefab, .unity, .asset, .mat, Prefab, Variant, 配線, 参照, 壊れた参照, broken reference, GUID, fileID, override, パッチ, patch plan, validate refs, validate structure, where-used, inspect variant, inspect wiring, inspect hierarchy, wiring, null参照, null reference, MonoBehaviour, 階層, hierarchy, Transform整合, 孤立, orphan, 重複fileID, duplicate fileID, Editor Bridge, Bridge セットアップ, bridge setup, deploy_bridge, UNITYTOOL_BRIDGE_WATCH_DIR, watch ディレクトリ のいずれかに該当する作業で使用する。

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

Plan a website's pages, hierarchy, navigation, URLs, and internal links. Produce page trees, visual sitemaps, URL tables, and navigation specifications to guide a new site or reorganize an existing one around visitor needs and business goals.

• Plan the page structure for a new website
• Reorganize navigation on an existing site
• Design URLs and internal links for a blog section

USE ONLY for (1) two or more projects with repeated MSBuild policy, targets, or package versions, or (2) an existing Directory.Build.props/targets/rsp hierarchy with an import, placement, or layering defect. A one-project repo without an existing Directory.Build file is outside scope; do not load this skill. Covers centralizing shared policy and targets, Directory.Packages.props across projects, parent hierarchy/import structure, props-versus-targets placement, and folder/project exceptions. An existing hierarchy defect remains in scope when only one project is affected. For property value or condition semantics use property-patterns. Exclude legacy-to-SDK migration and non-MSBuild systems.

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

Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).

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

USE ONLY for (1) two or more projects with repeated MSBuild policy, targets, or package versions, or (2) an existing Directory.Build.props/targets/rsp hierarchy with an import, placement, or layering defect. A one-project repo without an existing Directory.Build file is outside scope; do not load this skill. Covers centralizing shared policy and targets, Directory.Packages.props across projects, parent hierarchy/import structure, props-versus-targets placement, and folder/project exceptions. An existing hierarchy defect remains in scope when only one project is affected. For property value or condition semantics use property-patterns. Exclude legacy-to-SDK migration and non-MSBuild systems.

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

Use when choosing between Salesforce record-access mechanisms or reviewing the access model end to end. Trigger keywords: OWD, org-wide defaults, sharingModel, externalSharingModel, record access model, sharing architecture, which sharing mechanism, UserRecordAccess, __Share, RowCause, why can user see too much. NOT for sharing rules - use admin/sharing-rules. NOT for role hierarchy - use admin/role-hierarchy-design.

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

Use when configuring or troubleshooting Salesforce Enterprise Territory Management (ETM): territory models, territory types, territory hierarchies, account assignment rules, opportunity territory assignment, and forecast by territory. Trigger keywords: territory model, territory hierarchy, ETM, assign accounts to territories, territory forecast, territory activation. NOT for choosing the coverage model first — use admin/territory-design-requirements. NOT for role hierarchy — use admin/sharing-and-visibility. NOT for Field Service ServiceTerritory — use admin/fsl-service-territory-setup. Trigger keywords: Territory2, Territory2Model, Territory2Rule, territory2Model-meta.xml, ObjectTerritory2Association, UserTerritory2Association, territory assignment rule, run assignment rules, territory access level, Manage Territories permission.

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

Project-orientation workflow (/orient): installs predicate's enforcement into a target project, maps its structure and goal, and authors the persistent conditioning layer (AGENTS.md goal-hierarchy) so every subsequent walk is anchored and gated. Trigger when: - Onboarding a new project into predicate for the first time. - Refreshing an existing project's AGENTS.md hierarchy against the current state of the repository (re-run = refresh). - Prompt contains: /orient, orient workflow, onboard project, project orientation, AGENTS.md hierarchy, persistent conditioning layer.

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

Review a screen, user flow, or component against the user's task. Assess visual hierarchy, interaction cues, error handling, accessibility, and consistency, then provide prioritized fixes with reasons and identify strengths worth preserving.

• Getting feedback on a screen or mockup
• Checking usability before a feature launches
• Reviewing a flow where users may drop off

Create a single HTML wireframe for a desktop dashboard using grey blocks, placeholder text bars, and crossed image boxes. Review navigation, information hierarchy, and panel placement before choosing final colors, copy, or imagery.

• Reviewing a desktop dashboard layout
• Checking navigation and information hierarchy
• Planning KPI, chart, and table placement

Extract a Figma file into local project files containing its element hierarchy, reusable color and typography settings, and exportable assets. The structured snapshot supplies source data for later design mapping and implementation steps.

• Extract a Figma file's element hierarchy
• Collect color, typography, and spacing settings
• Prepare assets for later implementation steps

Control a running iOS Simulator on macOS from Orca’s live device pane. Perform taps, gestures, typing, button presses, and rotation, and inspect the interface element hierarchy to check app changes in the simulator.

• Check iOS app changes in the simulator
• Reproduce gestures and text entry
• Check the display after rotating the device

Review web page headings for skipped levels, unclear labels, and incorrect structure. Organize HTML headings around the content so people using screen readers can understand page sections and navigate between them.

• Audit heading levels on a web page
• Improve navigation for screen reader users
• Review headings in design-system patterns

Audit breadcrumb structured data, a machine-readable description of a page’s navigation path. Check that BreadcrumbList matches the visible trail and site hierarchy, then guide JSON-LD changes using the rendered HTML and HTTP response.

• Check breadcrumb structured data
• Add JSON-LD for visible breadcrumbs
• Review site hierarchy after template changes

Audit GitHub issues to find open work outside a masterplan, distinguishing missing parents from missing plan ancestors. Preview or apply removal of closed issues from the hierarchy while keeping their open children connected to the plan.

• Finding open issues outside a masterplan
• Distinguishing missing parents from missing plan ancestors
• Checking issue organization in automation

Review a Figma design, screenshot, or written description for usability, visual hierarchy, consistency, and accessibility. Receive specific findings, explanations, and prioritized improvements, with feedback tailored to the design stage and intended users.

• Reviewing an early screen design
• Checking navigation and onboarding usability
• Finding inconsistent colors, spacing, and typography

Review a Figma design, screenshot, or written description for usability, visual hierarchy, consistency, and accessibility. Receive specific findings, explanations, and prioritized improvements, with feedback tailored to the design stage and intended users.

• Reviewing an early screen design
• Checking navigation and onboarding usability
• Finding inconsistent colors, spacing, and typography

Help a long-running agent reconnect with the intended product outcome after context compaction or a major work transition. Trace the current work hierarchy and read relevant source files to rebuild grounding before the next consequential action.

• Restore context after conversation compaction
• Recheck the intended outcome during a long session
• Review the work hierarchy before an important action

Find classes left in parent folders or namespaces and identify nested component structures. Compare consolidation, splitting, and shared code extraction, then plan and carry out refactoring with updated references and tests.

• Find classes left in parent namespaces
• Compare consolidation and splitting of nested components
• Move shared utilities into a dedicated component

Review and refine websites and apps by finding generic decoration, inconsistent visual choices, and interface defects. Preserve the established art direction while improving hierarchy, layout, interaction states, and the connection between design choices and product needs.

• Removing unnecessary decoration from an existing page
• Keeping new components consistent with the design system
• Checking content hierarchy and primary actions