From 08115f9bb179092efd15592f8fd3ffba5f90cd55 Mon Sep 17 00:00:00 2001 From: sandipkumar-yadav Date: Thu, 2 Apr 2026 10:14:36 +0530 Subject: [PATCH] Update SKILL.md --- skills/generating-lightning-app/SKILL.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/skills/generating-lightning-app/SKILL.md b/skills/generating-lightning-app/SKILL.md index 186d108..83b5131 100644 --- a/skills/generating-lightning-app/SKILL.md +++ b/skills/generating-lightning-app/SKILL.md @@ -274,11 +274,16 @@ After all phases complete, consolidate outputs into deployment-ready structure. --- -### STEP 4: Deployment-Time Permission Set Suggestion +### STEP 4: Deployment and Permission Set Suggestion Policy -Whenever deployment is executed, you MUST include a suggestion that the user can assign generated permission set(s) to the current user. +Deployment is user-triggered and permission guidance is suggestion-only. +- Do NOT deploy automatically after generation. +- After generation, present the task/build summary and wait for user instruction. +- Deploy only when the user explicitly asks to deploy. +- Whenever deployment is executed, include a suggestion that the user can assign generated permission set(s) to the current user. - Show this suggestion as part of the deployment response. +- Do NOT assign permission sets directly in this step; provide suggestion only. - Include runnable command suggestion: - `sf org assign permset --name ` - If multiple permission sets were generated, include one command per permission set.