[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WHGPPGY0ZP8DK82Y95KZD":3,"skill-same:01M77WHGPPGY0ZP8DK82Y95KZD":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77WHGPPGY0ZP8DK82Y95KZD","stitch-generate-design",null,"Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI\u002FUX terminology, design tokens and theme system capabilities.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-generate-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI\u002FUX terminology, design tokens and theme system capabilities.\"\n---\n# Generate Design\n\nCreate new design screens from text descriptions, images, or mockups, edit\nexisting screens with prompts and design system tokens, and generate design\nvariants using Stitch MCP.\n\n> [!NOTE]\n> Refer to your system prompt for instruction on handling MCP tool prefixes for\n> all tools mentioned in this skill (e.g., `list_projects`,\n> `generate_screen_from_text`, `edit_screens`).\n\n## 🎨 Prompt Enhancement Pipeline\n\nBefore calling any Stitch generation or editing tool, you MUST enhance the\nuser's prompt.\n\n### 1. Analyze Context\n\n- **Project**: Use `list_projects` to find the correct `projectId`. If no\n  suitable project exists, create one using `create_project`.\n- **Design System**: Check if a design system exists for the project via\n  `list_design_systems`. If one exists, design tokens (colors, fonts, roundness)\n  are already applied at the project level — do NOT include any color, font, or\n  theme instructions in the generation prompt. If none exists, delegate to the\n  **manage-design-system** skill first before generating screens.\n\n### 2. Refine UI\u002FUX Terminology\n\nConsult [Design Mappings](references\u002Fdesign-mappings.md) to replace vague terms.\n\n- Vague: \"Make a nice header\"\n- Professional: \"Sticky navigation bar with glassmorphism effect and centered\n  logo\"\n\nUse [Prompting Keywords](references\u002Fprompt-keywords.md) for component names,\nadjective palettes, color roles, and shape descriptions.\n\n### 3. Structure the Final Prompt\n\nFormat the enhanced prompt for Stitch. Focus exclusively on **layout, content,\nand structure** — never include colors, fonts, or theme instructions (these are\nhandled by the manage-design-system skill at the project level).\n\nFor **new screens**, use this template:\n\n```markdown\n[Overall purpose and user intent of the page]\n\n**PLATFORM:** [Web\u002FMobile], [Desktop\u002FMobile]-first\n\n**PAGE STRUCTURE:**\n1. **Header:** [Description of navigation and branding]\n2. **Hero Section:** [Headline, subtext, and primary CTA]\n3. **Primary Content Area:** [Detailed component breakdown]\n4. **Footer:** [Links and copyright information]\n```\n\nFor **edits**, be specific about what to change:\n\n- **Location**: \"Change the [primary button] in the [hero section]...\"\n- **Visuals**: \"...to a darker blue (#004080) and add a subtle shadow.\"\n- **Structure**: \"Add a secondary button next to the primary one with the text\n  'Learn More'.\"\n\n> [!CAUTION]\n> Do NOT include hex codes, font names, color palettes, roundness values, or\n> any design system tokens in a **generation** prompt. These are applied at the\n> project level by the manage-design-system skill and will conflict if\n> duplicated. (For **edit** prompts, hex codes are acceptable for precise\n> color adjustments.)\n\n### 4. Present AI Insights\n\nAfter any tool call, always surface the `outputComponents` (Text Description and\nSuggestions) to the user.\n\nSee [examples\u002Fenhanced-prompt.md](examples\u002Fenhanced-prompt.md) for a full\nbefore\u002Fafter prompt enhancement example.\n\n--------------------------------------------------------------------------------\n\n## Steps\n\n### Determine the Mode\n\nDecide which flow to use based on the user's request:\n\n- User wants to create from a text description → **Generate from Text** flow\n- User provides an image, screenshot, or mockup → **Generate from Image** flow\n- User wants to modify an existing screen → **Edit** flow\n- User wants layout\u002Fcolor\u002Fcontent variations → **Generate Variants** flow\n\n---\n\n### Generate from Text Flow (New Screen)\n\n#### 1. Enhance the User Prompt\n\nApply the Prompt Enhancement Pipeline above.\n\n#### 2. Identify the Project\n\nUse `list_projects` to find the correct `projectId` if it is not already known.\n\n#### 3. Generate the Screen\n\nCall the `generate_screen_from_text` tool with the enhanced prompt and the\n`designSystem` ID (if found in Step 1).\n\n```json\n{\n  \"projectId\": \"...\",\n  \"prompt\": \"[Your Enhanced Prompt]\",\n  \"designSystem\": \"assets\u002F...\", \u002F\u002F Optional: Pass if found in Step 1\n  \"deviceType\": \"DESKTOP\"  \u002F\u002F Options: MOBILE, DESKTOP, TABLET\n}\n```\n\n#### 4. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 5. Download Design Assets\n\nAfter generation, download the HTML and screenshot urls from `outputComponents`\nto the `.stitch\u002Fdesigns` directory.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n#### 6. Review and Refine\n\n- If the result is not exactly as expected, continue with the **Edit** flow\n  to make targeted adjustments.\n- Do NOT re-generate from scratch unless the fundamental layout is wrong.\n\n---\n\n### Generate from Image Flow (Image\u002FMockup → Design)\n\nUse this flow when the user provides an image, screenshot, or design mockup to\nrecreate in Stitch.\n\n#### 1. Identify the Project\n\nUse `list_projects` to find the correct `projectId`. If no suitable project\nexists, create one using `create_project`.\n\n#### 2. Upload the Image\n\nDelegate to the **upload-to-stitch** skill to upload the image to the project.\nThis creates a new screen with the image as its content.\n\n#### 3. Refine with Edit\n\nOnce uploaded, use `list_screens` to find the newly created `screenId`, then\ncall `edit_screens` with a descriptive prompt to refine the design:\n\n```json\n{\n  \"projectId\": \"...\",\n  \"selectedScreenIds\": [\"\u003Cuploaded-screen-id>\"],\n  \"prompt\": \"[Describe what to adjust, enhance, or recreate from this mockup]\"\n}\n```\n\n> [!TIP]\n> For best results, describe the intent behind the image rather than just saying\n> \"make it look like this\". For example: \"This is a dashboard mockup — recreate\n> it with a proper data table, sidebar navigation, and chart widgets.\"\n\n#### 4. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 5. Download Design Assets\n\nDownload the HTML and screenshot urls from `outputComponents` to the\n`.stitch\u002Fdesigns` directory.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n---\n\n### Edit Flow (Modify Existing Screen)\n\n#### 1. Identify the Screen\n\nUse `list_screens` or `get_screen` to find the correct `projectId` and\n`screenId`.\n\n#### 2. Formulate the Edit Prompt\n\nApply the Prompt Enhancement Pipeline, focusing on specificity:\n\n- **Location**: \"Change the color of the [primary button] in the [hero\n  section]...\"\n- **Visuals**: \"...to a darker blue (#004080) and add a subtle shadow.\"\n- **Structure**: \"Add a secondary button next to the primary one with the text\n  'Learn More'.\"\n\n#### 3. Apply the Edit\n\nCall the `edit_screens` tool.\n\n```json\n{\n  \"projectId\": \"...\",\n  \"selectedScreenIds\": [\"...\"],\n  \"prompt\": \"[Your targeted edit prompt]\"\n}\n```\n\n#### 4. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 5. Download Design Assets\n\nAfter editing, download the updated HTML and screenshot urls from\n`outputComponents` to the `.stitch\u002Fdesigns` directory, overwriting previous\nversions to ensure the local files reflect the latest edits.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n#### 6. Update Project Metadata\n\nAfter downloading assets, update `.stitch\u002Fmetadata.json` to reflect any changes\n(e.g., updated screen titles or new screen IDs from the edit). The metadata\nfile tracks all screens, their device types, and design system info. See the\n**manage-design-system** skill's `examples\u002Fmetadata.json` for the format.\n\n#### 7. Verify and Repeat\n\n- Check the output screen to see if the changes were applied correctly.\n- If more polish is needed, repeat the edit flow with a new specific prompt.\n\n---\n\n### Generate Variants Flow (Explore Variations)\n\nUse this flow when the user wants to explore alternative layouts, color schemes,\nor content variations of an existing screen.\n\n#### 1. Identify the Screen\n\nUse `list_screens` or `get_screen` to find the correct `projectId` and\n`screenId`.\n\n#### 2. Configure Variant Options\n\nCall the `generate_variants` tool with the appropriate options:\n\n```json\n{\n  \"projectId\": \"...\",\n  \"selectedScreenIds\": [\"...\"],\n  \"prompt\": \"[Describe the direction for variants]\",\n  \"variantOptions\": {\n    \"variantCount\": 3,\n    \"creativeRange\": \"EXPLORE\",\n    \"aspects\": [\"LAYOUT\", \"COLOR_SCHEME\"]\n  }\n}\n```\n\n**Variant Options:**\n- **`variantCount`**: 1–5 variants (default: 3)\n- **`creativeRange`**: `REFINE` (subtle), `EXPLORE` (balanced), or `REIMAGINE`\n  (radical)\n- **`aspects`**: Focus on specific dimensions — `LAYOUT`, `COLOR_SCHEME`,\n  `IMAGES`, `TEXT_FONT`, `TEXT_CONTENT`, or leave empty for all\n\n#### 3. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 4. Download Design Assets\n\nDownload the variant HTML and screenshot urls from `outputComponents` to the\n`.stitch\u002Fdesigns` directory.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n--------------------------------------------------------------------------------\n\n## 💡 Tips\n\n- **Be structural**: Break the page down into header, hero, features, and\n  footer in your prompt.\n- **Content first**: Describe what each section contains (text, images, CTAs)\n  rather than how it looks.\n- **Iterative Polish**: Prefer editing for targeted adjustments over full\n  re-generation.\n- **No theme leakage**: Never put hex codes, font names, or color roles in a\n  generation prompt — the design system handles all visual styling.\n- **Specify interactions**: Mention hover states, animations, and click behavior\n  rather than visual styling.\n- **Keep edits focused**: One edit at a time is often better than a long list of\n  changes.\n- **Reference components**: Use professional terms like \"navigation bar\", \"hero\n  section\", \"footer\", \"card grid\".\n- **Precise colors in edits**: Use hex codes for exact color matching when\n  editing existing screens.\n\n## 📚 References\n\n- [Design Mappings](references\u002Fdesign-mappings.md) — UI\u002FUX keywords and\n  atmosphere descriptors.\n- [Prompting Keywords](references\u002Fprompt-keywords.md) — Technical terms Stitch\n  understands best.\n- [Enhanced Prompt Example](examples\u002Fenhanced-prompt.md) — Before\u002Fafter prompt\n  enhancement.\n","# Generate Design\n\nCreate new design screens from text descriptions, images, or mockups, edit\nexisting screens with prompts and design system tokens, and generate design\nvariants using Stitch MCP.\n\n> [!NOTE]\n> Refer to your system prompt for instruction on handling MCP tool prefixes for\n> all tools mentioned in this skill (e.g., `list_projects`,\n> `generate_screen_from_text`, `edit_screens`).\n\n## 🎨 Prompt Enhancement Pipeline\n\nBefore calling any Stitch generation or editing tool, you MUST enhance the\nuser's prompt.\n\n### 1. Analyze Context\n\n- **Project**: Use `list_projects` to find the correct `projectId`. If no\n  suitable project exists, create one using `create_project`.\n- **Design System**: Check if a design system exists for the project via\n  `list_design_systems`. If one exists, design tokens (colors, fonts, roundness)\n  are already applied at the project level — do NOT include any color, font, or\n  theme instructions in the generation prompt. If none exists, delegate to the\n  **manage-design-system** skill first before generating screens.\n\n### 2. Refine UI\u002FUX Terminology\n\nConsult [Design Mappings](references\u002Fdesign-mappings.md) to replace vague terms.\n\n- Vague: \"Make a nice header\"\n- Professional: \"Sticky navigation bar with glassmorphism effect and centered\n  logo\"\n\nUse [Prompting Keywords](references\u002Fprompt-keywords.md) for component names,\nadjective palettes, color roles, and shape descriptions.\n\n### 3. Structure the Final Prompt\n\nFormat the enhanced prompt for Stitch. Focus exclusively on **layout, content,\nand structure** — never include colors, fonts, or theme instructions (these are\nhandled by the manage-design-system skill at the project level).\n\nFor **new screens**, use this template:\n\n```markdown\n[Overall purpose and user intent of the page]\n\n**PLATFORM:** [Web\u002FMobile], [Desktop\u002FMobile]-first\n\n**PAGE STRUCTURE:**\n1. **Header:** [Description of navigation and branding]\n2. **Hero Section:** [Headline, subtext, and primary CTA]\n3. **Primary Content Area:** [Detailed component breakdown]\n4. **Footer:** [Links and copyright information]\n```\n\nFor **edits**, be specific about what to change:\n\n- **Location**: \"Change the [primary button] in the [hero section]...\"\n- **Visuals**: \"...to a darker blue (#004080) and add a subtle shadow.\"\n- **Structure**: \"Add a secondary button next to the primary one with the text\n  'Learn More'.\"\n\n> [!CAUTION]\n> Do NOT include hex codes, font names, color palettes, roundness values, or\n> any design system tokens in a **generation** prompt. These are applied at the\n> project level by the manage-design-system skill and will conflict if\n> duplicated. (For **edit** prompts, hex codes are acceptable for precise\n> color adjustments.)\n\n### 4. Present AI Insights\n\nAfter any tool call, always surface the `outputComponents` (Text Description and\nSuggestions) to the user.\n\nSee [examples\u002Fenhanced-prompt.md](examples\u002Fenhanced-prompt.md) for a full\nbefore\u002Fafter prompt enhancement example.\n\n--------------------------------------------------------------------------------\n\n## Steps\n\n### Determine the Mode\n\nDecide which flow to use based on the user's request:\n\n- User wants to create from a text description → **Generate from Text** flow\n- User provides an image, screenshot, or mockup → **Generate from Image** flow\n- User wants to modify an existing screen → **Edit** flow\n- User wants layout\u002Fcolor\u002Fcontent variations → **Generate Variants** flow\n\n---\n\n### Generate from Text Flow (New Screen)\n\n#### 1. Enhance the User Prompt\n\nApply the Prompt Enhancement Pipeline above.\n\n#### 2. Identify the Project\n\nUse `list_projects` to find the correct `projectId` if it is not already known.\n\n#### 3. Generate the Screen\n\nCall the `generate_screen_from_text` tool with the enhanced prompt and the\n`designSystem` ID (if found in Step 1).\n\n```json\n{\n  \"projectId\": \"...\",\n  \"prompt\": \"[Your Enhanced Prompt]\",\n  \"designSystem\": \"assets\u002F...\", \u002F\u002F Optional: Pass if found in Step 1\n  \"deviceType\": \"DESKTOP\"  \u002F\u002F Options: MOBILE, DESKTOP, TABLET\n}\n```\n\n#### 4. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 5. Download Design Assets\n\nAfter generation, download the HTML and screenshot urls from `outputComponents`\nto the `.stitch\u002Fdesigns` directory.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n#### 6. Review and Refine\n\n- If the result is not exactly as expected, continue with the **Edit** flow\n  to make targeted adjustments.\n- Do NOT re-generate from scratch unless the fundamental layout is wrong.\n\n---\n\n### Generate from Image Flow (Image\u002FMockup → Design)\n\nUse this flow when the user provides an image, screenshot, or design mockup to\nrecreate in Stitch.\n\n#### 1. Identify the Project\n\nUse `list_projects` to find the correct `projectId`. If no suitable project\nexists, create one using `create_project`.\n\n#### 2. Upload the Image\n\nDelegate to the **upload-to-stitch** skill to upload the image to the project.\nThis creates a new screen with the image as its content.\n\n#### 3. Refine with Edit\n\nOnce uploaded, use `list_screens` to find the newly created `screenId`, then\ncall `edit_screens` with a descriptive prompt to refine the design:\n\n```json\n{\n  \"projectId\": \"...\",\n  \"selectedScreenIds\": [\"\u003Cuploaded-screen-id>\"],\n  \"prompt\": \"[Describe what to adjust, enhance, or recreate from this mockup]\"\n}\n```\n\n> [!TIP]\n> For best results, describe the intent behind the image rather than just saying\n> \"make it look like this\". For example: \"This is a dashboard mockup — recreate\n> it with a proper data table, sidebar navigation, and chart widgets.\"\n\n#### 4. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 5. Download Design Assets\n\nDownload the HTML and screenshot urls from `outputComponents` to the\n`.stitch\u002Fdesigns` directory.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n---\n\n### Edit Flow (Modify Existing Screen)\n\n#### 1. Identify the Screen\n\nUse `list_screens` or `get_screen` to find the correct `projectId` and\n`screenId`.\n\n#### 2. Formulate the Edit Prompt\n\nApply the Prompt Enhancement Pipeline, focusing on specificity:\n\n- **Location**: \"Change the color of the [primary button] in the [hero\n  section]...\"\n- **Visuals**: \"...to a darker blue (#004080) and add a subtle shadow.\"\n- **Structure**: \"Add a secondary button next to the primary one with the text\n  'Learn More'.\"\n\n#### 3. Apply the Edit\n\nCall the `edit_screens` tool.\n\n```json\n{\n  \"projectId\": \"...\",\n  \"selectedScreenIds\": [\"...\"],\n  \"prompt\": \"[Your targeted edit prompt]\"\n}\n```\n\n#### 4. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 5. Download Design Assets\n\nAfter editing, download the updated HTML and screenshot urls from\n`outputComponents` to the `.stitch\u002Fdesigns` directory, overwriting previous\nversions to ensure the local files reflect the latest edits.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n#### 6. Update Project Metadata\n\nAfter downloading assets, update `.stitch\u002Fmetadata.json` to reflect any changes\n(e.g., updated screen titles or new screen IDs from the edit). The metadata\nfile tracks all screens, their device types, and design system info. See the\n**manage-design-system** skill's `examples\u002Fmetadata.json` for the format.\n\n#### 7. Verify and Repeat\n\n- Check the output screen to see if the changes were applied correctly.\n- If more polish is needed, repeat the edit flow with a new specific prompt.\n\n---\n\n### Generate Variants Flow (Explore Variations)\n\nUse this flow when the user wants to explore alternative layouts, color schemes,\nor content variations of an existing screen.\n\n#### 1. Identify the Screen\n\nUse `list_screens` or `get_screen` to find the correct `projectId` and\n`screenId`.\n\n#### 2. Configure Variant Options\n\nCall the `generate_variants` tool with the appropriate options:\n\n```json\n{\n  \"projectId\": \"...\",\n  \"selectedScreenIds\": [\"...\"],\n  \"prompt\": \"[Describe the direction for variants]\",\n  \"variantOptions\": {\n    \"variantCount\": 3,\n    \"creativeRange\": \"EXPLORE\",\n    \"aspects\": [\"LAYOUT\", \"COLOR_SCHEME\"]\n  }\n}\n```\n\n**Variant Options:**\n- **`variantCount`**: 1–5 variants (default: 3)\n- **`creativeRange`**: `REFINE` (subtle), `EXPLORE` (balanced), or `REIMAGINE`\n  (radical)\n- **`aspects`**: Focus on specific dimensions — `LAYOUT`, `COLOR_SCHEME`,\n  `IMAGES`, `TEXT_FONT`, `TEXT_CONTENT`, or leave empty for all\n\n#### 3. Present AI Feedback\n\nAlways show the text description and suggestions from `outputComponents` to the\nuser.\n\n#### 4. Download Design Assets\n\nDownload the variant HTML and screenshot urls from `outputComponents` to the\n`.stitch\u002Fdesigns` directory.\n\n- **Naming**: Use the screen ID or a descriptive slug for the filename.\n- **Tools**: Use `curl -o` via `run_command` or similar.\n- **Directory**: Ensure `.stitch\u002Fdesigns` exists.\n\n--------------------------------------------------------------------------------\n\n## 💡 Tips\n\n- **Be structural**: Break the page down into header, hero, features, and\n  footer in your prompt.\n- **Content first**: Describe what each section contains (text, images, CTAs)\n  rather than how it looks.\n- **Iterative Polish**: Prefer editing for targeted adjustments over full\n  re-generation.\n- **No theme leakage**: Never put hex codes, font names, or color roles in a\n  generation prompt — the design system handles all visual styling.\n- **Specify interactions**: Mention hover states, animations, and click behavior\n  rather than visual styling.\n- **Keep edits focused**: One edit at a time is often better than a long list of\n  changes.\n- **Reference components**: Use professional terms like \"navigation bar\", \"hero\n  section\", \"footer\", \"card grid\".\n- **Precise colors in edits**: Use hex codes for exact color matching when\n  editing existing screens.\n\n## 📚 References\n\n- [Design Mappings](references\u002Fdesign-mappings.md) — UI\u002FUX keywords and\n  atmosphere descriptors.\n- [Prompting Keywords](references\u002Fprompt-keywords.md) — Technical terms Stitch\n  understands best.\n- [Enhanced Prompt Example](examples\u002Fenhanced-prompt.md) — Before\u002Fafter prompt\n  enhancement.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fstitch-generate-design",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill stitch-generate-design",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill stitch-generate-design",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill stitch-generate-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-generate-design\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"examples\u002Fenhanced-prompt.md","REFERENCE","参考文档",1704,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-generate-design\u002Fexamples\u002Fenhanced-prompt.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fdesign-mappings.md",2330,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-generate-design\u002Freferences\u002Fdesign-mappings.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fprompt-keywords.md",2798,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-generate-design\u002Freferences\u002Fprompt-keywords.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]