Repository navigation
feat: improve mobile guidance and platform detection - #23
Merged
Merged
Conversation
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (16)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
AnxForever
marked this pull request as ready for review
October 7, 2026 05:42
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.
Mobile work could be routed into the wrong runtime: the detector classified React Native as React Web, while the Skill lacked guidance for selecting native versus browser components. This update adds evidence-based platform detection and mobile guidance, including how to adapt ChunUI's visual direction in a Web project and when to use its actual SwiftUI package.
The entrypoint now routes to focused references for mobile work, complete specs, and update controls. Existing updater safeguards remain intact. Documentation clarifies full CLI/API/MCP brief contracts, verifies
stylekit-cli@0.3.1 brief, and scopes Skills CLI upgrades with--projector--global. The managed payload version is 0.8.0.Validation:
git diff --checkpassed.skills@1.7.1 add <local-checkout> --listdiscovered exactly onestylekitskill without installing it.stylekit-cli@0.3.1 brief glassmorphismnormalized through the Python loader asstylekit-brief-v1with 10 recipes.The mobile library guidance uses official external sources; it does not assume the unpublished StyleKit
/mobileroute or invent asset-catalog entries. The existing StyleKit website checkout is not part of this PR.