scc-universal 1.1.0

package/skills/_reference/TESTING_STANDARDS.md

@@ -0,0 +1,96 @@
+# Testing Standards — Salesforce Reference
+
+> Last verified: API v66.0 (Spring '26)
+> Source: <https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing.htm>
+
+## Coverage Requirements
+
+| Context | Minimum Coverage | Recommended Target |
+|---|---|---|
+| Production deployment | 75% org-wide | 85%+ per class |
+| Managed package (AppExchange) | 75% org-wide | 90%+ per class |
+| Per-class (not enforced but tracked) | 0% | 80%+ |
+
+Coverage measures **lines executed**, not branches tested. 100% line coverage can still miss branches in `if/else` statements.
+
+## Core Annotations
+
+| Annotation | Scope | Purpose |
+|---|---|---|
+| `@IsTest` / `@isTest` | Class or method | Marks code as test-only (not counted toward coverage) |
+| `@TestSetup` | Method | Runs once per class; each test method gets its own rollback |
+| `@TestVisible` | Field or method | Makes private members accessible in tests without changing access modifiers |
+| `@testFor(ClassName)` | Class (v66.0+) | Explicitly maps test class to production class for `RunRelevantTests` |
+
+## Test Class Rules
+
+| Rule | Detail |
+|---|---|
+| Test classes deploy to production | They DO count toward the 6 MB Apex code size limit |
+| Test classes are excluded from coverage | They are not included in coverage calculations |
+| `@TestSetup` data is isolated per method | Each test method gets a fresh transaction with setup data |
+| No `SeeAllData=true` | Exception: Pricebook-dependent tests only |
+| No hardcoded Record IDs | IDs differ between orgs and sandboxes |
+
+## Test.startTest() / Test.stopTest()
+
+| Behavior | Detail |
+|---|---|
+| `Test.startTest()` | Resets all governor limit counters — fresh budget for code under test |
+| `Test.stopTest()` | Async work (@future, Queueable, Batch) enqueued inside the block runs synchronously here |
+| Scope | Only one `startTest/stopTest` pair per test method |
+
+## TestDataFactory Pattern
+
+A central `@IsTest` factory class that creates test records consistently across the test suite. Benefits:
+
+- Prevents duplicated record-creation logic across test classes
+- Ensures valid test data with all required fields populated
+- Supports override maps for scenario-specific field values
+- Centralizes maintenance when field requirements change
+
+## Test Method Naming
+
+Format: `test{MethodName}_{scenario}_{expectedResult}`
+
+Examples:
+
+- `testCalculateDiscount_premiumTier_returns20Percent()`
+- `testCreateAccount_duplicateName_throwsException()`
+- `testProcessOrders_emptyList_noExceptionThrown()`
+
+## Assertion API
+
+| API | Minimum Version | Notes |
+|---|---|---|
+| `Assert.areEqual()`, `Assert.isTrue()`, `Assert.fail()` | v56.0+ | Preferred — clearer method names |
+| `System.assertEquals()`, `System.assert()` | All versions | Legacy — still valid |
+
+Every test method must have at least one meaningful assertion. Asserting only that a record was inserted is insufficient — assert specific field values and business logic outcomes.
+
+## Bulk Testing
+
+Always test with **200 records** (the standard trigger batch size). A method that works with 1 record may fail at governor limits with 200.
+
+## Mock Patterns
+
+| Pattern | Use Case |
+|---|---|
+| `HttpCalloutMock` | Mock HTTP callouts in test context |
+| `System.StubProvider` | Mock arbitrary interfaces without HTTP |
+| `Test.setMock()` | Register the mock before the code under test runs |
+
+## RunRelevantTests (Spring '26, API v66.0+)
+
+Smart test-selection mode that runs only tests statistically linked to changed Apex classes. Pair with `@testFor` for explicit mapping. Falls back to `RunLocalTests` if `sourceApiVersion` < 66.0.
+
+## Anti-Patterns
+
+| Anti-Pattern | Problem | Fix |
+|---|---|---|
+| No assertions | Test always passes | Every test needs meaningful assertions |
+| `SeeAllData=true` | Brittle, fails on sandbox refresh | Create data in test |
+| One method testing 10 scenarios | Masks which scenario fails | One scenario per test method |
+| Hardcoded IDs | Fails in other orgs | Query or create records |
+| Missing `@testFor` | RunRelevantTests may skip test | Add `@testFor(ClassName)` |
+| No bulk test (200 records) | Governor limit violations hidden | Test with 200 records |

package/skills/_reference/TRIGGER_PATTERNS.md

@@ -0,0 +1,114 @@
+# Trigger Patterns -- Reference
+
+> Source: <https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm>
+> Source: <https://github.com/kevinohara80/sfdc-trigger-framework>
+> Source: <https://github.com/apex-enterprise-patterns/fflib-apex-common>
+> Last verified: API v66.0, Spring '26 (2026-03-28)
+
+## Order of Execution (Record Save)
+
+| Step | Phase |
+|------|-------|
+| 1 | Load original record from DB (or init new) |
+| 2 | Overwrite field values from request |
+| 3 | System validation (layout rules, field types, max length) |
+| 4 | Before-save record-triggered flows |
+| 5 | **Before triggers** execute |
+| 6 | Custom validation rules |
+| 7 | Duplicate rules |
+| 8 | Record saved to DB (not committed) |
+| 9 | **After triggers** execute |
+| 10 | Assignment rules |
+| 11 | Auto-response rules |
+| 12 | Workflow rules evaluate; field updates execute |
+| 13 | If workflow field update fired: re-runs before/after update triggers **once more** (custom validation skipped) |
+| 14 | Escalation rules |
+| 15 | After-save record-triggered flows |
+| 16 | Entitlement rules |
+| 17 | Roll-up summary fields on parent; parent goes through own save cycle |
+| 18 | Criteria-based sharing recalculated |
+| 19 | DML committed; post-commit logic (async jobs, emails, platform events) |
+
+Multiple triggers on the same object + event have **no guaranteed execution order**.
+
+## Trigger Context Variables
+
+| Variable | Type | Available |
+|----------|------|-----------|
+| `Trigger.isExecuting` | `Boolean` | All contexts |
+| `Trigger.isBefore` | `Boolean` | All contexts |
+| `Trigger.isAfter` | `Boolean` | All contexts |
+| `Trigger.isInsert` | `Boolean` | All contexts |
+| `Trigger.isUpdate` | `Boolean` | All contexts |
+| `Trigger.isDelete` | `Boolean` | All contexts |
+| `Trigger.isUndelete` | `Boolean` | All contexts |
+| `Trigger.new` | `List<sObject>` | insert, update, undelete |
+| `Trigger.old` | `List<sObject>` | update, delete |
+| `Trigger.newMap` | `Map<Id, sObject>` | after insert, before/after update, after undelete |
+| `Trigger.oldMap` | `Map<Id, sObject>` | update, delete |
+| `Trigger.operationType` | `System.TriggerOperation` | All contexts |
+| `Trigger.size` | `Integer` | All contexts |
+
+`Trigger.new` is mutable only in **before** triggers. `Trigger.old` is always read-only.
+
+## Framework Comparison
+
+| Aspect | Kevin O'Hara TriggerHandler | FFLIB Domain Layer (fflib_SObjectDomain) |
+|--------|----------------------------|------------------------------------------|
+| **Complexity** | Low -- single base class | High -- domain + selector + UoW |
+| **Trigger body** | `new Handler().run();` | `fflib_SObjectDomain.triggerHandler(Domain.class);` |
+| **Handler methods** | `beforeInsert()`, `afterInsert()`, `beforeUpdate()`, `afterUpdate()`, `beforeDelete()`, `afterDelete()`, `afterUndelete()` | `onBeforeInsert()`, `onAfterInsert()`, `onBeforeUpdate()`, `onAfterUpdate()`, `onBeforeDelete()`, `onAfterDelete()`, `onAfterUndelete()`, plus `onApplyDefaults()`, `onValidate()` |
+| **Bypass** | `TriggerHandler.bypass('HandlerName')` / `.clearBypass()` / `.clearAllBypasses()` | `fflib_SObjectDomain.getTriggerEvent(Type).disableAll()` |
+| **Recursion guard** | `setMaxLoopCount(n)` -- throws exception on exceed | Manual via static flags or `fflib_SObjectDomain` configuration |
+| **Testability** | Standard Apex DML | Supports DI/mocking via Application factory |
+| **Best for** | Small-to-medium orgs, straightforward logic | Enterprise orgs, complex multi-object transactions |
+
+## One-Trigger-Per-Object Pattern
+
+Every sObject gets exactly **one** trigger that delegates to a handler class.
+
+```apex
+trigger AccountTrigger on Account (
+    before insert, before update, before delete,
+    after insert, after update, after delete, after undelete
+) {
+    new AccountTriggerHandler().run();
+}
+```
+
+## Recursion Prevention Patterns
+
+| Pattern | Mechanism | Trade-off |
+|---------|-----------|-----------|
+| Static `Boolean` flag | `if (hasRun) return; hasRun = true;` | Blocks all re-entry including legitimate workflow re-fire |
+| Static `Set<Id>` processed | Skip IDs already in set | Allows first pass per record; handles partial batches correctly |
+| `setMaxLoopCount(n)` | TriggerHandler throws exception after n invocations | Configurable; exception must be handled or allowed to surface |
+| Static counter | Increment on entry, check threshold | Flexible but manual |
+
+Recommended: **`Set<Id>`-based** for most cases -- prevents true recursion while allowing workflow-triggered re-entry for records not yet processed.
+
+## Bypass Mechanisms
+
+```apex
+// Kevin O'Hara pattern
+TriggerHandler.bypass('AccountTriggerHandler');
+update accounts;                                  // handler skipped
+TriggerHandler.clearBypass('AccountTriggerHandler');
+
+// Custom Metadata bypass (org-configurable, no deploy)
+Trigger_Setting__mdt setting = Trigger_Setting__mdt.getInstance('Account');
+if (setting != null && setting.Is_Active__c == false) return;
+
+// Hierarchy Custom Setting bypass (per-user/profile)
+Trigger_Config__c config = Trigger_Config__c.getInstance();
+if (config != null && config.Disable_Account_Trigger__c) return;
+```
+
+## Key Rules
+
+- Triggers fire on DML, not on formula/roll-up recalculation.
+- Bulk triggers receive up to **200 records per batch** (`Trigger.size` max per chunk in Data Loader = 200).
+- `addError()` on `Trigger.new` records prevents save (before triggers) or rolls back (after triggers).
+- Callouts in triggers require `@future(callout=true)` or `Queueable` -- direct callouts are blocked.
+- `before delete` and `after delete` do not fire on `merge` for the losing records (they get delete triggers).
+- Undelete triggers: only `after undelete` exists; there is no `before undelete`.

package/skills/_reference/VISUALFORCE_PATTERNS.md

@@ -0,0 +1,121 @@
+<!-- Source: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_intro.htm -->
+<!-- Last verified: API v66.0 — 2026-03-29 -->
+<!-- WARNING: Web fetch of canonical URL failed (LWR client-side rendering). Facts below extracted from sf-visualforce-development skill. -->
+
+# Visualforce Patterns — Reference
+
+## Page Structure
+
+| Attribute | Purpose | Notes |
+|-----------|---------|-------|
+| `standardController` | Binds to standard SObject controller | Mutually exclusive with `controller` |
+| `controller` | Custom Apex controller class | Mutually exclusive with `standardController` |
+| `extensions` | Comma-separated controller extensions | Works with either controller type |
+| `renderAs` | Output format (`"pdf"` for PDF generation) | LWC cannot do this natively |
+| `lightningStylesheets` | Apply SLDS styling | Use for Lightning-compatible look |
+| `docType` | HTML doctype | Use `"html-5.0"` for modern pages |
+| `sidebar` | Show/hide Classic sidebar | Boolean |
+| `showHeader` | Show/hide Classic header | Boolean |
+| `applyBodyTag` | Generate `<body>` tag | Set `false` for full HTML control |
+
+## Controller Types
+
+| Type | Class Pattern | Constructor Signature | Use Case |
+|------|--------------|----------------------|----------|
+| Standard Controller | Built-in (no Apex) | N/A | Single-record CRUD without custom logic |
+| Standard List Controller | Built-in (`recordSetVar`) | N/A | List views with pagination (`hasNext`, `hasPrevious`) |
+| Custom Controller | `public with sharing class Ctrl` | No-arg: `public Ctrl()` | Full control over logic, data, navigation |
+| Controller Extension | `public with sharing class Ext` | `public Ext(ApexPages.StandardController sc)` | Add functionality to standard/custom controllers |
+
+## ViewState
+
+| Fact | Value |
+|------|-------|
+| Maximum ViewState size | **170 KB** (runtime error if exceeded) |
+| Storage mechanism | Hidden, encrypted form field |
+| Survives across | Postbacks (form submissions) |
+
+### What Counts Toward ViewState
+
+- All non-transient controller/extension instance variables
+- Component tree state
+- Expressions evaluated in the page
+
+### ViewState Reduction Strategies
+
+| Strategy | Impact |
+|----------|--------|
+| `transient` keyword on large/recomputable variables | High |
+| `apex:outputPanel` + `reRender` (partial refresh) | Medium |
+| Paginate large data sets (store only current page) | High |
+| JavaScript Remoting instead of action methods (stateless) | High |
+| Move read-only data to `<apex:repeat>` outside `<apex:form>` | Medium |
+| Store IDs only, re-query on postback | Medium |
+
+## Encoding Functions (XSS Prevention)
+
+| Function | Context | Example |
+|----------|---------|---------|
+| `HTMLENCODE()` | HTML attributes, raw HTML | `<div title="{!HTMLENCODE(val)}">` |
+| `JSENCODE()` | JavaScript strings in `<script>` blocks | `var x = '{!JSENCODE(val)}';` |
+| `URLENCODE()` | URL parameters | `?q={!URLENCODE(val)}` |
+| `JSINHTMLENCODE()` | JS inside HTML event handlers only | `onclick="fn('{!JSINHTMLENCODE(val)}')"` |
+
+## Security Patterns
+
+| Threat | Prevention |
+|--------|-----------|
+| XSS | Auto-escaped by `apex:outputText`, `apex:outputField`; never use `escape="false"` with user data |
+| CSRF | Use `<apex:form>` (auto-includes CSRF token); never raw `<form>` tags |
+| SOQL Injection | Use bind variables (`:term`) or `String.escapeSingleQuotes()`; prefer `Database.queryWithBinds()` |
+| CRUD/FLS bypass | Controllers run in system mode; use `WITH USER_MODE` in SOQL, `AccessLevel.USER_MODE` in DML |
+| Rich text XSS | Use `apex:outputField` for rich text fields; `String.stripHtmlTags()` to strip all HTML |
+
+## Key Components
+
+| Component | Purpose |
+|-----------|---------|
+| `apex:page` | Page container (defines controller, attributes) |
+| `apex:form` | Form with CSRF token |
+| `apex:pageBlock` / `apex:pageBlockSection` | Structured layout blocks |
+| `apex:pageBlockTable` | Data table bound to collection |
+| `apex:commandButton` / `apex:commandLink` | Server-side action triggers |
+| `apex:inputField` / `apex:outputField` | CRUD/FLS-aware field input/output |
+| `apex:actionFunction` | Call controller from JavaScript |
+| `apex:actionSupport` | Fire action on DOM event |
+| `apex:actionPoller` | Periodic server poll (interval in seconds) |
+| `apex:actionStatus` | Loading indicator |
+| `apex:outputPanel` | Rerenderable container |
+| `apex:repeat` | Non-table iteration |
+| `apex:includeLightning` | Enables Lightning Out (embed LWC in VF) |
+| `apex:pageMessages` | Display ApexPages.addMessage feedback |
+| `apex:slds` | Include SLDS stylesheets |
+
+## JavaScript Remoting
+
+| Fact | Value |
+|------|-------|
+| Annotation | `@RemoteAction` (must be `public static`) |
+| Invocation | `Visualforce.remoting.Manager.invokeAction()` |
+| Reference syntax | `{!$RemoteAction.ClassName.methodName}` (namespace-safe) |
+| ViewState impact | None (fully stateless) |
+| `escape: true` | Auto-escapes HTML in response (prevents XSS) |
+| `timeout` | Configurable in ms (e.g., `30000` for 30s) |
+
+## Migration Decision: Keep VF vs Migrate to LWC
+
+| Keep Visualforce | Migrate to LWC |
+|-----------------|----------------|
+| PDF generation (`renderAs="pdf"`) | High-traffic pages needing performance |
+| Email templates (VF/HTML) | Standard controller overrides |
+| Complex server-state wizards | New feature development (always LWC) |
+| | Pages using Apex controller only (easy migration) |
+
+## Lightning Out (Embed LWC in VF)
+
+| Step | Detail |
+|------|--------|
+| 1 | Add `<apex:includeLightning />` to VF page |
+| 2 | Create Aura app extending `ltng:outApp` with `<aura:dependency>` |
+| 3 | Call `$Lightning.use("c:appName", callback)` |
+| 4 | Call `$Lightning.createComponent("c:lwcName", attrs, containerId)` |

package/skills/aside/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: aside
+description: >-
+  Use when you need a quick Salesforce answer mid-task. Answer a side question about Apex, org config,
+  or metadata without losing context, then resume work automatically.
+origin: SCC
+user-invocable: true
+---
+
+# Aside — Quick Side Question Without Losing Context
+
+Ask a question mid-task and get an immediate, focused answer — then continue right where you left off. The current task, files, and context are never modified.
+
+## When to Use
+
+- You're curious about something while Claude is working and don't want to lose momentum
+- You need a quick explanation of code Claude is currently editing
+- You want a second opinion or clarification on a decision without derailing the task
+- You need to understand an error, concept, or pattern before Claude proceeds
+- You want to ask something unrelated to the current task without starting a new session
+
+## Usage
+
+```
+/aside <your question>
+/aside what does this function actually return?
+/aside is this pattern thread-safe?
+/aside why are we using X instead of Y here?
+/aside what's the difference between foo() and bar()?
+/aside should we be worried about the SOQL in a loop we just added?
+```
+
+## Process
+
+### Step 1: Freeze the current task state
+
+Before answering anything, mentally note:
+
+- What is the active task? (what file, feature, or problem was being worked on)
+- What step was in progress at the moment the aside was invoked?
+- What was about to happen next?
+
+Do NOT touch, edit, create, or delete any files during the aside.
+
+### Step 2: Answer the question directly
+
+Answer the question in the most concise form that is still complete and useful.
+
+- Lead with the answer, not the reasoning
+- Keep it short — if a full explanation is needed, offer to go deeper after the task
+- If the question is about the current file or code being worked on, reference it precisely (file path and line number if relevant)
+- If answering requires reading a file, read it — but read only, never write
+
+Format the response as:
+
+```
+ASIDE: [restate the question briefly]
+
+[Your answer here]
+
+— Back to task: [one-line description of what was being done]
+```
+
+### Step 3: Resume the main task
+
+After delivering the answer, immediately continue the active task from the exact point it was paused. Do not ask for permission to resume unless the aside answer revealed a blocker or a reason to reconsider the current approach.
+
+---
+
+## Edge Cases
+
+**No question provided (aside invoked with nothing after it):**
+Respond:
+
+```
+ASIDE: no question provided
+
+What would you like to know? (ask your question and I'll answer without losing the current task context)
+
+— Back to task: [one-line description of what was being done]
+```
+
+**Question reveals a potential problem with the current task:**
+Flag it clearly before resuming:
+
+```
+ASIDE: [answer]
+
+Warning: This answer suggests [issue] with the current approach. Want to address this before continuing, or proceed as planned?
+```
+
+Wait for the user's decision before resuming.
+
+**Question is actually a task redirect (not a side question):**
+If the question implies changing what is being built, clarify:
+
+```
+ASIDE: That sounds like a direction change, not just a side question.
+Do you want to:
+  (a) Answer this as information only and keep the current plan
+  (b) Pause the current task and change approach
+```
+
+Wait for the user's answer.
+
+**No active task (nothing in progress when aside is invoked):**
+Still use the standard wrapper:
+
+```
+ASIDE: [restate the question briefly]
+
+[Your answer here]
+
+— Back to task: no active task to resume
+```
+
+**Multiple aside questions in a row:**
+Answer each one in sequence. After the last answer, resume the main task.

package/skills/checkpoint/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: checkpoint
+description: >-
+  Use when saving Salesforce development progress. Create a named checkpoint via git stash before risky
+  Apex deploys or org changes for easy recovery.
+origin: SCC
+user-invocable: true
+disable-model-invocation: true
+---
+
+# Checkpoint — Named Progress Snapshots
+
+Save current progress as a named checkpoint for easy recovery.
+
+## When to Use
+
+- When you want to save work-in-progress before attempting a risky change
+- When starting a refactoring pass and need a safe rollback point
+- When switching between tasks and want to preserve current state
+- When you need to snapshot progress at key milestones during a long session
+- When collaborating and want to share a recoverable state with another agent or session
+
+## Usage
+
+```text
+checkpoint [name]
+```
+
+## Workflow
+
+1. **Create checkpoint** — `git stash push --include-untracked -m "checkpoint: <name> [<timestamp>]"`
+2. **Log metadata** — Append to `.claude/checkpoints.log`:
+   - Timestamp
+   - Checkpoint name
+   - Files changed (count)
+   - Current branch
+3. **Verify** — Confirm working tree is clean after stash
+
+## Operations
+
+- `checkpoint save <name>` — Create new checkpoint
+- `checkpoint list` — Show all checkpoints from log
+- `checkpoint restore <name>` — Apply the named stash (`git stash apply`; keeps the stash entry safe). Find the stash reference via `git stash list | grep "<name>"`, then `git stash apply stash@{N}`. After verifying the restore, drop with `git stash drop stash@{N}`.
+- `checkpoint verify` — Verify current state matches last checkpoint
+
+## Examples
+
+```
+checkpoint save before-trigger-refactor
+checkpoint list
+checkpoint restore before-trigger-refactor
+checkpoint verify
+```

package/skills/configure-scc/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: configure-scc
+description: >-
+  Use when setting up SCC for Salesforce Apex and LWC development. Interactive wizard to install
+  profiles, modules, and customize the harness for your org.
+origin: SCC
+user-invocable: true
+---
+
+# Configure SCC
+
+Interactive guide for installing and configuring Salesforce Claude Code.
+
+## When to Use
+
+- When installing SCC for the first time on a Salesforce project
+- When adding new modules or profiles to an existing SCC installation
+- When customizing hook behavior or profiles for your team's workflow
+- When troubleshooting SCC configuration or missing components
+- When setting up SCC for different team members or CI/CD environments
+
+## Installation
+
+### Quick Install
+
+```bash
+# Install globally
+npm install -g scc-universal
+
+# Install with a profile
+npx scc install all      # Everything (all agents, skills, rules)
+npx scc install apex     # Apex-focused development
+npx scc install lwc      # LWC-focused development
+```
+
+### Profile Details
+
+| Profile | Includes |
+|---------|----------|
+| `apex` | Common rules + Apex rules, agents, skills |
+| `lwc` | Common rules + LWC rules, agents, skills |
+| `full` | All agents, skills, rules |
+
+### Diagnostics
+
+```bash
+npx scc doctor    # Check for missing/drifted files
+npx scc status    # View installed components
+npx scc repair    # Restore drifted files
+npx scc uninstall # Remove SCC-managed files
+```
+
+## Hook Configuration
+
+### Profiles
+
+```bash
+# Set hook profile (controls which hooks run)
+export SCC_HOOK_PROFILE=minimal    # Session start + stop only
+export SCC_HOOK_PROFILE=standard   # Default — includes quality checks
+export SCC_HOOK_PROFILE=strict     # All hooks including auto-format
+```
+
+### Disable Specific Hooks
+
+```bash
+export SCC_DISABLED_HOOKS=governor-check,cost-tracker
+```
+
+## Package Manager
+
+SCC auto-detects your package manager. Override with:
+
+```bash
+export CLAUDE_PACKAGE_MANAGER=npm  # or pnpm, yarn, bun
+```
+
+## Environment-Specific Configuration
+
+### Sandbox / Scratch Org Development
+
+```bash
+# Set default target org for SF CLI commands
+sf config set target-org=my-scratch-org
+
+# Scratch org duration is set via --duration-days flag or scratch org definition file
+# sf org create scratch -f config/project-scratch-def.json --duration-days 7
+```
+
+### CI/CD Environments
+
+```bash
+# Minimal hooks for CI (fast, no interactive prompts)
+export SCC_HOOK_PROFILE=minimal
+
+# Disable all cost/session tracking in CI
+export SCC_DISABLED_HOOKS=cost-tracker,session-start,session-end,evaluate-session
+```
+
+### Team Setup
+
+Share SCC configuration across your team by adding to your project's `.env.example`:
+
+```bash
+# .env.example — copy to .env and customize
+SCC_HOOK_PROFILE=standard
+CLAUDE_PACKAGE_MANAGER=npm
+```
+
+## Troubleshooting
+
+### Common Issues
+
+| Problem | Cause | Fix |
+|---------|-------|-----|
+| `npx scc install` fails | Node.js < 20 | Upgrade: `nvm install 20` |
+| Hooks not firing | SCC not installed in project | Run `npx scc doctor` to check |
+| `Permission denied` on hooks | Script not executable | Run `npx scc repair` |
+| Skills not loading | Wrong install profile | Run `npx scc install all` |
+| `sf` command not found | SF CLI not installed | Install: `npm install -g @salesforce/cli` |
+| `sf` commands fail with errors | SF CLI version too old | Upgrade: `npm update -g @salesforce/cli` (SCC requires SF CLI v2.x / `sf` not `sfdx`) |
+| Hooks slow down session | Too many hooks enabled | Switch to `SCC_HOOK_PROFILE=minimal` |
+
+### Diagnostic Commands
+
+```bash
+# Full diagnostic report
+npx scc doctor
+
+# See exactly what's installed
+npx scc list-installed
+
+# Preview what WOULD be installed (dry run)
+npx scc plan apex
+
+# Check state store
+npx scc status
+
+# Reset everything and reinstall
+npx scc uninstall && npx scc install all
+```
+
+### Upgrading SCC
+
+```bash
+# Update to latest version
+npm install -g scc-universal@latest
+
+# Repair any drifted files after upgrade
+npx scc repair
+
+# Verify upgrade
+npx scc doctor
+```
+
+## Verification
+
+```bash
+npm test              # Run all validators
+npx scc doctor        # Check installation health
+sf --version          # Verify SF CLI is installed
+npx scc status        # Confirm installed components
+```