[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WHQZ0HHBMJSTSFTPJASXY":3,"skill-same:01M77WHQZ0HHBMJSTSFTPJASXY":52},{"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},"01M77WHQZ0HHBMJSTSFTPJASXY","stitch-manage-design-system",null,"Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating\u002Fupdating design systems in Stitch, and applying them to screens.","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-manage-design-system\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating\u002Fupdating design systems in Stitch, and applying them to screens.\"\n---\n# Design-System\n\nCreate a \"source of truth\" for your project's design language to ensure\nconsistency across all future screens.\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., `get_screen`,\n> `create_design_system_from_design_md`, `apply_design_system`).\n\n## 📥 Retrieval\n\nTo analyze a Stitch project, you must retrieve metadata and assets using the\nStitch MCP tools:\n\n1. **Project lookup**: Use `list_projects` to find the target `projectId`.\n2. **Screen lookup**: Use `list_screens` for that `projectId` to find\n   representative screens (e.g., \"Home\", \"Main Dashboard\").\n3. **Metadata fetch**: Call `get_screen` for the target screen to get\n   `screenshot.downloadUrl` and `htmlCode.downloadUrl`.\n4. **Asset download**: Use `read_url_content` to fetch the HTML code.\n\n## 🧠 Synthesis from Description\n\nIf you need to extract a design system from existing screens, use the `design-md` skill (in the `stitch-utilities` plugin).\n\nIf there are no existing screens (new project), or the user provides a direct description (e.g., \"dark theme, blue and purple, rounded, Inter font\"):\n\n1. Map the user's vague terms to precise values using the design mappings (see `design-md` skill in `stitch-utilities` or `generate-design` skill).\n2. Select concrete hex codes, font families, and roundness values.\n3. Generate the `DESIGN.md` file (refer to the `design-md` skill in `stitch-utilities` for structure).\n4. Proceed to the \"Create or Update Design System in Stitch\" step below.\n\n## 📝 Output Structure\n\nThe `DESIGN.md` file should follow the structure defined in the `design-md` skill (in the `stitch-utilities` plugin).\n\n## 🚀 Create or Update Design System in Stitch\n\nAfter generating `.stitch\u002FDESIGN.md`, make sure to also create or update the\ndesign system in Stitch.\n\n**Two-step design system creation:**\n\n> [!WARNING]\n> **Checkpoint — User Confirmation Required.**\n> Before uploading, you **MUST** pause and ask the user for\n> confirmation. Present a summary of the design system you are about to create\n> (display name, key colors, fonts, and roundness) and wait for explicit approval\n> before proceeding. Do **NOT** upload until the user confirms.\n\n1. **Upload `DESIGN.md`**:\n   - **Option A (Recommended - Uploader Script)**: Use the modified `upload-to-stitch` Python script which natively handles `.md` files. It base64-encodes the markdown file in-process and sends it to the `\u002Fv1\u002Fprojects\u002F{projectId}\u002Fscreens:batchCreate` endpoint, bypassing output token limits.\n     ```bash\n     python3 stitch-skills\u002Fplugins\u002Fstitch-design\u002Fskills\u002Fupload-to-stitch\u002Fscripts\u002Fupload_to_stitch.py \\\n       --project-id \u003CPROJECT_ID> \\\n       --file-path \u002Fpath\u002Fto\u002FDESIGN.md \\\n       --api-key \u003CAPI_KEY> \\\n       --generated-by \u003CGENERATED_BY>\n     ```\n     Set `\u003CGENERATED_BY>` to identify the skill or tool that produced the\n     `DESIGN.md`. Use the calling skill name when invoked from another skill\n     (e.g. `stitch::code-to-design`), or the agent\u002Ftool name for standalone\n     use (e.g. `Gemini`, `Claude Code`). If omitted, the script defaults to\n     `UserUploadedDesignMd`.\n\n     This returns the `sourceScreen` ID and the `screenInstance` ID.\n   - **Option B (Direct MCP Tool)**: If the `DESIGN.md` is small (under ~5KB), you can call the `upload_design_md` MCP tool directly, passing the base64-encoded design markdown content as `designMdBase64`.\n2. **Create Design System**: Call the `create_design_system_from_design_md` tool immediately after the upload, passing the `projectId` and the `selectedScreenInstance` (containing the `id` and `sourceScreen` returned from the upload step).\n\nOnce the upload script and `create_design_system_from_design_md` have both completed,\nStitch holds the design tokens at the project level — you do NOT need to repeat\nthem in generation prompts.\n\n## 🎨 Apply Design System to Screens\n\nUse `apply_design_system` to apply a design system to existing screens.\n\n> [!IMPORTANT]\n> `selectedScreenInstances` must contain **only** `id` and `sourceScreen` — do\n> NOT include position\u002Fdimension fields (`x`, `y`, `width`, `height`) or the\n> request will fail with \"invalid argument\". Get the screen instance IDs from\n> `get_project`.\n\n```json\n{\n  \"projectId\": \"...\",\n  \"assetId\": \"...\",\n  \"selectedScreenInstances\": [\n    {\n      \"id\": \"...\",\n      \"sourceScreen\": \"projects\u002F...\u002Fscreens\u002F...\"\n    }\n  ]\n}\n```\n\n**How to get the required IDs:**\n1. Call `get_project` to retrieve `screenInstances` — each has an `id` and\n   `sourceScreen`.\n2. Call `list_design_systems` to retrieve the design system `name` (format:\n   `assets\u002F{assetId}`) — use the part after `assets\u002F` as the `assetId`.\n3. Filter out any instances with `type: \"DESIGN_SYSTEM_INSTANCE\"` — only pass\n   real screens.\n\n## 📋 Update Project Metadata\n\nAfter writing `.stitch\u002FDESIGN.md`, also create or update `.stitch\u002Fmetadata.json`\nto track the `projectId`, `title`, all known screens, and design system summary.\nSee [examples\u002Fmetadata.json](examples\u002Fmetadata.json) for the format.\n\n## Schema Reference\n\nSee [reference\u002Ftool-schema.md](reference\u002Ftool-schema.md) for the full\n`designSystem` object schema with all available options.\n\n## 💡 Best Practices\n\nRefer to the `design-md` skill (in the `stitch-utilities` plugin) for best practices on describing design elements.\n","# Design-System\n\nCreate a \"source of truth\" for your project's design language to ensure\nconsistency across all future screens.\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., `get_screen`,\n> `create_design_system_from_design_md`, `apply_design_system`).\n\n## 📥 Retrieval\n\nTo analyze a Stitch project, you must retrieve metadata and assets using the\nStitch MCP tools:\n\n1. **Project lookup**: Use `list_projects` to find the target `projectId`.\n2. **Screen lookup**: Use `list_screens` for that `projectId` to find\n   representative screens (e.g., \"Home\", \"Main Dashboard\").\n3. **Metadata fetch**: Call `get_screen` for the target screen to get\n   `screenshot.downloadUrl` and `htmlCode.downloadUrl`.\n4. **Asset download**: Use `read_url_content` to fetch the HTML code.\n\n## 🧠 Synthesis from Description\n\nIf you need to extract a design system from existing screens, use the `design-md` skill (in the `stitch-utilities` plugin).\n\nIf there are no existing screens (new project), or the user provides a direct description (e.g., \"dark theme, blue and purple, rounded, Inter font\"):\n\n1. Map the user's vague terms to precise values using the design mappings (see `design-md` skill in `stitch-utilities` or `generate-design` skill).\n2. Select concrete hex codes, font families, and roundness values.\n3. Generate the `DESIGN.md` file (refer to the `design-md` skill in `stitch-utilities` for structure).\n4. Proceed to the \"Create or Update Design System in Stitch\" step below.\n\n## 📝 Output Structure\n\nThe `DESIGN.md` file should follow the structure defined in the `design-md` skill (in the `stitch-utilities` plugin).\n\n## 🚀 Create or Update Design System in Stitch\n\nAfter generating `.stitch\u002FDESIGN.md`, make sure to also create or update the\ndesign system in Stitch.\n\n**Two-step design system creation:**\n\n> [!WARNING]\n> **Checkpoint — User Confirmation Required.**\n> Before uploading, you **MUST** pause and ask the user for\n> confirmation. Present a summary of the design system you are about to create\n> (display name, key colors, fonts, and roundness) and wait for explicit approval\n> before proceeding. Do **NOT** upload until the user confirms.\n\n1. **Upload `DESIGN.md`**:\n   - **Option A (Recommended - Uploader Script)**: Use the modified `upload-to-stitch` Python script which natively handles `.md` files. It base64-encodes the markdown file in-process and sends it to the `\u002Fv1\u002Fprojects\u002F{projectId}\u002Fscreens:batchCreate` endpoint, bypassing output token limits.\n     ```bash\n     python3 stitch-skills\u002Fplugins\u002Fstitch-design\u002Fskills\u002Fupload-to-stitch\u002Fscripts\u002Fupload_to_stitch.py \\\n       --project-id \u003CPROJECT_ID> \\\n       --file-path \u002Fpath\u002Fto\u002FDESIGN.md \\\n       --api-key \u003CAPI_KEY> \\\n       --generated-by \u003CGENERATED_BY>\n     ```\n     Set `\u003CGENERATED_BY>` to identify the skill or tool that produced the\n     `DESIGN.md`. Use the calling skill name when invoked from another skill\n     (e.g. `stitch::code-to-design`), or the agent\u002Ftool name for standalone\n     use (e.g. `Gemini`, `Claude Code`). If omitted, the script defaults to\n     `UserUploadedDesignMd`.\n\n     This returns the `sourceScreen` ID and the `screenInstance` ID.\n   - **Option B (Direct MCP Tool)**: If the `DESIGN.md` is small (under ~5KB), you can call the `upload_design_md` MCP tool directly, passing the base64-encoded design markdown content as `designMdBase64`.\n2. **Create Design System**: Call the `create_design_system_from_design_md` tool immediately after the upload, passing the `projectId` and the `selectedScreenInstance` (containing the `id` and `sourceScreen` returned from the upload step).\n\nOnce the upload script and `create_design_system_from_design_md` have both completed,\nStitch holds the design tokens at the project level — you do NOT need to repeat\nthem in generation prompts.\n\n## 🎨 Apply Design System to Screens\n\nUse `apply_design_system` to apply a design system to existing screens.\n\n> [!IMPORTANT]\n> `selectedScreenInstances` must contain **only** `id` and `sourceScreen` — do\n> NOT include position\u002Fdimension fields (`x`, `y`, `width`, `height`) or the\n> request will fail with \"invalid argument\". Get the screen instance IDs from\n> `get_project`.\n\n```json\n{\n  \"projectId\": \"...\",\n  \"assetId\": \"...\",\n  \"selectedScreenInstances\": [\n    {\n      \"id\": \"...\",\n      \"sourceScreen\": \"projects\u002F...\u002Fscreens\u002F...\"\n    }\n  ]\n}\n```\n\n**How to get the required IDs:**\n1. Call `get_project` to retrieve `screenInstances` — each has an `id` and\n   `sourceScreen`.\n2. Call `list_design_systems` to retrieve the design system `name` (format:\n   `assets\u002F{assetId}`) — use the part after `assets\u002F` as the `assetId`.\n3. Filter out any instances with `type: \"DESIGN_SYSTEM_INSTANCE\"` — only pass\n   real screens.\n\n## 📋 Update Project Metadata\n\nAfter writing `.stitch\u002FDESIGN.md`, also create or update `.stitch\u002Fmetadata.json`\nto track the `projectId`, `title`, all known screens, and design system summary.\nSee [examples\u002Fmetadata.json](examples\u002Fmetadata.json) for the format.\n\n## Schema Reference\n\nSee [reference\u002Ftool-schema.md](reference\u002Ftool-schema.md) for the full\n`designSystem` object schema with all available options.\n\n## 💡 Best Practices\n\nRefer to the `design-md` skill (in the `stitch-utilities` plugin) for best practices on describing design elements.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fstitch-manage-design-system",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-manage-design-system",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill stitch-manage-design-system",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill stitch-manage-design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-manage-design-system\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Ftool-schema.md","REFERENCE","参考文档",6630,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-manage-design-system\u002Freference\u002Ftool-schema.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]