Merge pull request #24 from vratan-sf/experts-global-rule

Added global rules file for Experts skills
This commit is contained in:
vratan-sf 2026-03-11 18:34:02 +05:30 committed by GitHub
commit 59f7832fa0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -0,0 +1,69 @@
# Rule: Salesforce Metadata Generation
## Objective
Enforce: **skill load → API context → file generation** for all Salesforce metadata.
## Constraints
1. **Never write** without both: metadata type skill loaded AND `get_metadata_api_context` called for that type
2. **One type at a time** - complete full cycle before next type
3. **One type per API call** - no batching
4. **No cross-type content** in files
5. **Max one clarifying question** before starting
## Workflow
### 1. Detect Intent
- **Solution skill** (end-to-end capability like lex/react app) → Solution Path
- **Direct metadata** (specific fields/objects/pages) → Direct Path
### 2. Solution Path
1. Load solution skill, extract metadata type sequence
2. For each type, execute loop (a-e below)
3. Proceed to Step 3
### 2. Direct Path
1. Identify all needed types
2. For each type in dependency order, execute loop (a-e below)
3. Proceed to Step 3
### Loop (a-e) - Execute for Each Type
**a. Load Skill**
- Load metadata type skill once (not per record)
- If no skill exists, continue with API context only
**b. Call API Context**
- `get_metadata_api_context("TypeName")` - single type only
- Wait for response
**c. Pre-Write Gate**
- Before EVERY write: confirm API context called for this type
- If no → stop and call now
**d. Generate Files**
- Use skill constraints + API context
- Generate all records for this type now
**e. Checkpoint**
- Skill loaded? API context called? All files written?
- Only proceed to next type when all true
### 3. Deploy Verification
```bash
sf project deploy start --dry-run -d "<path>" --target-org <alias> --test-level NoTestRun --wait 10 --json
```
On failure: attempt to fix the errors and re-run, retrying up to a maximum of 5 times until it succeeds.
## Anti-Patterns
| Don't | Why | Do |
|-------|-----|-----|
| Write without API context | Missing schema validation | Call API context before first write |
| Reload skill per record | Wastes tokens | Load once per type |
| Skip API context for later types | No schema for those types | Call for EVERY type |
| Skip metadata skills | Missing platform constraints | Load skill for every type |
| Ask 3+ questions | Token waste | Max 1 question |
| Skip solution skill gates | Wrong artifacts | Follow all mandatory gates |
| Write despite missing checkpoint | Aware violation | Stop and complete missing step |
| Batch types in API call | Violates constraint #3 | One type per call |