feat(react-native): add style-guide.json and Stitch API reference - #65
feat(react-native): add style-guide.json and Stitch API reference#65ademakdogan wants to merge 1 commit into
Conversation
… reference Adds two follow-up resources to the react-native skill, complementing the existing build skills: - resources/style-guide.json: starter design tokens (colors, spacing, typography, border radii) using React Native-friendly numeric units, so extracted Stitch values map to a theme instead of hardcoded styles. - resources/stitch-api-reference.md: documents the get_screen metadata schema and React Native-specific mapping rules (density-independent sizing, asset handling, theme extraction over Tailwind merging). SKILL.md references both resources from the retrieval and color-extraction steps so they are part of the generation flow.
|
Hey @ademakdogan! I think I can help you get this merged. The repo was recently-ish restructured to move all skills into the To resolve the conflicts, you can run these steps on your branch:
Once committed and pushed, this should clear the merge conflicts! |
Follow-up to #47 (closed as a duplicate of #42). As suggested by @davideast in that thread, this adds the extra resources on top of the merged
react-nativeskill rather than duplicating the core skill.What this adds
resources/style-guide.json— starter design tokens (colors, spacing, typography, border radii) using React Native-friendly numeric units. Gives the skill a concrete target to sync extracted Stitch values into, instead of hardcoding styles. Bringsreact-nativeto parity with the siblingreact-componentsskill, which already ships a style guide.resources/stitch-api-reference.md— documents theget_screenmetadata schema and React Native-specific mapping rules (density-independent sizing viauseWindowDimensions/Dimensions, asset handling throughmockData.ts, and mapping the HTMLtailwind.configinto the style guide /theme.tsrather than merging a web config).SKILL.md wiring
Both resources are referenced from
SKILL.md(the retrieval step points to the API reference; the color-extraction step points to the style guide) so they are part of the generation flow rather than orphaned files.No changes to the core skill behavior, scripts, or existing resources.