dtcg plugins

by Manavarya Singh

Extract any website's design language and ship it. Fourteen slash commands — /extract, /site, /grade, /battle, /remix, /pack, /theme-swap, /brand, /pair, /studio, /verify, /fidelity, /gallery, /dna — wrap the designlang CLI to pull DTCG tokens, Tailwind/shadcn/Figma vars, motion + voice, synthesize a whole-site canonical design system with a consistency grade, generate shareable graded report cards, head-to-head battle pages, six-vocabulary remixes, downloadable design-system bundles, OKLCH-correct theme recolouring, full editorial brand-guidelines books, design crossovers between two sites, a live token-editor studio, a rebuild-and-pixel-diff fidelity check, a measured clone-vs-original fidelity score (visual + motion) with a ranked correction plan via /fidelity, a shareable static gallery of scored clones via /gallery, and — via /dna — a measured design space that places any site among real design systems by nearest neighbours, per-axis percentiles, and the features that make it look the way it does.

by Anselm Hahn

Derives a named, platform-neutral design system from reference exemplars and emits it to any target. Measurement and interpretation stay separate artefacts rather than separate sections: decode records what each reference actually shows, graded for how far its values can be trusted and what rights its source carries, while name interprets — every recurring element gets a purpose, a rule and an anti-rule, and a rule with no stated failure case is not emitted at all. The source of truth is a DTCG token file, never CSS; CSS, a VitePress theme layer and the landscape sketchbook are formatter output run by committed scripts, so the same tokens regenerate byte-stable. References are read-only, enforced by a PreToolUse hook rather than by convention, so values and rules may be extracted while assets are never copied. Every fan-out agent is read-only; writes are confined to the configured design root's system/ and out/ directories.

by Tej Gandham

Stack-agnostic, ad-hoc orchestration framework. karta synthesizes a binder of work items (karta-plan) and delivers it in parallel waves onto a per-binder integration branch (karta-deliver), building each item in an isolated git worktree (karta-build) and verifying it against its own acceptance check — behavioral (karta-verify) or visual (karta-validate). Works across stacks (frontend, backend, CLI, data, IaC, …) while keeping deep frontend support: component/icon/token mapping, DTCG conformance, and a design-validation loop.

by Tej Gandham

Stack-agnostic, ad-hoc orchestration framework. karta synthesizes a binder of work items (karta-plan) and delivers it in parallel waves onto a per-binder integration branch (karta-deliver), building each item in an isolated git worktree (karta-build) and verifying it against its own acceptance check — behavioral (karta-verify) or visual (karta-validate). Works across stacks (frontend, backend, CLI, data, IaC, …) while keeping deep frontend support: component/icon/token mapping, DTCG conformance, and a design-validation loop.