Salesforce Architect

Salesforce architect — SfSkills domain router

Solution and platform architecture: multi-org strategy, scalability limits, licensing, Well-Architected reviews and architecture decision records.

106 skill packages live under ${CLAUDE_PLUGIN_ROOT}/skills/architect/<slug>/SKILL.md. They are not loaded — reach them by path, on demand.

Generated by scripts/build_plugin.py. Do not hand-edit.

How to find the right skill

Three mechanisms, listed in order of reliability on a fresh install. Use the first one that is available; do not stop at a guess.

1. The shipped roster (always works, no setup). Read references/skill-index.md next to this file. It lists every architect skill package with a one-line gloss, generated from registry/skills.json. Scan it and pick by name.

2. The MCP server (fast, needs the sfskills-mcp server connected). Call the search_skill tool with the user's phrasing and domain: "architect". It returns ranked skill ids. get_skill then returns the package contents.

3. The search CLI (fast, needs a locally built index).

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/search_knowledge.py" "<the user's question>" --domain architect --json

This needs vector_index/, which is not shipped — it is gitignored and must be built once per clone:

cd "${CLAUDE_PLUGIN_ROOT}" && python3 -m pip install -r requirements.txt && python3 scripts/build_index.py

If the command errors or reports Coverage: NONE, fall back to mechanism 1 rather than telling the user the topic is uncovered.

Then read the package. Open the exact ${CLAUDE_PLUGIN_ROOT}/skills/<domain>/<slug>/SKILL.md the lookup returned, plus its references/gotchas.md and references/llm-anti-patterns.md. Do not answer from this router: it is a map, not the territory.

Featured entry points

Curated starting points when the request is broad or the lookup is ambiguous. This is a shortlist, not the catalogue — the roster at references/skill-index.md has all 106.

• ${CLAUDE_PLUGIN_ROOT}/skills/architect/solution-design-patterns/SKILL.md — the pattern catalogue to check before inventing a design
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/well-architected-review/SKILL.md — running a Salesforce Well-Architected assessment against a real org
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/architecture-decision-records/SKILL.md — capturing the decision and its alternatives so it survives the team
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/large-data-volume-architecture/SKILL.md — skinny tables, custom indexes, sharing recalculation and LDV design
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/limits-and-scalability-planning/SKILL.md — org-level limits that constrain a design before code does
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/integration-framework-design/SKILL.md — the org-wide integration layer, not a single point-to-point callout
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/security-architecture-review/SKILL.md — the access model as an architecture concern rather than a config task
• ${CLAUDE_PLUGIN_ROOT}/skills/architect/multi-org-strategy/SKILL.md — when a second org is right and what it costs forever after

Decision trees

Read the tree before activating a skill when the request could be solved more than one way, and cite the branch that decided it.

• ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/automation-selection.md — the platform's automation routing, one layer above any skill
• ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/integration-pattern-selection.md — REST vs Bulk vs events vs Connect vs MuleSoft
• ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/sharing-selection.md — the access-model decision at design time
• ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/performance-tuning.md — where the time goes, before proposing a redesign

Run-time agents for this domain

Invoke one of these subagents when the ask is a whole workflow rather than a single question:

• salesforce-decision-facilitator — Compare viable Salesforce options with evidence, hard gates, sensitivity, and reversibility
• waf-assessor — Well-Architected Framework assessment

Rules

1. Answer from the opened architect package, never from this router.
2. Cite the skill id and, where one applied, the decision-tree branch.
3. Never claim a topic is uncovered without pasting lookup output.
4. Never deploy to an org.