/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

nextlevelbuilder/ui-ux-pro-max-skill

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:04:48.418Z

3mo ago

nextlevelbuilder/ui-ux-pro-max-skill

UI UX Pro Max is an actively maintained AI skill for generating professional UI/UX design systems across multiple platforms and frameworks. It is popular (54,726 stars, 5,304 forks) and has recent activity as of 2026-03-28. The repo appears to include a documentation site plus CLI, preview, screenshots, and source content for the skill.

Loading tags...

Stars54,726

Forks5,304

Default branchmain

Last pushed2026-03-28T05:40:26Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you want the upstream project with essentially no modifications and are comfortable missing the latest 18 upstream updates. If you want the newest CLI fixes, asset sync work, or Three.js-related additions, upstream is the better starting point.

Choose this fork only if you need a lightly pinned snapshot. If you want the newest CLI fixes and feature work, upstream is the better default.

Choose this fork if your priority is operational workflow support, especially GitHub Actions-based packaging and SLSA publishing. Avoid it if you want the newest upstream UI/UX skill features, because it appears significantly behind and mostly changes automation rather than core capability.

Choose upstream unless you specifically want a fork as your own working copy. This fork has no added capabilities and is behind recent upstream improvements, so its value is mainly as a starting point for private customization.

Choose this fork only if you want the project’s funding workflow extended with GitHub Sponsors and Buy Me a Coffee. If you want the newest CLI, integration, or bug-fix work, upstream is the better default because this fork is materially behind and otherwise nearly unchanged.

Choose the upstream project unless you specifically need a blank fork to extend. This fork does not add capabilities and is already behind recent upstream work, so it is best treated as a staging copy rather than a differentiated distribution.

Choose upstream unless you specifically need this fork as a frozen snapshot; it currently offers no added capability and is behind the main project.

Adopt this fork only if you want a close copy of upstream and are prepared to sync the missing upstream commits yourself. For most users, upstream is the better choice because this fork adds nothing yet lags behind recent work.

Prefer upstream unless you specifically need a personal fork. This fork is effectively a stale mirror with no added capability, so its main value is ownership, not differentiation.

Fork comparison

moekyawaungvivov30pro-design/ui-ux-pro-max-skill

52/100

slowing

minor

Choose this fork only if you want the upstream project with essentially no modifications and are comfortable missing the latest 18 upstream updates. If you want the newest CLI fixes, asset sync work, or Three.js-related additions, upstream is the better starting point.

Likely purpose

A copy for tracking or experimenting with the upstream UI/UX design skill, without diverging yet.

Best for

Teams that want an almost untouched mirror of the upstream skill.; Users planning to add their own changes on top of a clean baseline.; Maintainers who prefer minimal divergence and can periodically rebase from upstream.

Additional features

Missing features

18 upstream commits of fixes and enhancements are not present here, including CLI uninstall handling improvements, draft and Google Fonts asset sync for the CLI, and Three.js stack integration.
Any upstream bug fixes and review-driven cleanups after the fork point are absent, so adopters may miss recent stability and compatibility work.

Strengths

Low divergence makes it easy to sync back to upstream.
Suitable if you want the upstream design-skill baseline with minimal local customization risk.
Recent push activity suggests it is not abandoned entirely.

Risks

It is behind upstream, so adopters inherit known fixes and feature additions only from before the fork point.
No unique commits means there is no fork-specific value yet.
If you need the newest CLI behavior or stack support, this fork may lag until rebased.

nextlevelbuilder/ui-ux-pro-max-skill · Discofork