feat: Migration to new Figma code connect templates#740
Merged
Conversation
…tained skill and update component listing skill
- rollback root tsconfig types change in favor of web/mobile type module for figma types - update imports in connect files to more specific paths - add code connect files for all icons (separate files for now)
Collaborator
✅ Heimdall Review Status
✅
|
| Code Owner | Status | Calculation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ui-systems-eng-team |
✅
1/1
|
Denominator calculation
|
Contributor
adrienzheng-cb
approved these changes
Jun 4, 2026
Contributor
|
💯 🥇 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Used Claude's new Dynamic Workflow to conduct a large-scale migration of hundreds of files across CDS web and mobile packages.
This also addresses CDS-2185 ensuring figma connect files are no longer compiled and packaged into the production builds of the CDS NPM packages, cutting thousands of unnecessary
.jsand.d.tsfiles.Problem
Strategy
Given a single .md file containing links to all 80 CDS Figma components/component sets, run a Claude Code dynamic workflow to orchestrate approximately 80 custom sub-agents each tasked with creating a new code connect template for a CDS component
Custom agent responsibilities:
figma-code-connectskillThe orchestration script (workflow) batches agents to avoid hitting Figma's tool call rate limits.
The workflow was built idempotent to ensure I could safely back off and reattempt at a later time if rate limits were hit.
Testing
How has it been tested?
Run Figma
connectCLI:--dry-runpublish to ensure connect templates were valid and pointing to correct Figma component nodespreviewcommand to spot check output of genereated codeChange management
type=routine
risk=low
impact=sev5
automerge=false