@W-21723468 expert rules and lightning app skills update#99
@W-21723468 expert rules and lightning app skills update#99ysachdeva-sfdc wants to merge 0 commit intoforcedotcom:mainfrom
Conversation
ysachdeva-sfdc
changed the title
| - Only proceed to the next type when all are true. | ||
| ## Required Criteria (Lightning App Runs) | ||
|
|
||
| 1. Generate ALL of these metadata types in order: `CustomObject` -> `CustomField` -> `CustomTab` -> `FlexiPage` -> `CustomApplication` -> `PermissionSet`. |
There was a problem hiding this comment.
We can not mention this in the global rule file, LEX App skill takes care of dependency.
There was a problem hiding this comment.
Since this was not being followed, had to explicitly state this.
| 2. Call the per-type skill before first write for that type. | ||
| 3. Call `salesforce-api-context` for every metadata type before write (record tool evidence). | ||
| 4. Generate `FlexiPage` using CLI-driven generation from the loaded FlexiPage skill. | ||
| 5. Generate `Flow` through metadata experts MCP flow tooling (with skill + API context gates). |
There was a problem hiding this comment.
Why are we mentioning this explicitly?
There was a problem hiding this comment.
these were the errors that were coming across multiple runs
|
|
||
| After completing generation for a metadata type, you MUST advance to the next type in the sequence. Never loop back to a previously completed type. The required execution order is: | ||
|
|
||
| 1. `CustomObject` — load `generating-custom-object` skill, call `get_metadata_type_fields("CustomObject")`, generate, checkpoint |
There was a problem hiding this comment.
we can not hard code all the metadataType like this in the Global rule file.
There was a problem hiding this comment.
This is ensuring that calls are being made correctly. Unless we have a better way around this, we should use this to achieve the results we want.
| After completing generation for a metadata type, you MUST advance to the next type in the sequence. Never loop back to a previously completed type. The required execution order is: | ||
|
|
||
| 1. `CustomObject` — load `generating-custom-object` skill, call `get_metadata_type_fields("CustomObject")`, generate, checkpoint | ||
| 2. `CustomField` — load `generating-custom-field` skill, call `get_metadata_type_fields("CustomField")`, generate, checkpoint |
There was a problem hiding this comment.
get_metadata_type_fields("CustomField") : API context has 5 tools, we can not hard code and direct to use only single tool.
There was a problem hiding this comment.
I think this is one reason why API Context calls are not being made. Do we know at a high level which other tool calls are needed for which type? This makes all the difference in the testing I have seen so far
There was a problem hiding this comment.
This is a static plan and we are getting deployable metadata from this. we can further add what all tool calls should be made for any specific md type if we see issues. Currently I dont see any more for space station.
| category: orchestration | ||
| version: "1.0" | ||
| related-skills: generating-custom-object, generating-custom-field, generating-custom-tab, generating-flexipage, generating-custom-application, generating-flow, generating-validation-rule, generating-list-view, generating-permission-set | ||
| related-skills: skills/generating-custom-object/SKILL.md, skills/generating-custom-field/SKILL.md, skills/generating-custom-tab/SKILL.md, skills/generating-flexipage/SKILL.md, skills/generating-custom-application/SKILL.md, skills/generating-flow/SKILL.md, skills/generating-validation-rule/SKILL.md, skills/generating-list-view/SKILL.md, skills/generating-permission-set/SKILL.md |
There was a problem hiding this comment.
I think you modified on top of stale version, we updated this path, we can not have hard dependenci paths like this, now OOTB skills uses Sf-Skills not skills, it might conuse Agent.
There was a problem hiding this comment.
Got it, had taken the latest pull last evening will test and revert this.
2 participants
References: Contributing guide · Skill authoring guide · Agent Skills spec
What changed
lightning app skill file and A4V rules
Why
Notes
Working for 9/10 runs