feat: replacing ootb components with open code components @W-21880083@ [post-TDX]

[nkurapati-sfdx]

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

What changed

@W-21880083@

Replacing OOTB components with Open Code Component

Why

Automating manual step for salesforce developer

Notes

---

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)