Menú
Use before writing Lightning Web Components.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Merge the base branch into the current branch. Do the merge and resolve the safe parts first, then let a cheap signal decide how deep to look. Go past textual conflicts to semantic breaks, and past those to design consistency. When the base carries a refactor or redesign, bring the current branch into line with it (with the user's consent).
Provides Apex development workflow including static analysis and testing steps. Use before writing Apex classes or triggers
Access Salesforce Apex classes and schema objects. Use BEFORE writing Apex code to check what frameworks, utilities, or patterns are already available (e.g., trigger frameworks, selector patterns, service classes). Also use when you need to know object fields, System class methods, API signatures. Check this when asked to create triggers, services, or any new Apex to see if there's an existing framework to follow.
Gets Claude to think about what went well and badly in a session with an eye on future improvements or lessons for the user.
| name | salesforce-lwc |
| description | Use before writing Lightning Web Components. |
| allowed-tools | mcp__ide__getDiagnostics, Bash(npm run *), Bash(sf code-analyzer *), Bash(sf project deploy *), Bash(sf lightning generate *) |
Read project config — Get sourceApiVersion from sfdx-project.json for the component's -meta.xml file.
Write the component — Create the JS, HTML, and meta.xml files following code-guidance.md.
Check IDE diagnostics — Use mcp__ide__getDiagnostics on new files. Fix errors and warnings before proceeding.
Static analysis
sf code-analyzer run --target <path-to-component> --view table
Address violations before proceeding.
Write Jest tests (if needed) — See test-guidance.md for when tests are warranted.
Run tests locally (if applicable)
npm run test:unit -- --testPathPattern=<componentName>
Deploy
sf project deploy start --source-dir <path-to-component>
The task is complete when the component works in the org.