sf-compound
/sf-compound
Zapisuje rozwiązany problem Salesforce w docs/solutions i odświeża nieaktualne wnioski z wcześniejszych prac.
- Autor
- divingsbysangam ↗
- Repozytorium
- salesforce-compound-engineering-plugin ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 21.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 21.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zapisuje rozwiązany problem Salesforce w docs/solutions i odświeża nieaktualne wnioski z wcześniejszych prac.
Wyzwalacze z opisu
Argumenty
/sf-compound [mode:refresh|doc-format] [scope; defaults to recent work]
Oryginalny opis (EN)
Capture a solved Salesforce problem in docs/solutions/ and refresh stale learnings. Use for 'compound this', 'document this fix', 'remember this', 'refresh learnings'.
Jak działa
- Modes
- Copy-paste-to-agent
- Interaction Method
- Goal
- The Compound Loop
- Step 1: Analyze Recent Work
- Step 2: Search Existing Knowledge First
- Step 3: Classify Learnings
- Step 4: Write Solution Documents
- Step 5: Update Plugin Resources
Podgląd SKILL.md
---
name: sf-compound
description: "Capture a solved Salesforce problem in docs/solutions/ and refresh stale learnings. Use for 'compound this', 'document this fix', 'remember this', 'refresh learnings'."
argument-hint: "[mode:refresh|doc-format] [scope; defaults to recent work]"
---
# /sf-compound
## Modes
First argument `mode:<name>` selects a mode; everything after it passes to that mode's guide. Load only the guide for the chosen mode.
| Mode | Use for | Guide |
|---|---|---|
| `(none)` | Write a solution doc from recent work | this file |
| `refresh` | Review stale docs/solutions entries against the codebase | `references/refresh/guide.md` |
| `doc-format` | Reference: solution doc format and schema | `references/doc-format/guide.md` |
> **Principles enforced:** 5 (taste and oversight), 7 (institutional memory). See `PRINCIPLES.md`.
> **Persona dispatch.** This skill dispatches personas as isolated subagents — see `../sf-work/references/dispatch/guide.md` for the mechanics (isolated subagents, same-response parallelism, same-file-conflict check). Any reviewer/researcher it invokes (e.g. `sf-learnings-researcher`) is a research persona referenced from `../sf-plan/references/personas/`.
## Copy-paste-to-agent
```
Capture learnings from completed Salesforce work into docs/solutions/ as YAML-frontmatter
solution documents validated against schema.yaml. Capture two kinds of learning explicitly:
(1) bug-fix learnings (symptom → root cause → resolution → prevention) and (2) aesthetic
or pattern learnings (the "works but gross" code we cleaned up, the abstraction we picked,
the convention we standardized on). Search existing solutions first — update existing
entries instead of duplicating. Update CLAUDE.md, agents, and skills only when the
learning generalizes beyond a single solution.
```
\<feature\_description>
\#$ARGUMENTS
\</feature\_description>
## Interaction Method
When asking the user a question, use the platform's blocking question tool: `AskUserQuestion` in Claude Code (call `ToolSearch` with `select:AskUserQuestion` first if its schema isn't loaded), `request_user_input` in Codex, `ask_user` in Gemini. Fall back to numbered options in chat only when no blocking tool exists in the harness or the call errors. Never silently skip the question.
Ask one question at a time. Prefer a concise single-select choice when natural options exist.
You are capturing learnings from completed work into the institutional knowledge system. Every solution documented makes the next iteration smarter.
## Goal
Analyze recent work and capture learnings: `$ARGUMENTS.scope`
If no scope specified, analyze recent commits and changes.
***
## The Compound Loop
```
Brainstorm (10%) → Plan (30%) → Work (20%) → Review (20%) → Compound (20%) → Repeat
│
└── YOU ARE HERE
```
***
## Step 1: Analyze Recent Work
Review what was built:
```bash
# Recent commits
git log --oneline -20
# Changed files
git diff HEAD~5 --name-only
# Recent solutions
ls docs/solutions/ -R
```
***
## Step 2: Search Existing Knowledge First
Before writing new entries, check what already exists:
* Task sf-learnings-researcher(work\_description)
Avoid duplicating existing documentation. Update existing entries if the new work adds context.
***
## Step 3: Classify Learnings
For each insight from the work, classify into a category:
| Category | Directory | Examples |
| --------------- | --------------------------------------- | ----------------------------------- |
| Governor Limits | `docs/solutions/governor-limit-issues/` | SOQL 101, DML 150, CPU timeout |
| Deployment | `docs/solutions/deployment-issues/` | Deploy failures, metadata conflicts |
| Test Failures | `docs/solutions/test-failures/` | Flaky tests, coverage gaps |
| Security | `docs/solutions/security-issues/` | CRUD/FLS, injection, sharing |
| Integration | `docs/solutions/integration-issues/` | Callout failures, auth issues |
| Flow | `docs/solutions/flow-issues/` | Flow errors, recursion, limits |
| LWC | `docs/solutions/lwc-issues/` | Rendering, wire, events |
| Data Model | `docs/solutions/data-model-issues/` | Relationships, indexes, skew |
| Best Practice | `docs/solutions/best-practices/` | Proven patterns, approaches |
| Pattern | `docs/solutions/patterns/` | Reusable design patterns |
***
## Step 4: Write Solution Documents
For each learning, create a solution document with YAML frontmatter:
```markdown
---
title: "{Short descriptive title}"
date: {YYYY-MM-DD}
category: {category from schema.yaml}
severity: {critical|high|medium|low}
tags: ["{tag1}", "{tag2}", "{tag3}"]
---
## Symptoms
{What went wrong or what was the challenge}
## Root Cause
{Why it happened — technical explanation}
## Resolution
{How it was fixed — specific code/config changes}
## Prevention
{How to avoid this in the future}
## Related Files
- {file_path}:{line_number}
```
Save to: `docs/solutions/{category}/{YYYY-MM-DD}-{slug}.md`
Validate frontmatter against `schema.yaml`.
***
## Step 5: Update Plugin Resources
Route updates via index files:
* Read `../sf-review/references/personas/` to identify the owning skill's persona files for new checks
* Read `skills/index.md` to identify skill files for new patterns
* Update only files relevant to the work classification
* Avoid cross-contamination across domains
### What to update:
* **Agent files**: Add new review checks discovered during the work
* **Skill files**: Add new patterns or gotchas
* **CLAUDE.md**: Update project context, conventions, tips
***
## Step 6: Compound Report
Save a report to `docs/solutions/` summarizing all changes.
***
## Output
```
Compound complete.
Knowledge updates:
- Solutions documented: {count} new entries in docs/solutions/
- Skills updated: {list of skills modified}
- Agents updated: {list of agents modified}
- CLAUDE.md: {entries added/updated}
Categories:
- {category}: {count} entries
The next iteration starts smarter.
Next: /sf-plan mode:brainstorm or /sf-plan for the next feature
```
Pliki w paczce (3)
- SKILL.md 6 KB
- references/doc-format/guide.md 7 KB
- references/refresh/guide.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie sf-compound.
Migawka bazy z 13.11.2026 · wersja paczki 1dafccd9846e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 85ce:compound-refresh
Odświeża nieaktualne notatki i wzorce w docs/solutions po refaktoryzacjach, migracjach i aktualizacjach zależności. - 90ce:compound-refresh
Aktualizuje nieaktualne notatki i wzorce w katalogu docs/solutions względem obecnego kodu po refaktoryzacji. - 95ce-compound-refresh
Odświeża nieaktualne notatki i wzorce w docs/solutions, sprawdzając je względem bieżącego kodu po refaktorach i migracjach. - 85ce:compound-refresh
Odświeża, łączy lub usuwa nieaktualne notatki w docs/solutions względem bieżącego kodu, po refaktorach i aktualizacjach. - 100ce-compound-refresh
Odświeża zapisane lekcje repozytorium względem bieżącej bazy kodu: audytuje nieaktualne, nakładające się, zastąpione lub zdryfowane wpisy. - 95compound
Dokumentuje niedawno rozwiązany problem, żeby wiedza zespołu rosła.