Manavarya09/design-extract

An extraction currently writes 17+ files. Some users only want one (e.g. just tailwind.config.js for a CI artifact). Add two filter flags so the file write loop only writes what's asked for. What Two new options on the main extract command: --only <list> only write the named emitters (comma-separated) --skip <list> skip the named emitters (comma-separated) Where <list> is comma-separated emitter ids like tailwind,figma,dtcg,shadcn,react,ios,android,flutter,wordpress,pdf,brand-book. Where bin/design-extract.js. The extract action handler has a sequence of writeFileSync(...) calls each tied to one emitter. Wrap that sequence in a small helper: function shouldEmit(id, opts) { if (opts.only) return opts.only.split(',').map(s => s.trim()).includes(id); if (opts.skip) return !opts.skip.split(',').map(s => s.trim()).includes(id); return true; } Then gate each write behind if (shouldEmit('tailwind', opts)) { ... }. Acceptance npx designlang stripe.com --only tailwind writes only th

designlang already emits SwiftUI extensions (ios/DesignTokens.swift). Add a parallel UIKit emitter so iOS teams on UIKit don't have to manually translate. Why A non-trivial share of iOS apps are still UIKit-only. The emitted file should give them UIColor and UIFont extensions with the same token names as the SwiftUI version, so the two compile side-by-side in a mixed codebase. What to build src/formatters/ios-uikit.js exporting formatIosUIKit(dtcg). Output shape: import UIKit extension UIColor { static let dlPrimary = UIColor(red: 0.32, green: 0.23, blue: 0.99, alpha: 1.0) static let dlBackground = UIColor(red: 1.0, green: 1.0, blue: 1.0, alpha: 1.0) // ... } extension UIFont { static func dlSans(size: CGFloat, weight: UIFont.Weight = .regular) -> UIFont { return UIFont(name: "sohne-var", size: size) ?? .systemFont(ofSize: size, weight: weight) } } enum DLSpacing { static let xs: CGFloat = 4 static let sm: CGFloat = 8 // ... } Wire it up Add formatIosUIKit to th

Add a top-level --quiet / -q flag to the extract command so CI pipelines can run designlang without flooding their build logs. What When --quiet is passed: The progress spinner (ora) is suppressed. All informational console.log lines are skipped. Only the final summary block (or errors written to stderr) prints. The exit code is unchanged (0 on success, 1 on error). Where bin/design-extract.js. Add the option to the main extract command (and ideally to the other subcommands too: brand, pair, brands). A clean way: thread an opts.quiet boolean through the action handler and gate spinner.start() plus the console.log calls behind it. spinner = ora({ ... isSilent: opts.quiet }) is the cleanest path. Acceptance npx designlang stripe.com --quiet prints nothing on success. npx designlang stripe.com -q does the same. Errors still go to stderr and the exit code still reflects success/failure. An invalid URL still prints the error in quiet mode (via console.error). Scope ~20 lines across the

Add a new emitter that writes Open Props (https://open-props.style) CSS custom properties from the extracted DTCG tokens. Mirrors the existing emitters in src/formatters/. Why Open Props is a popular zero-runtime CSS variables library and a natural fit for designlang's output. Adding it means users can plug an extraction straight into an Open Props project without a manual translation step. What to build src/formatters/open-props.js exporting formatOpenProps(design) that returns a string of @layer blocks following the Open Props conventions: @layer base { :root { --brand-1: <primary>; --brand-2: <secondary>; --size-1: <spacing[0]>; --size-2: <spacing[1]>; --font-sans: <typography.families[0]>; --radius-1: <radii[0]>; /* ...etc */ } } Wire it up Add formatOpenProps to the extract command's emit loop in bin/design-extract.js (search for where formatTailwind is written). Add a corresponding entry to website/lib/build-files.js so the web extractor includes