fix: remove stale /skill-name invocations for pattern skills (#21)

Pattern skills are not user-invocable — they're consulted by agents
automatically. Replaced /sf-skill-name with sf-skill-name (backtick)
across examples, skills, and README. Rewrote Tips section to describe
natural agent triggering instead of slash commands.

Author: jiten-singh-shahi

.cursor/skills/prompt-optimizer/SKILL.md

@@ -93,13 +93,13 @@ Map intent + scope + tech stack (from Phase 0) to specific SCC components.
 
 | Intent | Invocable Skills | Skills | Agents |
 |--------|----------|--------|--------|
-| New Feature | /sf-tdd-workflow, /sf-apex-best-practices | sf-apex-best-practices, sf-apex-enterprise-patterns | sf-architect, sf-apex-agent, sf-review-agent |
-| Bug Fix | /sf-tdd-workflow, /sf-build-fix | sf-apex-testing, sf-debugging | sf-bugfix-agent, sf-apex-agent |
-| Refactor | /refactor-clean, /sf-apex-best-practices | sf-trigger-frameworks, sf-apex-enterprise-patterns | refactor-cleaner, sf-review-agent |
-| Testing | /sf-tdd-workflow, /sf-apex-testing, /sf-e2e-testing | sf-apex-testing, sf-tdd-workflow | sf-apex-agent |
-| Review | /sf-apex-best-practices, /sf-lwc-development, /sf-security | sf-security | sf-review-agent, sf-review-agent |
+| New Feature | sf-tdd-workflow, sf-apex-best-practices | sf-apex-best-practices, sf-apex-enterprise-patterns | sf-architect, sf-apex-agent, sf-review-agent |
+| Bug Fix | sf-tdd-workflow, sf-build-fix | sf-apex-testing, sf-debugging | sf-bugfix-agent, sf-apex-agent |
+| Refactor | /refactor-clean, sf-apex-best-practices | sf-trigger-frameworks, sf-apex-enterprise-patterns | refactor-cleaner, sf-review-agent |
+| Testing | sf-tdd-workflow, sf-apex-testing, sf-e2e-testing | sf-apex-testing, sf-tdd-workflow | sf-apex-agent |
+| Review | sf-apex-best-practices, sf-lwc-development, sf-security | sf-security | sf-review-agent, sf-review-agent |
 | Documentation | /update-docs | — | doc-updater, deep-researcher |
-| Infrastructure | /sf-deployment | sf-devops-ci-cd, sf-deployment | sf-architect |
+| Infrastructure | sf-deployment | sf-devops-ci-cd, sf-deployment | sf-architect |
 | Design (EPIC) | — | — | sf-architect, sf-architect |
 
 #### By Tech Stack
@@ -161,7 +161,7 @@ For tasks that exceed a single session, split into sequential prompts:
 
 - Prompt 1: Research + Plan (use search-first skill, then sf-architect agent)
 - Prompt 2-N: Implement one phase per prompt (each ends with sf-review-agent agent)
-- Final Prompt: Integration test + /sf-apex-best-practices across all phases
+- Final Prompt: Integration test + sf-apex-best-practices across all phases
 - Use /save-session and /resume-session to preserve context between sessions
 
 ---
@@ -188,7 +188,7 @@ If Phase 0 auto-detected the answer, state it instead of asking.
 
 | Type | Component | Purpose |
 |------|-----------|---------|
-| Command | /sf-tdd-workflow | TDD workflow for Apex |
+| Command | sf-tdd-workflow | TDD workflow for Apex |
 | Skill | sf-apex-best-practices | Apex coding standards |
 | Agent | sf-review-agent | Post-implementation review |
 | Model | Sonnet | Recommended for this scope |
@@ -206,20 +206,20 @@ The prompt must be self-contained and ready to copy-paste. Include:
 - Scope boundaries (what NOT to do)
 
 For items that reference blueprint, write: "Use the sf-architect agent to..."
-(not `/blueprint`, since sf-architect is an agent, not a command).
+(not `sf-architect agent`, since sf-architect is an agent, not a command).
 
 ### Section 4: Optimized Prompt — Quick Version
 
 A compact version for experienced SCC users. Vary by intent type:
 
 | Intent | Quick Pattern |
 |--------|--------------|
-| New Feature | `Use sf-architect agent for [feature]. /sf-tdd-workflow to implement. /sf-apex-best-practices. Use sf-review-agent agent.` |
-| Bug Fix | `/sf-tdd-workflow — write failing test for [bug]. Fix to green. Use sf-review-agent agent.` |
-| Refactor | `/refactor-clean [scope]. /sf-apex-best-practices. Use sf-review-agent agent.` |
+| New Feature | `Use sf-architect agent for [feature]. sf-tdd-workflow to implement. sf-apex-best-practices. Use sf-review-agent agent.` |
+| Bug Fix | `sf-tdd-workflow — write failing test for [bug]. Fix to green. Use sf-review-agent agent.` |
+| Refactor | `/refactor-clean [scope]. sf-apex-best-practices. Use sf-review-agent agent.` |
 | Research | `Use search-first skill for [topic]. Use sf-architect agent based on findings.` |
-| Testing | `/sf-tdd-workflow [class]. /sf-e2e-testing for critical flows. /sf-apex-testing.` |
-| Review | `/sf-apex-best-practices. Then use sf-review-agent agent.` |
+| Testing | `sf-tdd-workflow [class]. sf-e2e-testing for critical flows. sf-apex-testing.` |
+| Review | `sf-apex-best-practices. Then use sf-review-agent agent.` |
 | Docs | `/update-docs. Use deep-researcher agent.` |
 | EPIC | `Use sf-architect agent for "[objective]". Execute phases with sf-review-agent agent gates.` |
 
@@ -267,9 +267,9 @@ Technical requirements:
 
 Workflow:
 1. Use sf-architect agent to plan trigger handler structure and business logic
-2. /sf-tdd-workflow — write failing test class first (use @TestSetup and test data factory)
+2. sf-tdd-workflow — write failing test class first (use @TestSetup and test data factory)
 3. Implement AccountTrigger and AccountTriggerHandler
-4. /sf-apex-best-practices to review implementation
+4. sf-apex-best-practices to review implementation
 5. Use sf-review-agent agent to verify all tests pass and coverage reaches 75%+
 
 Security requirements:
@@ -279,7 +279,7 @@ Security requirements:
 Acceptance criteria:
 - Test coverage 85%+
 - Zero governor limit violations
-- Passes /sf-security review
+- Passes sf-security review
 ```
 
 ### Example 2: Moderate English Prompt
@@ -309,10 +309,10 @@ Requirements:
 
 Workflow:
 1. Use sf-architect agent for the endpoint structure, validation logic, and error response envelope
-2. /sf-tdd-workflow — write tests for success, validation failure, permission failure
+2. sf-tdd-workflow — write tests for success, validation failure, permission failure
 3. Implement AccountAPI class following existing REST patterns
-4. /sf-security — verify CRUD/FLS enforcement
-5. /sf-apex-best-practices
+4. sf-security — verify CRUD/FLS enforcement
+5. sf-apex-best-practices
 6. Use sf-review-agent agent — run full test suite, confirm no regressions
 
 Do not:
@@ -342,7 +342,7 @@ Before executing, answer these questions in the blueprint:
 The blueprint should produce phases like:
 - Phase 1: Audit all existing triggers and document business logic
 - Phase 2: Implement TriggerHandler base class and factory
-- Phase 3: Migrate highest-priority object triggers with /sf-tdd-workflow gates
+- Phase 3: Migrate highest-priority object triggers with sf-tdd-workflow gates
 - Phase 4: Migrate remaining triggers
 - Phase N: Remove legacy trigger code, run full regression
 

.cursor/skills/sf-quickstart/SKILL.md

@@ -102,7 +102,7 @@ Based on the project state, suggest 3-5 commands to start with:
 | Low test coverage | `sf-apex-testing` skill -- analyze gaps |
 | Deployment files present | `sf-deployment` skill -- pre-deployment check |
 | Security review needed | `sf-security` skill -- full security audit |
-| Build errors | `/sf-build-fix` -- fix build and deployment errors |
+| Build errors | `sf-build-fix` -- fix build and deployment errors |
 | Any project | `/sf-help` -- browse all available commands and skills |
 
 ### Step 5 — Verify SCC Installation

README.md

@@ -420,52 +420,21 @@ Control which hooks run via the `SCC_HOOK_PROFILE` environment variable:
 
 ## Tips and Best Practices
 
-### Salesforce-Specific Workflows
+### Typical Workflows
 
-**New Feature Development:**
+**New Feature:** Describe what you want to build — sf-architect activates automatically, designs the solution, and delegates to domain agents (sf-apex-agent, sf-lwc-agent, sf-flow-agent) with TDD.
 
-1. `/blueprint` - Plan the implementation (metadata types, governor limits)
-2. `/sf-tdd-workflow` - Write tests first, then implement
-3. `/sf-apex-best-practices` - Review your code
-4. `/sf-deployment` - Deploy to target org
+**Bug Fix:** Describe the error — sf-bugfix-agent activates, diagnoses root cause, applies minimal fix.
 
-**Code Review:**
-
-1. `/sf-apex-best-practices` - Full review of uncommitted changes
-2. `/sf-security` - Security-focused audit
-3. `/sf-governor-limits` - Check for governor limit issues
-
-**Performance Optimization:**
-
-1. `/sf-soql-optimization` - Fix expensive queries
-2. `/sf-governor-limits` - Find limit violations
-3. Use the `sf-review-agent` for deep analysis
-
-### Context Window Management
-
-- Keep MCP servers minimal (SF CLI MCP + 2-3 others)
-- Use specific prompts: "Review AccountTrigger.cls" not "review everything"
-- Use `/compact` when context gets large
-
-### Parallel Workflows
-
-- Use `/fork` for non-overlapping tasks
-- Use git worktrees for parallel scratch org work:
-
-```bash
-git worktree add ../feature-branch feature-branch
-cd ../feature-branch
-sf org create scratch --alias feature-scratch
-```
+**Code Review:** Ask to review before deploy — sf-review-agent runs a full quality gate (security, governor limits, test coverage, deploy readiness).
 
 ### Key Principles
 
 1. **Governor limits are king** — Every agent checks for limit violations
 2. **Test-first approach** — 75% is the SF minimum, aim for 85%+
-3. **Use the right agent** — Specialized agents give better results than generic prompts
+3. **Be specific** — "Review AccountTrigger.cls" not "review everything"
 4. **Hook profiles matter** — Start with `standard`, move to `strict` for CI
-5. **Context is precious** — Be specific in prompts, disable unused MCPs
-6. **Security baked in** — CRUD/FLS and sharing model from the start
+5. **Security baked in** — CRUD/FLS and sharing model from the start
 
 ---
 

examples/agentforce-action/README.md

@@ -221,7 +221,7 @@ Flow: Case Creation from Chat
 
 ## SCC Skills
 
-- `/sf-agentforce-development` -- scaffold and review Agentforce actions
-- `/sf-apex-best-practices` -- review the action class for best practices
-- `/sf-tdd-workflow` -- write tests first, then implement the action
-- `/sf-governor-limits` -- check governor limit compliance in bulk scenarios
+- `sf-agentforce-development` -- scaffold and review Agentforce actions
+- `sf-apex-best-practices` -- review the action class for best practices
+- `sf-tdd-workflow` -- write tests first, then implement the action
+- `sf-governor-limits` -- check governor limit compliance in bulk scenarios

examples/devops-pipeline/README.md

@@ -319,7 +319,7 @@ jobs:
 
 ## SCC Skills
 
-- `/sf-deployment` -- validate and deploy metadata to a target org
-- `/sf-devops-ci-cd` -- CI/CD pipeline patterns with scratch orgs
-- `/sf-build-fix` -- diagnose and fix deployment failures
-- `/sf-apex-testing` -- run Apex tests with coverage analysis
+- `sf-deployment` -- validate and deploy metadata to a target org
+- `sf-devops-ci-cd` -- CI/CD pipeline patterns with scratch orgs
+- `sf-build-fix` -- diagnose and fix deployment failures
+- `sf-apex-testing` -- run Apex tests with coverage analysis

examples/integration-pattern/README.md

@@ -410,7 +410,7 @@ private class PaymentGatewayService_Test {
 
 ## SCC Skills
 
-- `/sf-security` -- verify Named Credential usage and no hardcoded secrets
-- `/sf-apex-best-practices` -- review callout service code for best practices
-- `/sf-tdd-workflow` -- write tests first using mock classes
-- `/sf-governor-limits` -- check callout limits in async and batch contexts
+- `sf-security` -- verify Named Credential usage and no hardcoded secrets
+- `sf-apex-best-practices` -- review callout service code for best practices
+- `sf-tdd-workflow` -- write tests first using mock classes
+- `sf-governor-limits` -- check callout limits in async and batch contexts

examples/platform-events/README.md

@@ -486,7 +486,7 @@ private class OrderEventPublisher_Test {
 
 ## SCC Skills
 
-- `/sf-platform-events-cdc` -- review Platform Event and CDC implementations
-- `/sf-apex-best-practices` -- review publisher and subscriber Apex code
-- `/sf-lwc-development` -- review the empApi subscription component
-- `/sf-governor-limits` -- check event publish limits and bulk compliance
+- `sf-platform-events-cdc` -- review Platform Event and CDC implementations
+- `sf-apex-best-practices` -- review publisher and subscriber Apex code
+- `sf-lwc-development` -- review the empApi subscription component
+- `sf-governor-limits` -- check event publish limits and bulk compliance

examples/security-audit/README.md

@@ -239,6 +239,6 @@ sf scanner run --target "force-app/" \
 
 ## SCC Skills
 
-- `/sf-security` -- run a comprehensive security audit on your codebase
-- `/sf-apex-best-practices` -- review Apex code including security best practices
-- `/sf-governor-limits` -- check for governor limit issues (overlaps with security for SOQL)
+- `sf-security` -- run a comprehensive security audit on your codebase
+- `sf-apex-best-practices` -- review Apex code including security best practices
+- `sf-governor-limits` -- check for governor limit issues (overlaps with security for SOQL)

examples/visualforce-migration/README.md

@@ -308,7 +308,7 @@ public with sharing class AccountEditorLwcController {
 
 ## SCC Skills
 
-- `/sf-visualforce-development` -- audit a Visualforce page for migration readiness
-- `/sf-lwc-development` -- review the migrated LWC component for best practices
-- `/sf-apex-best-practices` -- review the simplified Apex controller
-- `/sf-security` -- verify security enforcement in the new component
+- `sf-visualforce-development` -- audit a Visualforce page for migration readiness
+- `sf-lwc-development` -- review the migrated LWC component for best practices
+- `sf-apex-best-practices` -- review the simplified Apex controller
+- `sf-security` -- verify security enforcement in the new component

skills/prompt-optimizer/SKILL.md

@@ -96,13 +96,13 @@ Map intent + scope + tech stack (from Phase 0) to specific SCC components.
 
 | Intent | Invocable Skills | Skills | Agents |
 |--------|----------|--------|--------|
-| New Feature | /sf-tdd-workflow, /sf-apex-best-practices | sf-apex-best-practices, sf-apex-enterprise-patterns | sf-architect, sf-apex-agent, sf-review-agent |
-| Bug Fix | /sf-tdd-workflow, /sf-build-fix | sf-apex-testing, sf-debugging | sf-bugfix-agent, sf-apex-agent |
-| Refactor | /refactor-clean, /sf-apex-best-practices | sf-trigger-frameworks, sf-apex-enterprise-patterns | refactor-cleaner, sf-review-agent |
-| Testing | /sf-tdd-workflow, /sf-apex-testing, /sf-e2e-testing | sf-apex-testing, sf-tdd-workflow | sf-apex-agent |
-| Review | /sf-apex-best-practices, /sf-lwc-development, /sf-security | sf-security | sf-review-agent, sf-review-agent |
+| New Feature | sf-tdd-workflow, sf-apex-best-practices | sf-apex-best-practices, sf-apex-enterprise-patterns | sf-architect, sf-apex-agent, sf-review-agent |
+| Bug Fix | sf-tdd-workflow, sf-build-fix | sf-apex-testing, sf-debugging | sf-bugfix-agent, sf-apex-agent |
+| Refactor | /refactor-clean, sf-apex-best-practices | sf-trigger-frameworks, sf-apex-enterprise-patterns | refactor-cleaner, sf-review-agent |
+| Testing | sf-tdd-workflow, sf-apex-testing, sf-e2e-testing | sf-apex-testing, sf-tdd-workflow | sf-apex-agent |
+| Review | sf-apex-best-practices, sf-lwc-development, sf-security | sf-security | sf-review-agent, sf-review-agent |
 | Documentation | /update-docs | — | doc-updater, deep-researcher |
-| Infrastructure | /sf-deployment | sf-devops-ci-cd, sf-deployment | sf-architect |
+| Infrastructure | sf-deployment | sf-devops-ci-cd, sf-deployment | sf-architect |
 | Design (EPIC) | — | — | sf-architect, sf-architect |
 
 #### By Tech Stack
@@ -164,7 +164,7 @@ For tasks that exceed a single session, split into sequential prompts:
 
 - Prompt 1: Research + Plan (use search-first skill, then sf-architect agent)
 - Prompt 2-N: Implement one phase per prompt (each ends with sf-review-agent agent)
-- Final Prompt: Integration test + /sf-apex-best-practices across all phases
+- Final Prompt: Integration test + sf-apex-best-practices across all phases
 - Use /save-session and /resume-session to preserve context between sessions
 
 ---
@@ -191,7 +191,7 @@ If Phase 0 auto-detected the answer, state it instead of asking.
 
 | Type | Component | Purpose |
 |------|-----------|---------|
-| Command | /sf-tdd-workflow | TDD workflow for Apex |
+| Command | sf-tdd-workflow | TDD workflow for Apex |
 | Skill | sf-apex-best-practices | Apex coding standards |
 | Agent | sf-review-agent | Post-implementation review |
 | Model | Sonnet | Recommended for this scope |
@@ -209,20 +209,20 @@ The prompt must be self-contained and ready to copy-paste. Include:
 - Scope boundaries (what NOT to do)
 
 For items that reference blueprint, write: "Use the sf-architect agent to..."
-(not `/blueprint`, since sf-architect is an agent, not a command).
+(not `sf-architect agent`, since sf-architect is an agent, not a command).
 
 ### Section 4: Optimized Prompt — Quick Version
 
 A compact version for experienced SCC users. Vary by intent type:
 
 | Intent | Quick Pattern |
 |--------|--------------|
-| New Feature | `Use sf-architect agent for [feature]. /sf-tdd-workflow to implement. /sf-apex-best-practices. Use sf-review-agent agent.` |
-| Bug Fix | `/sf-tdd-workflow — write failing test for [bug]. Fix to green. Use sf-review-agent agent.` |
-| Refactor | `/refactor-clean [scope]. /sf-apex-best-practices. Use sf-review-agent agent.` |
+| New Feature | `Use sf-architect agent for [feature]. sf-tdd-workflow to implement. sf-apex-best-practices. Use sf-review-agent agent.` |
+| Bug Fix | `sf-tdd-workflow — write failing test for [bug]. Fix to green. Use sf-review-agent agent.` |
+| Refactor | `/refactor-clean [scope]. sf-apex-best-practices. Use sf-review-agent agent.` |
 | Research | `Use search-first skill for [topic]. Use sf-architect agent based on findings.` |
-| Testing | `/sf-tdd-workflow [class]. /sf-e2e-testing for critical flows. /sf-apex-testing.` |
-| Review | `/sf-apex-best-practices. Then use sf-review-agent agent.` |
+| Testing | `sf-tdd-workflow [class]. sf-e2e-testing for critical flows. sf-apex-testing.` |
+| Review | `sf-apex-best-practices. Then use sf-review-agent agent.` |
 | Docs | `/update-docs. Use deep-researcher agent.` |
 | EPIC | `Use sf-architect agent for "[objective]". Execute phases with sf-review-agent agent gates.` |
 
@@ -270,9 +270,9 @@ Technical requirements:
 
 Workflow:
 1. Use sf-architect agent to plan trigger handler structure and business logic
-2. /sf-tdd-workflow — write failing test class first (use @TestSetup and test data factory)
+2. sf-tdd-workflow — write failing test class first (use @TestSetup and test data factory)
 3. Implement AccountTrigger and AccountTriggerHandler
-4. /sf-apex-best-practices to review implementation
+4. sf-apex-best-practices to review implementation
 5. Use sf-review-agent agent to verify all tests pass and coverage reaches 75%+
 
 Security requirements:
@@ -282,7 +282,7 @@ Security requirements:
 Acceptance criteria:
 - Test coverage 85%+
 - Zero governor limit violations
-- Passes /sf-security review
+- Passes sf-security review
 ```
 
 ### Example 2: Moderate English Prompt
@@ -312,10 +312,10 @@ Requirements:
 
 Workflow:
 1. Use sf-architect agent for the endpoint structure, validation logic, and error response envelope
-2. /sf-tdd-workflow — write tests for success, validation failure, permission failure
+2. sf-tdd-workflow — write tests for success, validation failure, permission failure
 3. Implement AccountAPI class following existing REST patterns
-4. /sf-security — verify CRUD/FLS enforcement
-5. /sf-apex-best-practices
+4. sf-security — verify CRUD/FLS enforcement
+5. sf-apex-best-practices
 6. Use sf-review-agent agent — run full test suite, confirm no regressions
 
 Do not:
@@ -345,7 +345,7 @@ Before executing, answer these questions in the blueprint:
 The blueprint should produce phases like:
 - Phase 1: Audit all existing triggers and document business logic
 - Phase 2: Implement TriggerHandler base class and factory
-- Phase 3: Migrate highest-priority object triggers with /sf-tdd-workflow gates
+- Phase 3: Migrate highest-priority object triggers with sf-tdd-workflow gates
 - Phase 4: Migrate remaining triggers
 - Phase N: Remove legacy trigger code, run full regression