Add Salesforce Apex, Flow, LWC/Aura, and Visualforce development agents#1095
Conversation
There was a problem hiding this comment.
Pull request overview
Adds new Salesforce-focused custom agents to the repository and updates the agents documentation so they can be discovered and installed.
Changes:
- Added four new Salesforce development agents covering Apex/Triggers, Flow, Aura/LWC UI, and Visualforce.
- Updated
docs/README.agents.mdto list the new agents with install links.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/README.agents.md | Adds entries (descriptions + install links) for the new Salesforce agents. |
| agents/salesforce-apex-triggers.agent.md | New agent definition for Apex classes and trigger development guidelines. |
| agents/salesforce-flow.agent.md | New agent definition for Salesforce Flow automation guidelines. |
| agents/salesforce-aura-lwc.agent.md | New agent definition for Lightning UI (Aura + LWC) development guidelines. |
| agents/salesforce-visualforce.agent.md | New agent definition for Visualforce pages/controllers development guidelines. |
|
|
||
| - ❌ Adding new npm packages when existing packages provide the functionality | ||
| - ❌ Introducing new state management libraries (use what's already configured) | ||
| - ❌ Introducing new ORMs or database tools (use SQLAlchemy as established) |
There was a problem hiding this comment.
This bullet is incorrect for a Salesforce Apex agent: “Introducing new ORMs or database tools (use SQLAlchemy as established)” is Python-specific and unrelated to Salesforce development, and may confuse users. Suggest removing it or replacing it with a Salesforce-relevant restriction (e.g., avoid unmanaged custom persistence layers / prefer platform-native data access patterns) while keeping the intent of avoiding unnecessary new dependencies.
| - ❌ Introducing new ORMs or database tools (use SQLAlchemy as established) | |
| - ❌ Introducing unmanaged custom persistence layers or external ORM-style abstractions (use native SOQL/DML and existing data access patterns) |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
aaronpowell
left a comment
aaronpowell
left a comment
There was a problem hiding this comment.
Looks good - might be worth considering creating a plugin for these to easily setup a Salesforce agentic dev environment, but that can be another PR.
|
@all-contributors add @TemitayoAfolabi for agents |
|
I couldn't determine any contributions to add, did you specify any contributions? |
|
@all-contributors add @TemitayoAfolabi for agents |
|
I couldn't determine any contributions to add, did you specify any contributions? |
|
@all-contributors add @TemitayoAfolabi for code, review and tool |
|
I've put up a pull request to add @TemitayoAfolabi! 🎉 |
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.Description
This pull request introduces four new specialized Salesforce development agents and updates the agent documentation to include them. The new agents cover Apex & Triggers, Flow, Lightning UI (Aura & LWC), and Visualforce development, each with detailed operational guidelines and completion requirements to ensure best practices and code quality.
New Salesforce agent additions:
salesforce-apex-triggers.agent.mdfor Apex classes and triggers development, including strict requirements for code quality, completion, and use of existing tooling and patterns.salesforce-flow.agent.mdfor declarative Salesforce Flow automation, emphasizing clear requirements, mandatory completion, and verification steps.salesforce-aura-lwc.agent.mdfor Lightning Web Components and Aura UI development, with guidelines for component completeness, accessibility, and user consultation.salesforce-visualforce.agent.mdfor Visualforce pages and controllers, including operational standards and completion definitions.Documentation updates:
docs/README.agents.mdto list the new Salesforce agents, with descriptions and install links for each, ensuring visibility and easy access for users.Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.