@W-21829588 : Custom Lightning Type Skills Fixes

[suhanigupta-collab]

References: Contributing guide · Skill authoring guide · Agent Skills spec

What changed

• Added clarification that nested objects are not supported / often fail validation in CLTs
• Introduced recommendation to use a flattened schema structure instead of nested objects
• Use Apex-based CLTs (@apexClassType/...) when true nesting is required
• Highlighted and corrected misspellings of lightning:type values
• Ensures use of valid types like:
  lightning__richTextType (not richtextType, etc.)

Why

• Nested objects are causing deployment failures — only flattened schemas are supported/allowed by the org metaschema
• Flattened structure ensures successful, deploy-safe CLTs
• Misspelled lightning:type values lead to schema validation failures and block deployment

Notes

• Change is incremental, not a full rewrite
• Focused only on:
  Nested object limitation
  Fixing incorrect lightning:type values
• No major structural changes to the skill

---

Skills

Manual checklist

Description quality

• Describes what the skill does and the expected output
• Includes relevant Salesforce domain keywords (Apex, LWC, SOQL, metadata types, etc.)
• Trigger phrases are specific enough for Vibes to select this skill reliably

Instructions

• Clear goal statement
• Step-by-step workflow
• Validation rules for generated output
• Defined output / artifact

Context efficiency

• Core instructions are concise — supporting material lives in templates/, examples/, or docs/ subdirectories
• No unnecessary background explanation in the body

Automated checks

Enforced by CI (npm run validate:skills) per the Agent Skills spec:

• Directory is one level deep, named in kebab-case (max 64 chars), contains SKILL.md
• Frontmatter name matches directory name; description is present, ≥ 20 words, ≤ 1024 characters, and includes trigger language
• Body is non-empty and under 500 lines
• Name uses gerund form ⚠ (warning — does not block merge)

[salesforce-cla]

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Suhani Gupta <s***@s***.i***.s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce Inc. Contributor License Agreement and this Pull Request will be revalidated.

[salesforce-cla]

Thanks for the contribution! It looks like @suhanigupta-collab is an internal user so signing the CLA is not required. However, we need to confirm this.