feat: support community skins generation - #1663
Open
brtbrt wants to merge 10 commits into
Open
Conversation
Enable generate-design-tokens to discover and generate community skins from JSON tokens in the mistica-design repo. Community skin tokens are expected in tokens/community/ folder, with generated files output to src/community/skins/ and css/community/ directories. - Add community skins folder paths (src/community/skins, css/community) - Modify generateSkinSrc to handle community skins with correct import paths and type usage - Add generateCommunitySkins function to discover and process community token files - Community skins use generic Skin type instead of KnownSkin - Constants are defined inline in community skin files
|
Size stats
|
|
Deploy preview for mistica-web ready!
Deployed with vercel-action |
|
Accessibility report ℹ️ You can run this locally by executing |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the generate-design-tokens package to support generating both official and community skins from mistica-design tokens using a single, data-driven pipeline (skin families), aligning with the new tokens/community/ structure.
Changes:
- Refactors generation logic into a generic
generateSkinFamily(family)pipeline driven byOFFICIAL_SKINS_FAMILYandCOMMUNITY_SKINS_FAMILYdescriptors. - Adds
@generatedbanners to formatted TypeScript/CSS outputs and introduces community output folders (src/community/skins,css/community). - Updates the package README to document where official vs community generated files are written and where community tokens are discovered.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| packages/generate-design-tokens/README.md | Documents official vs community generated output locations and token discovery path. |
| packages/generate-design-tokens/index.js | Implements skin-family-based generation for official and community skins and adds generated banners. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
brtbrt
changed the title
Marcosld
approved these changes
Jul 22, 2026
brtbrt
commented
Jul 22, 2026
# Conflicts: # packages/generate-design-tokens/index.js
brtbrt
commented
Jul 22, 2026
Contributor
Author
There was a problem hiding this comment.
testing the generation by using mistica-design master locally
brtbrt
enabled auto-merge
July 28, 2026 11:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
How the script is organized
The generator is built around one concept: a skin family. Each family is a descriptor object declaring where its tokens live, where its output goes, its list of skins, its file naming, and how its module is shaped (skinModule).
There are two:
OFFICIAL_SKINS_FAMILYand
COMMUNITY_SKINS_FAMILY.A single generic pipeline,
generateSkinFamily(family), does all the work: list the family's skins, generate each.tsxand.css, then run any family-specific shared files.main()just runs it for each family.The two families differ only in data, so official and community skins no longer have separate code paths.
Related Issues
Fixes #1588