CONTENT CREATION
Audit Figma color tokens for contrast, then gate the style-guide deploy on a passing report
On file change, evaluates every text/background color-token pairing for WCAG contrast, blocks the style-guide deploy if any required pair fails.
How it runs
The automated pipeline, trigger to output.
- TriggerFigma tokens changed (webhook)Figma
- ActionFetch color variables and documented pairingsFigma
- LogicCompute WCAG contrast; flag failing pairs
- ActionOn failure: file Linear issue per failing pair and stopLinear
- ActionOn pass: regenerate guide with contrast badgesOpenAI
- ActionDeploy passing style guide to VercelVercel
- OutputReport pass/fail outcome to SlackSlack
What it does
Adds an accessibility gate to your design-system pipeline. Before publishing the style guide, it checks color-token combinations against WCAG AA/AAA contrast thresholds and refuses to deploy a guide that documents inaccessible pairings.
When to use it
Use it when accessibility is a hard requirement and you want CI-style enforcement on design tokens, not just code. It catches a too-light text-on-surface combination at the token level before it spreads through the product.
How it works
- 1A Figma webhook fires when tokens change.
- 2The flow pulls color variables and the documented text/background pairings.
- 3A logic step computes contrast ratios and flags pairs below their required threshold.
- 4If any required pair fails, the flow opens a Linear issue per failure with the offending tokens and measured ratio, then stops before deploy.
- 5If all pairs pass, an OpenAI step regenerates the style-guide page with contrast badges shown next to each pairing.
- 6A Vercel step deploys the passing guide.
- 7A Slack message reports pass/fail with the failing-pair count or the live URL.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect VercelDeploys, runtime logs, analytics.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Full multi-format snippet pack from one episode
An agent takes a published episode and produces a complete repurposing pack: quote cards, show notes, audiogram scripts, and a thread, organized into a Notion hub page.
Guest recap email draft after episode publish
When an episode publishes, transcribe it, draft a personalized thank-you email to the guest with their best quotes and shareable links, and queue it as a Gmail draft.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Audiogram script and clip-timestamp builder
From a transcript dropped in Drive, pick three viral-worthy 30-to-60-second segments, write captions and hook text, and post the clip plan to Slack for editors.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Podcast episode to branded quote cards
When a new episode audio file lands in Drive, transcribe it, pull the five most quotable lines, and generate branded quote-card images ready to post.
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.