Roadmap / Feature Requests

Problem Users cannot tell whether a palette actually fits their design until they apply it manually, which makes palette validation slow and speculative. Proposed Solution Add a quick simulation on the current selection. Detect colors in the selected page, illustration or component Remap each detected color to a palette color based on its luminance, computed client-side No semantics involved, purely a visual preview Acceptance Criteria [ ] Users can trigger a palette simulation on a selection [ ] Detected colors are remapped by luminance to palette colors [ ] Simulation runs client-side with no server call [ ] Original document colors can be restored after preview Use Case As a designer evaluating a palette, I want to see it applied to my existing design so that I can validate the direction before committing. Additional Context Exploratory hypothesis; precedes the more technical, template-based semantic simulation. Market Opportunity Shortens the path from palette creation to confident adoption, a strong hook for trial users.

Problem Exports assume sRGB only, so users on wide-gamut displays cannot output optimized color values for modern screens. Proposed Solution Make the target gamut an explicit palette setting. Support sRGB, Display P3 and Rec. 2020 Gamut stored per palette, not globally Default to sRGB for maximum compatibility Acceptance Criteria [ ] Gamut is selectable in palette settings, with sRGB as default [ ] Exported color values are converted to the selected gamut [ ] Existing palettes keep sRGB behavior after migration [ ] Selected gamut is stated in generated documentation and exports Use Case As a designer working on wide-gamut screens, I want to export in Display P3 so that my colors render as intended. Additional Context Applies to Figma, FigJam, Penpot, Sketch, Buzz, Framer. Market Opportunity Appeals to brand and media teams on high-end hardware, reinforcing the Pro tier value.

Problem Palettes only expose primitive tints, so teams must recreate semantic naming (surface, text, border…) by hand in every editor and keep it in sync manually. Proposed Solution Add a UI context to define and visualize semantics mapped to primitives. New semantic editing context, with an embedded example taxonomy (no default taxonomy injected) Figma: dedicated Variables collection referencing primitives; modes handled on primitives only; "Primitives" and "Semantics" style folders per palette Penpot: new Token Sets referencing primitive sets; themes handled inside primitives; same folder logic Sketch: primitive and semantic folders, styles and variables only, no cross-reference Framer: styles with auto-generated inverted color, plus Primitives and Semantics folders Generated documentation: shared template with a taxonomy breakdown table and associated colors Any semantic can be excluded from code, documentation and all exports Acceptance Criteria [ ] Users can define and visualize semantics linked to primitives in a dedicated context [ ] Primitive and semantic folders/collections are created per palette, even when semantics are empty [ ] Documentation includes the taxonomy table, empty but structured when nothing is filled Excluded semantics appear in no export, no code and no documentation Use Case As a design system owner, I want semantic tokens generated from my palette so that product teams consume intent, not raw tints. Additional Context Back-end is ready: taxonomy and primitive ↔ semantic binding are implemented; remaining work is front-end. Exclusion is handled engine-side and needs follow-up for multi-document zip exports. Market Opportunity Moves the product from palette generator to full design system tooling, targeting the teams with the highest willingness to pay.

In nature, shades (shadows) are more saturated, and the more sunny or lighter parts are less saturated. I would like if we could emulate that in the generator by having two saturation sliders - one for shades and other for tints.

Problem Users need to save and reuse color palette configurations, settings, or custom arrangements to improve workflow efficiency and maintain consistency across palettes and projects. Proposed Solution Implement a preset system that allows users to: Save current palette configurations as named presets Quickly apply saved presets to new palettes Organize and manage preset libraries Share presets with team members Acceptance Criteria [ ] Enable saving of current palette state as a named preset [ ] Provide preset library/manager interface [ ] Allow quick application of saved presets to new palettes [ ] Support preset organization with folders/categories [ ] Enable preset sharing within teams or workspaces [ ] Include preset preview/thumbnail functionality [ ] Support preset import/export for backup and migration Use Case As a designer working on multiple palettes and projects, I want to save my frequently used color palette configurations as presets so that I can quickly apply consistent color schemes across different palettes/projects without having to recreate them each time. Additional Context This feature would significantly speed up the design process for users who work with recurring color schemes or brand guidelines, reducing setup time and ensuring consistency across palettes/projects. Benefits Improved workflow efficiency Reduced setup time for new palettes Better consistency across design work Enhanced collaboration through preset sharing

Problem Users need to integrate their design system palettes with popular website builders like Framer and Webflow to maintain brand consistency across different platforms and reduce manual color management. Proposed Solution Create an extension/integration that allows users to: Consume published palettes as styles or assets directly in Webflow Create and manage palettes quickly, with less sophistication than full design tools Acceptance Criteria [ ] Consume published palettes as styles or assets in Webflow [ ] Create and manage palettes quickly, with less sophistication than full design tools [ ] Enable one-click palette import/export between platforms [ ] Provide simplified palette management interface optimized for Webflow Use Case As a web designer/developer using website builders, I want to easily access and apply my design system palettes in Webflow so that I can maintain brand consistency without manually recreating color schemes. Additional Context This extension would bridge the gap between sophisticated design systems and practical website building, making design tokens accessible to a broader range of users including those using no-code/low-code platforms. Market Opportunity Expanding into the website builder ecosystem opens up new user segments and use cases, particularly for agencies and freelancers who work across multiple platforms.

Problem Design teams need seamless synchronization between their design system primitives and Tokens Studio to maintain consistency across design and development workflows. Proposed Solution Implement automatic synchronization of design primitives (colors, typography, spacing, etc.) with Tokens Studio 1.0 platform to ensure: Real-time updates between design system and Tokens Studio 1.0 Consistent token management across tools Reduced manual work for design system maintenance Acceptance Criteria [ ] Establish bidirectional sync between design system and Tokens Studio 1.0 [ ] Ensure all primitive tokens (colors, typography, spacing) are synchronized [ ] Implement conflict resolution for concurrent updates Use Case As a design system maintainer, I want primitives to automatically sync with Tokens Studio 1.0 so that designers and developers always have access to the latest design tokens without manual intervention, reducing inconsistencies and maintenance overhead. Additional Context This integration would streamline the design-to-development handoff process and ensure single source of truth for design primitives across the entire product ecosystem.

Problem Design teams need seamless synchronization between their design system primitives and Supernova to maintain consistency across design and development workflows. Proposed Solution Implement automatic synchronization of design primitives (colors, typography, spacing, etc.) with Supernova platform to ensure: Real-time updates between design system and Supernova Consistent token management across tools Reduced manual work for design system maintenance Acceptance Criteria [ ] Establish bidirectional sync between design system and Supernova [ ] Ensure all primitive tokens (colors, typography, spacing) are synchronized [ ] Implement conflict resolution for concurrent updates Use Case As a design system maintainer, I want primitives to automatically sync with Supernova so that designers and developers always have access to the latest design tokens without manual intervention, reducing inconsistencies and maintenance overhead. Additional Context This integration would streamline the design-to-development handoff process and ensure single source of truth for design primitives across the entire product ecosystem.