Claude Skills by PranavNagrecha

Use when building a Lightning Web Component that runs from a record page quick-action button — either a screen action that renders UI in a modal or a headless action that invokes logic with no UI. Triggers: 'lwc quick action on record page', 'headless quick action no ui', 'closeactionscreenevent not working', 'how to pass recordid into quick action lwc'. NOT for Flow screen components — use lwc/lwc-in-flow-screens. NOT for global actions without a record context — use admin/global-actions-and...

LWC reactivity after API v48 — @track vs class fields, deep object updates, rerender pitfalls. Triggers: LWC reactivity, @track, reactive object, rerender. NOT for wire adapter refresh — use lwc/lwc-wire-refresh-patterns. NOT for record form data — use lwc/lwc-lightning-record-forms.

lightning-record-picker base component (Winter '24 GA): object/record filter, displayInfo/matchingInfo, graph-ql filters, accessibility. Replaces ad-hoc lookup inputs. NOT for a fully custom typeahead lookup — use lwc/lwc-custom-lookup.

Use when designing or reviewing Lightning Web Components for DOM safety, Lightning Web Security. Triggers: 'innerHTML in lwc', 'Lightning Web Security', 'document.querySelector', 'light DOM security', 'secure apex class for lwc'. NOT for org-wide sharing architecture or Apex-only security reviews when no LWC surface — use lwc/lwc-light-dom.

Use when building LWCs that must react to live server pushes — Platform Events, Change Data Capture, or streaming updates — via the lightning/empApi (CometD) subscription model. Covers lifecycle, replayId, error handling. NOT for publishing events (see platform-events or apex-platform-events) — use integration/platform-events-integration.

Decide Shadow DOM vs Light DOM for an LWC — Salesforce distribution rules, Locker/LWS, third-party library needs. Triggers: shadow vs light DOM, renderMode decision. NOT for implementing Light DOM after the decision — use lwc/lwc-light-dom.

ShowToastEvent in LWC: variants (success/warning/error/info), modes (dismissible/pester/sticky), message formatting, NOT supported in LWR Experience Cloud sites, alternatives (lightning-alert, inline banners). NOT for custom notification types (use admin/custom-notification-types). NOT for SLDS popovers.

Use when a Lightning Web Component needs to let a parent inject markup into predefined regions using `<slot>` — default and named slots, `slotchange` wiring, fallback content, and detecting slot emptiness. NOT for rendering a dynamic component whose tag name is chosen at runtime (that is `lwc:is`) — use lwc/lwc-dynamic-components. NOT for third-party custom-element interop — use lwc/lwc-web-components-interop.

Share state across LWCs using pub/sub, Lightning Message Service, @wire, and reactive stores. NOT for in-component reactivity — use lwc/lwc-reactive-state-patterns.

Plan, execute, and verify a Lightning Web Components JavaScript-to-TypeScript migration with an explicit Salesforce toolchain strategy, bundle-by-bundle sequencing, Lightning base-component types, generated-output ownership, tests, and rollback. Trigger keywords: migrate LWC to TypeScript, LWC .ts, defaultLwcLanguage, lightning-types, TypeScript LWC build. General TypeScript tutorials and non-Salesforce web applications are outside this package. NOT for performance refactoring unrelated to th...

Use when building, deploying, or reviewing a React web app that runs natively on Salesforce via Salesforce Multi-Framework and the UIBundle metadata type — scaffolding with `sf template generate ui-bundle`, data access through @salesforce/sdk-data (createDataSDK, GraphQL, Apex fetch), App Launcher / Custom Application / Experience targeting, and embedding Agentforce chat with the Agentforce Conversation Client. Open Beta: scratch orgs and sandboxes only, English default language, no productio...

Use when configuring single sign-on into or out of a Salesforce org. Trigger keywords: SAML SSO setup, configure single sign-on, identity provider metadata, Just-in-Time provisioning, My Domain SSO, OpenID Connect, SSO-only login, Salesforce as identity provider. NOT for SSO failures - use security/sso-saml-troubleshooting. NOT for OAuth integration access - use admin/connected-apps-and-auth.

Answers Salesforce admin documentation-generation requests: "generate a data dictionary for Account", "create an admin handbook for this org", "write an onboarding doc for a new developer", "generate an architecture overview", "produce a sharing-model summary", "draft a compliance report on PII". Drives the v2.5 documentation-generator tier (`generate_data_dictionary`, `generate_admin_handbook`, `generate_onboarding_doc`, `generate_architecture_overview`, `generate_sharing_summary`, `generate...

Answers admin questions about Salesforce's legacy automation layer: "what workflow rules touch Account", "which approval processes are still active", "what assignment rule routes Cases", "is this workflow being replaced by a flow", "which fields does this duplicate rule check", "what emails go out for this approval", "show me the auto-response rules for Lead". Calls `sfi.get_impact` and `sfi.get_edges` to find workflow rules, approval processes, assignment/auto-response/escalation rules, dupl...

Answers Salesforce admin questions about which page layout a user sees and why: "what layout does user X see for Account", "which page layout for Sales rep on Opportunity", "why is this user seeing this layout", "which record type does this profile default to", "what's the layout for record type Y", "user reports wrong layout", "page layout assignments for profile X". Call `sfi.run_analysis` with `{ "name": "sfi.layout_for_user", "args": { … } }` (cascade over profile lookup, layoutAssignment...

Saved, repeatable admin routines for the sf-intelligence org that batch the right `sfi.*` tools in one request, then synthesize ONE report. Fire when the user asks for a named routine rather than a single fact — "run my pre-deploy checklist", "I inherited this org, give me the tour", "run a security audit", "what's junk in this org / what can I clean up", "is my org healthy / on fire", "audit sweep", "cleanup sweep", "go-live check". Each playbook is an ordered tool batch; run it end to end, ...

Answers Salesforce admin sharing/visibility questions like "why can't user X see Y", "who can see this record", "what would let this user see Y", "the user says they can't see Z", "visibility check for X on Y", "sharing rules touching Z", "role hierarchy from Foo up", "what grants Edit access to Bar". Calls `sfi.why_cant_user_see_record` (cascade over OWD → permission grants → role hierarchy → owner sharing rules → criteria sharing rules → manual/sets/teams) and explains the verdict honestly:...

Conversational interface for questions about the Salesforce org backed by this repo's `org-kb/` vault. Use for any question about schema, dependencies, permissions, naming conventions, Apex source, Flow metadata, or vault freshness — except refresh requests (those fire `refreshing-the-org-vault` instead) and initialization (which fires `/sfi-init`). Triggers on questions starting with "what", "which", "show me", "find", "list", "who can", "where is", "how many", "does", "is there", or "when w...

Answers Salesforce architect async + event-driven topology questions that v2.8 surfaces beyond the v1.5 integration tier. Triggers: "who subscribes to CDC events on Account", "what change-data-capture subscribers do we have", "what's the async chain depth from this Queueable", "show me every scheduled job", "what outbound messages does this org send", "give me every endpoint URL in one place". Drives the cascade: `event_topology` (the event plane — Platform Events, Change Data Capture enablem...

Answers cross-org metadata comparison questions for Salesforce architects — sandbox-vs-prod drift, prod-vs-prod (multi-customer) audits, "what changed since I last refreshed?" diffs, and Lead-vs- Contact (intra-org) field-mapping for the conversion. Triggers on phrases like "compare sandbox vs prod", "compare two orgs", "what's drifted between {vaultA} and {vaultB}?", "is this object different in sandbox?", "does System Administrator have the same permissions in sandbox?", "Lead conversion ma...

Answers "what breaks if I change X?" CHANGE-IMPACT questions for Salesforce architects. Triggers on phrases like "what breaks if I change/delete/rename", "what depends on", "what's the impact of", "is it safe to deprecate", "blast radius of". USAGE phrasings — "where is X used", "what touches X", "which components reference X", "show me everything that uses X" — are NOT this skill: route them to `sfi.find_component_usages` (the §C3 universal usage dispatcher), and "find formulas using X" to `...

Answers Salesforce architect integration questions: "draw me our integration map", "what subscribes to this platform event", "who calls this REST API", "which classes are queueable / batchable", "what runs async in this org", "where does this external data source connect", "what is our external API surface", "which external services use this named credential", "audit our auth providers". Call `sfi.run_analysis` with `{ "name": "sfi.integration_map", "args": { … } }` (organized map of auth + e...

Answers business-user-flavored Salesforce questions like "what does this field mean in English", "what happens when I close this opportunity", "why can't I do X", "how do I find report Y", "what's the SLA on this case", "how are cases routed to agents", "is this field required", "what's this object for", "how is this calculated". Classifies the intent and routes to the right `sfi.*` tool, OR honestly refuses when v1.x doesn't yet model the answer (record-level data, reports, dashboards, live ...

Conversation memory and follow-up handling for the sf-intelligence org. Fire on follow-up turns that depend on what was just discussed — pronouns and ellipsis ("what about the other one?", "and on Contact?", "is that one safe to delete?", "show me its dependencies", "the second one"), refinements of a prior answer, or "what should I look at next?". Keeps the resolved component, the last tool/plane, and the disambiguation options from the previous turns so the user does not have to repeat them...

Answers code-source-focused developer questions across the full org code surface: Apex classes, Apex triggers, and the v1.4 frontend tier (LWC, Aura, Visualforce). Triggers: "where is field X used in Apex", "find LWC components reading this field", "what calls this Apex from VF", "Aura references to this object", "who reads/writes this field from code", "what classes call MyClass.someMethod", "is it safe to rename this method", "find all Apex references to this", "what Apex/LWC/VF touches thi...

Answers Salesforce developer code-quality questions: "audit my Apex for quality issues", "find governor-limit risks", "where do we have hardcoded IDs / emails / usernames", "check CRUD / FLS enforcement", "what tests are missing / fake-covered", "find dead code", "review this Apex class", "what methods does this class have". Drives the v2.1 quality-recognizer cascade (`code_quality_audit`, `governor_limit_risks`, `find_hardcoded_values`, `crud_fls_audit`, `test_coverage_gaps`), the v2.4 hygie...

Answers Salesforce developer "show me EVERYTHING about this field" and "trace this field's lineage" deep-forensics questions: "what does Account.Industry__c touch", "give me the full field profile for X", "where does this field's data come from", "what fires when this field changes", "show me the upstream + downstream walk for this field", and the same question one tier up: "show me everything about the Contact object". Cascades the v3.0 synthesis tools (`field_360`, `field_lineage`) plus the...

Answers Salesforce developer "where is X used everywhere" and "what does this field mean in our org" discovery questions: "find every reference to `Industry__c`", "do we already have a field for customer health", "what does this field actually mean", "is `Status` the same as `Stage` here", "is this field manually entered or automated", "what does this acronym mean", "find this literal anywhere in the org". Cascades over the v2.2 universal- search tools (`find_field_anywhere`, `find_semantic_f...

Answers Salesforce developer "what breaks if I change X / where is M reachable from / what does this method touch / is this dead code" questions. Cascades the v2.3 what-if composer family (`what_if_deactivate_flow`, `what_if_disable_trigger`, `what_if_change_method_signature`, `what_if_change_field_type`, `what_if_remove_picklist_value`, `what_if_make_field_required`, `what_if_merge_profiles`, `what_if_split_profile`) and the v2.7 deep code-understanding tools (`call_graph`, `downstream_effec...

Answers Salesforce admin/architect freshness questions like "when was X modified?", "who built this?", "what changed since last week?", "has this been touched since go-live?", "what changed in the last sprint?". Call `sfi.run_analysis` with `{ "name": "sfi.last_modified", "args": { … } }` and `sfi.changed_since`. Discloses v1.7 honesty axis: when Tooling API enrichment hasn't run, returns `enriched: false` with explicit guidance to run `sfi refresh --with-tooling-api`; never fabricates dates.

Diagnostic skill for the SfIntelligence vault. Use when the user invokes `/sfi-status`, says "is something wrong?", "the vault feels off", "something looks stale", "are we connected?", "is the index current?", or when a previous `sfi.*` MCP call returned a `degraded` or `unhealthy` status, an unexpected error envelope, or two consecutive errors. Runs three probes — `sfi.health_check`, `sfi.get_manifest`, and `sf org list --json` — and reports findings as a numbered checklist. Reports only; su...

Surfaces observed naming-convention patterns from the SfIntelligence vault. Use when the user asks "what's our convention", "what's the naming standard", "do we always …", "is this consistent with the rest of the org", or proposes a new component name and wants it sanity-checked ("can I name this `CustomerOrder__c`?", "should I call this `Foo__c` or `Bar__c`?"). Calls `sfi.get_naming_convention_report` and reports its observations as **heuristic** — observed patterns, not enforced rules.

Refreshes the SfIntelligence vault from a live Salesforce org. Use when the user invokes `/sfi-refresh`, or says "refresh", "refresh the vault", "pull latest", "pull the latest from my org", "rebuild the vault", "rebuild the index", "my data is stale", "the vault is stale", "I just deployed changes", or any phrase signaling the vault is out of date relative to the org. Drives `sfi refresh`, which shells out to `sf project retrieve`, runs the full extractor graph, imports into DuckDB, renders ...

Decide whether Salesforce fields can be deleted, and validate someone else's field-cleanup analysis. Traces every dependency (flows, formulas, roll-ups, validation rules, layouts, related lists, reports, dashboards, Apex, LWC, integrations) before any field is dispositioned Keep / Review / Deprecate-then-Remove / Remove. Use when asked about field cleanup, field deprecation, "can we delete this field", unused or dead fields, org cleanup, technical debt cleanup, field usage audit, safe-to-dele...

Answers Salesforce Industries / OmniStudio questions: "walk this OmniScript step by step", "what endpoints does this Integration Procedure hit", "what does this DataRaptor map", "what's inside this FlexCard", "what inputs does this DecisionTable take", "what OmniStudio version is this org on". Drives the v3.2 cascade: `omniscript_flow` (OmniScript step sequence + downstream IP / DataRaptor dispatches), `integration_procedure_chain` (IP action chain + REST endpoints + downstream IP / DataRapto...

Silent pre-loader for the SfIntelligence vault. Fires automatically when the user's message mentions any Salesforce concept — words like "object", "field", "trigger", "flow", "validation rule", "permission set", "profile", "layout", "Apex", "picklist", "lookup", "record type", "metadata", "org", "sandbox"; common object names like Account, Contact, Opportunity, Lead, Case, User; or the custom-suffix patterns `__c`, `__mdt`, `__e`, `__b`, `__r`, `__x`. Calls `sfi.org_card` (the refresh-time or...

Entry point for the SfIntelligence plugin. Use whenever the conversation touches a Salesforce org in this repo — schema, dependencies, permissions, naming conventions, automation, Apex, Flow, integrations, sharing, or any question about a component the org contains. Loads first; teaches Claude the `sfi.*` MCP tool cascade, the resolve-first / ask-a-clarifying-question pattern, the canonical component-ID format, and how to route to the other sf-intelligence skills.

Routes coverage and destructive-verdict questions. Call sfi.coverage_report when the user asks whether the vault is complete, why something was not found, or before narrating safe-to-delete / what-if answers. Render coverageCaveat BEFORE the verdict — never footnote it. Refuse absence-based answers for not-modeled families; distinguish "not in vault" from "not in org".