From 1307d97a72e6c1cda572cb65471ae5ce82995218 Mon Sep 17 00:00:00 2001 From: amazscript Date: Tue, 21 Jul 2026 17:51:36 +0200 Subject: [PATCH] docs: don't hardcode React Native as the project stack (#427) Step 1 of the workflow told the agent the stack was always React Native ("this project's only tech stack"), a leftover from the skill's origin as a React Native project. In a generic skill this actively misleads: agents pick React Native guidance for web, Flutter or desktop work, and skip the matching `--stack` file entirely. Replace it with stack inference plus an explicit platform question, and point at the Available Stacks list so the right rules get loaded. Also flags that several rule sections are scoped to App UI, so mobile-only concerns (safe areas, haptics, bottom nav, Dynamic Type) are not applied to desktop-web work. Co-authored-by: decilapdenis Co-authored-by: Claude Opus 4.8 (1M context) --- cli/assets/templates/base/skill-content.md | 7 ++++++- src/ui-ux-pro-max/templates/base/skill-content.md | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/cli/assets/templates/base/skill-content.md b/cli/assets/templates/base/skill-content.md index 83fea45..55812a1 100644 --- a/cli/assets/templates/base/skill-content.md +++ b/cli/assets/templates/base/skill-content.md @@ -42,7 +42,12 @@ Extract key information from user request: - **Product type**: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid - **Target audience**: C-end consumer users; consider age group, usage context (commute, leisure, work) - **Style keywords**: playful, vibrant, minimal, dark mode, content-first, immersive, etc. -- **Stack**: React Native (this project's only tech stack) +- **Stack**: whatever the user is actually building with — infer it from the project + (package.json, existing files, explicit request) or ask. Then load its rules with + `--stack ` (see "Available Stacks"). Do not assume React Native. +- **Platform**: web or native app. Several sections below are scoped to App UI + (iOS/Android/React Native/Flutter) and do not apply to desktop-web work — + safe areas, haptics, bottom nav and Dynamic Type are mobile-only concerns. ### Step 2: Generate Design System (REQUIRED) diff --git a/src/ui-ux-pro-max/templates/base/skill-content.md b/src/ui-ux-pro-max/templates/base/skill-content.md index 83fea45..55812a1 100644 --- a/src/ui-ux-pro-max/templates/base/skill-content.md +++ b/src/ui-ux-pro-max/templates/base/skill-content.md @@ -42,7 +42,12 @@ Extract key information from user request: - **Product type**: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid - **Target audience**: C-end consumer users; consider age group, usage context (commute, leisure, work) - **Style keywords**: playful, vibrant, minimal, dark mode, content-first, immersive, etc. -- **Stack**: React Native (this project's only tech stack) +- **Stack**: whatever the user is actually building with — infer it from the project + (package.json, existing files, explicit request) or ask. Then load its rules with + `--stack ` (see "Available Stacks"). Do not assume React Native. +- **Platform**: web or native app. Several sections below are scoped to App UI + (iOS/Android/React Native/Flutter) and do not apply to desktop-web work — + safe areas, haptics, bottom nav and Dynamic Type are mobile-only concerns. ### Step 2: Generate Design System (REQUIRED)