salesforce-apex

Estrellas7

Forks0

Actualizado22 de junio de 2026 a las 18:17

Provides Apex development workflow including static analysis and testing steps. Use before writing Apex classes or triggers

Instalación

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.

Ejecutar en Manus

Fuente

aquivalabs

aquivalabs/aidan-user-claude

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

name	salesforce-apex
description	Provides Apex development workflow including static analysis and testing steps. Use before writing Apex classes or triggers
allowed-tools	mcp__ide__getDiagnostics, Bash(sf project deploy ), Bash(sf apex run test )

Workflow

Read project config — Get sourceApiVersion from sfdx-project.json for all new -meta.xml files.
Write the Apex code
Check IDE diagnostics — Use mcp__ide__getDiagnostics on new files. Fix errors and warnings before proceeding.
Static analysis — Run sf code-analyzer on the new or changed .cls and .trigger files. Review its output and fix violations before proceeding.
Write tests — Create test classes following test-guidance.md.
Deploy code and tests Let source tracking which files to deploy
```
sf project deploy start
```

Run tests in org

sf apex run test --class-names <TestClassName> --result-format human --wait 10

The task is complete when tests pass in the org.

Más de este repositorio

mismo repositorio

merge-base

aquivalabs/aidan-user-claude

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).

2026-07-207

salesforce-illuminated-cloud-symbols

aquivalabs/aidan-user-claude

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.

2026-06-027

salesforce-lwc

aquivalabs/aidan-user-claude

Use before writing Lightning Web Components.

2026-06-027

claude-retrospective

aquivalabs/aidan-user-claude

Gets Claude to think about what went well and badly in a session with an eye on future improvements or lessons for the user.

2026-05-227

name	salesforce-apex
description	Provides Apex development workflow including static analysis and testing steps. Use before writing Apex classes or triggers
allowed-tools	mcp__ide__getDiagnostics, Bash(sf project deploy ), Bash(sf apex run test )

Workflow

Read project config — Get sourceApiVersion from sfdx-project.json for all new -meta.xml files.
Write the Apex code
Check IDE diagnostics — Use mcp__ide__getDiagnostics on new files. Fix errors and warnings before proceeding.
Static analysis — Run sf code-analyzer on the new or changed .cls and .trigger files. Review its output and fix violations before proceeding.
Write tests — Create test classes following test-guidance.md.
Deploy code and tests Let source tracking which files to deploy
```
sf project deploy start
```

Run tests in org

sf apex run test --class-names <TestClassName> --result-format human --wait 10

The task is complete when tests pass in the org.