Keep a DS alive when 5 teams contribute
5 teams (web, iOS, Android, marketing, brand) contribute to the same DS and each one drifts. Knapsack OR Supernova OR zeroheight (pick 1) as central platform serving as source of truth, Figma Code Connect to sync DS↔code multi-framework, codemod-hypermod to propagate a migration across 5 implementations without line-by-line human review. Per-action trust levels mandatory (auto-merge / draft / suggest-only).
Why
Keep a DS alive when 5 teams contribute in parallel. Your DS works fine at 2 teams. At 5, everything breaks. Mobile team wants a Button with a haptic prop. Marketing wants to rename primary to brand-primary. iOS team demands a SwiftUI variant. You spend days arbitrating Slack and nights hand-writing codemods to propagate breaking changes. This kit lays down active governance: Knapsack (or Supernova Portal / zeroheight MCP depending on your stack) structures docs + tokens + brand for humans and agents, Figma Code Connect bridges Figma↔code multi-framework, Codemod (Hypermod) automates bulk…
When
Enterprise scale phase, audience DS manager / head of design / staff frontend with ≥5 contributing teams and ≥3 products. ✅ You know it's your kit when You arbitrate ≥3 DS PRs daily on competing contributions Migrations take weeks: renaming a token = hell Your consumers are multi-framework: React + SwiftUI + Compose + Vue ❌ Not for this kit You protect a single-team DS → proteger-ds-agents with…
Tools included
- Knapsack Platform
- Figma Code Connect
- Codemod Hypermod