ENGINEERING
Reconcile Figma rename against Storybook stories before merging the MR
On a Figma rename, checks whether the renamed component still has a matching Storybook story; if the story name drifted, it updates both the Code Connect mapping and the story…
How it runs
The automated pipeline, trigger to output.
- TriggerFigma component renamedFigma
- ActionRead Code Connect map for mapped sourceFigma
- ActionSearch GitLab repo for matching Storybook storyGitLab
- LogicStory drifted? continue; missing? alert and stop
- ActionUpdate mapping in Figma and rewrite story titleFigma
- OutputOpen GitLab MR with synced changesGitLab
What it does
Closes the loop between Figma names, Code Connect, and Storybook. When a component is renamed in Figma it verifies a Storybook story still maps to the code component; if the story title is now out of sync it rewrites both the story and the Code Connect mapping and opens a GitLab MR. If no story exists at all, it raises the gap instead of guessing.
When to use it
Use it when your design system treats Storybook as the source of truth for component documentation and renames must stay consistent across Figma, Code Connect, and stories simultaneously.
How it works
- 1A Figma rename event triggers the flow.
- 2Read the Code Connect map to find the mapped source file and component.
- 3Search the GitLab repo for the matching Storybook story.
- 4Branch: if a story exists but the title drifted, continue; if none exists, alert in Slack and stop.
- 5Update the Code Connect mapping in Figma and rewrite the story title in the repo.
- 6Open a GitLab MR with the synced story and mapping changes.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.