[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WHV9RNZWTZQ7YNJMS2PD5":3,"skill-same:01M77WHV9RNZWTZQ7YNJMS2PD5":92},{"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},"01M77WHV9RNZWTZQ7YNJMS2PD5","stitch-react-components",null,"Converts Stitch designs into modular Vite and React components, or syncs\u002Fupdates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.","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-react-components\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Converts Stitch designs into modular Vite and React components, or syncs\u002Fupdates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.\"\n---\n# Stitch to React Components\n\nYou are a frontend engineer focused on transforming designs into clean React code or syncing\u002Fupdating existing React components to align with the latest Stitch designs. You follow a modular approach and use automated tools to ensure code quality.\n\n> **CRITICAL: Every step in this skill is MANDATORY. Do NOT skip any step or take shortcuts. Each section contains a GATE that must be satisfied before proceeding.**\n\n## Phase 1: Retrieval and networking\n\n> **GATE: Phase 1 is complete ONLY when all screens have been downloaded via `scripts\u002Ffetch-stitch.sh` AND visually audited. Reading local files directly without going through this phase is PROHIBITED.**\n\n1. **Namespace discovery**: Run `list_tools` to find the Stitch MCP prefix. Use this prefix (e.g., `stitch:`) for all subsequent calls.\n2. **Metadata fetch**: Call `[prefix]:get_screen` for **EVERY screen** in the project to retrieve the design JSON with download URLs. Do NOT skip any screen.\n3. **Check for existing designs**: Before downloading, check if `.stitch\u002Fdesigns\u002F{page}.html` and `.stitch\u002Fdesigns\u002F{page}.png` already exist:\n   - **If files exist**: Ask the user whether to refresh the designs from the Stitch project using the MCP, or reuse the existing local files. **You MUST ask — do not assume.**  Only re-download if the user confirms.\n   - **If files do not exist**: Proceed to step 4.\n4. **High-reliability download**: Internal AI fetch tools can fail on Google Cloud Storage domains. You MUST use the provided script.\n   - **HTML**: `bash scripts\u002Ffetch-stitch.sh \"[htmlCode.downloadUrl]\" \".stitch\u002Fdesigns\u002F{page}.html\"`\n   - **Screenshot**: Append `=w{width}` to the screenshot URL first, where `{width}` is the `width` value from the screen metadata (Google CDN serves low-res thumbnails by default). Then run: `bash scripts\u002Ffetch-stitch.sh \"[screenshot.downloadUrl]=w{width}\" \".stitch\u002Fdesigns\u002F{page}.png\"`\n   - This script handles the necessary redirects and security handshakes.\n5. **Visual audit**: Review the downloaded screenshot (`.stitch\u002Fdesigns\u002F{page}.png`) to confirm design intent and layout details. **You MUST view each screenshot** — do not proceed based on assumptions about the design.\n6. **Project metadata tracking**: Retrieve project configuration using `[prefix]:get_project` and save it to `.stitch\u002Fmetadata.json` (inside the app folder, and mirrored in the workspace root). Ensure it has:\n   - `projectId`, `title`, `deviceType`\n   - A `Last Sync Time` field matching the current sync ISO execution time\n   - A `screens` map detailing each screen's ID, label, sourceScreen reference, dimensions, and canvasPosition.\n\n### Anti-patterns for Phase 1\n- ❌ Reading `.stitch\u002Fdesigns\u002F*.html` directly without calling MCP `get_screen` first.\n- ❌ Skipping the `fetch-stitch.sh` download script.\n- ❌ Not asking the user when existing files are found.\n- ❌ Skipping the visual audit of `.png` screenshots.\n- ❌ Failing to generate or update `.stitch\u002Fmetadata.json` and its `Last Sync Time` field upon syncing.\n\n## Phase 2: Style extraction\n\n> **GATE: Phase 2 is complete ONLY when `resources\u002Fstyle-guide.json` has been updated with tokens extracted from the current project's HTML `\u003Chead>`. Tokens from a previous project are NOT acceptable.**\n\n1. **Extract `tailwind.config`**: Open each downloaded HTML file and locate the `tailwind.config` object in the `\u003Chead>` `\u003Cscript>` block. Extract:\n   - All color tokens\n   - Font families\n   - Spacing values\n   - Border radius values\n   - Font size\u002Ftypography tokens\n2. **Sync `resources\u002Fstyle-guide.json`**: Overwrite the file with the extracted tokens from THIS project. The style guide MUST match the Stitch project being converted.\n3. **Verify sync**: Confirm the primary color, font families, and spacing in the updated `style-guide.json` match what you extracted.\n\n### Anti-patterns for Phase 2\n- ❌ Using `style-guide.json` as-is without verifying it matches the current project.\n- ❌ Using hardcoded hex values in components instead of theme-mapped classes.\n\n## Phase 3: Architectural rules\n\n> **GATE: Every component MUST satisfy ALL of the following rules. Violations will cause `npm run validate` to fail.**\n\n* **Modular components**: Break the design into independent files. **Each reusable UI pattern** (cards, badges, pagination, search bars) MUST be extracted into its own component in `src\u002Fcomponents\u002F`. Monolithic page files that contain everything are PROHIBITED.\n* **Logic isolation**: Move event handlers and business logic into custom hooks in `src\u002Fhooks\u002F`. Examples: pagination logic → `usePagination`, filtering → `useFilter`.\n* **Data decoupling**: Move ALL static text, image URLs, and lists into `src\u002Fdata\u002FmockData.ts`. No hardcoded content in components.\n* **Type safety**: EVERY component file (including pages) MUST include a `Readonly` TypeScript interface named `[ComponentName]Props`. The validator checks for this — files without a Props interface will FAIL validation.\n* **Project specific**: Focus on the target project's needs and constraints. Leave Google license headers out of the generated React components.\n* **Navigation wiring**: Stitch screens are standalone pages with `href=\"#\"` placeholder links. When building a multi-page React app:\n    * Replace ALL `href=\"#\"` anchors with React Router `\u003CLink>` components pointing to the correct routes.\n    * **Always make the app logo\u002Ftitle in the TopAppBar a `\u003CLink to=\"\u002F\">`** so users can navigate home from any page. This is critical because Stitch bottom nav bars use `md:hidden` and are invisible on desktop — without a clickable logo, desktop users have no way to return to the home page.\n    * Wire the bottom nav items and sidebar nav items to their corresponding routes using `\u003CLink>` with active-state highlighting based on `useLocation()`.\n* **Style mapping**: Use theme-mapped Tailwind classes from the synced `style-guide.json`. No arbitrary hex codes.\n* **Dark mode**: Apply `dark:` variants to ALL color classes throughout every component.\n\n### Anti-patterns for Phase 3\n- ❌ Putting all UI in a single monolithic page file.\n- ❌ Inline event handlers or business logic without hooks.\n- ❌ Hardcoding text, URLs, or data in component files.\n- ❌ Components without a `[Name]Props` interface.\n- ❌ Using hex color values instead of theme tokens.\n- ❌ Leaving `href=\"#\"` links unconverted.\n\n## Phase 4: Execution steps\n\n> **GATE: Phase 4 verification, audits, and validation checks are optional. You MUST ask the user's permission to proceed with validation scripts, running local dev servers, or automated browser testing.**\n\n1. **Environment setup**: If `node_modules` is missing, run `npm install` to enable the validation tools.\n2. **Data layer**: Create `src\u002Fdata\u002FmockData.ts` based on the design content.\n3. **Component drafting**: Use `resources\u002Fcomponent-template.tsx` as a base. Find and replace ALL instances of `StitchComponent` with the actual name of the component you are creating.\n4. **Application wiring**: Update the project entry point (like `App.tsx`) to render the new components.\n5. **Quality check (Optional - Ask User first)**:\n    * Run `npm run validate \u003Cfile_path>` for **EVERY** `.tsx` file in `src\u002Fcomponents\u002F` and `src\u002Fpages\u002F` to report component validity.\n    * Run `tsc --noEmit` to verify TypeScript compile status.\n    * Check output against `resources\u002Farchitecture-checklist.md`.\n    * Obtain permission before starting the dev server with `npm run dev` or initiating visual browser audits to verify the live result.\n\n### Anti-patterns for Phase 4\n- ❌ Commencing dev server start or browser audits without user consent.\n- ❌ Declaring task \"done\" without verifying code compiles.\n\n## Troubleshooting\n* **Fetch errors**: Ensure the URL is quoted in the bash command to prevent shell errors.\n* **Validation errors**: Review the AST report and fix any missing interfaces or hardcoded styles. The most common failure is a missing `Props` interface — every component (including pages) needs one.\n* **Dead navigation links**: Stitch HTML uses `href=\"#\"` placeholders everywhere. Every `\u003Ca href=\"#\">` must be converted to a `\u003CLink to=\"\u002Froute\">` with a real route. Verify all nav items are clickable and lead to the correct page.\n* **Stale style-guide.json**: If colors or fonts look wrong, the `style-guide.json` likely has tokens from a different project. Re-extract from the current HTML `\u003Chead>`.","# Stitch to React Components\n\nYou are a frontend engineer focused on transforming designs into clean React code or syncing\u002Fupdating existing React components to align with the latest Stitch designs. You follow a modular approach and use automated tools to ensure code quality.\n\n> **CRITICAL: Every step in this skill is MANDATORY. Do NOT skip any step or take shortcuts. Each section contains a GATE that must be satisfied before proceeding.**\n\n## Phase 1: Retrieval and networking\n\n> **GATE: Phase 1 is complete ONLY when all screens have been downloaded via `scripts\u002Ffetch-stitch.sh` AND visually audited. Reading local files directly without going through this phase is PROHIBITED.**\n\n1. **Namespace discovery**: Run `list_tools` to find the Stitch MCP prefix. Use this prefix (e.g., `stitch:`) for all subsequent calls.\n2. **Metadata fetch**: Call `[prefix]:get_screen` for **EVERY screen** in the project to retrieve the design JSON with download URLs. Do NOT skip any screen.\n3. **Check for existing designs**: Before downloading, check if `.stitch\u002Fdesigns\u002F{page}.html` and `.stitch\u002Fdesigns\u002F{page}.png` already exist:\n   - **If files exist**: Ask the user whether to refresh the designs from the Stitch project using the MCP, or reuse the existing local files. **You MUST ask — do not assume.**  Only re-download if the user confirms.\n   - **If files do not exist**: Proceed to step 4.\n4. **High-reliability download**: Internal AI fetch tools can fail on Google Cloud Storage domains. You MUST use the provided script.\n   - **HTML**: `bash scripts\u002Ffetch-stitch.sh \"[htmlCode.downloadUrl]\" \".stitch\u002Fdesigns\u002F{page}.html\"`\n   - **Screenshot**: Append `=w{width}` to the screenshot URL first, where `{width}` is the `width` value from the screen metadata (Google CDN serves low-res thumbnails by default). Then run: `bash scripts\u002Ffetch-stitch.sh \"[screenshot.downloadUrl]=w{width}\" \".stitch\u002Fdesigns\u002F{page}.png\"`\n   - This script handles the necessary redirects and security handshakes.\n5. **Visual audit**: Review the downloaded screenshot (`.stitch\u002Fdesigns\u002F{page}.png`) to confirm design intent and layout details. **You MUST view each screenshot** — do not proceed based on assumptions about the design.\n6. **Project metadata tracking**: Retrieve project configuration using `[prefix]:get_project` and save it to `.stitch\u002Fmetadata.json` (inside the app folder, and mirrored in the workspace root). Ensure it has:\n   - `projectId`, `title`, `deviceType`\n   - A `Last Sync Time` field matching the current sync ISO execution time\n   - A `screens` map detailing each screen's ID, label, sourceScreen reference, dimensions, and canvasPosition.\n\n### Anti-patterns for Phase 1\n- ❌ Reading `.stitch\u002Fdesigns\u002F*.html` directly without calling MCP `get_screen` first.\n- ❌ Skipping the `fetch-stitch.sh` download script.\n- ❌ Not asking the user when existing files are found.\n- ❌ Skipping the visual audit of `.png` screenshots.\n- ❌ Failing to generate or update `.stitch\u002Fmetadata.json` and its `Last Sync Time` field upon syncing.\n\n## Phase 2: Style extraction\n\n> **GATE: Phase 2 is complete ONLY when `resources\u002Fstyle-guide.json` has been updated with tokens extracted from the current project's HTML `\u003Chead>`. Tokens from a previous project are NOT acceptable.**\n\n1. **Extract `tailwind.config`**: Open each downloaded HTML file and locate the `tailwind.config` object in the `\u003Chead>` `\u003Cscript>` block. Extract:\n   - All color tokens\n   - Font families\n   - Spacing values\n   - Border radius values\n   - Font size\u002Ftypography tokens\n2. **Sync `resources\u002Fstyle-guide.json`**: Overwrite the file with the extracted tokens from THIS project. The style guide MUST match the Stitch project being converted.\n3. **Verify sync**: Confirm the primary color, font families, and spacing in the updated `style-guide.json` match what you extracted.\n\n### Anti-patterns for Phase 2\n- ❌ Using `style-guide.json` as-is without verifying it matches the current project.\n- ❌ Using hardcoded hex values in components instead of theme-mapped classes.\n\n## Phase 3: Architectural rules\n\n> **GATE: Every component MUST satisfy ALL of the following rules. Violations will cause `npm run validate` to fail.**\n\n* **Modular components**: Break the design into independent files. **Each reusable UI pattern** (cards, badges, pagination, search bars) MUST be extracted into its own component in `src\u002Fcomponents\u002F`. Monolithic page files that contain everything are PROHIBITED.\n* **Logic isolation**: Move event handlers and business logic into custom hooks in `src\u002Fhooks\u002F`. Examples: pagination logic → `usePagination`, filtering → `useFilter`.\n* **Data decoupling**: Move ALL static text, image URLs, and lists into `src\u002Fdata\u002FmockData.ts`. No hardcoded content in components.\n* **Type safety**: EVERY component file (including pages) MUST include a `Readonly` TypeScript interface named `[ComponentName]Props`. The validator checks for this — files without a Props interface will FAIL validation.\n* **Project specific**: Focus on the target project's needs and constraints. Leave Google license headers out of the generated React components.\n* **Navigation wiring**: Stitch screens are standalone pages with `href=\"#\"` placeholder links. When building a multi-page React app:\n    * Replace ALL `href=\"#\"` anchors with React Router `\u003CLink>` components pointing to the correct routes.\n    * **Always make the app logo\u002Ftitle in the TopAppBar a `\u003CLink to=\"\u002F\">`** so users can navigate home from any page. This is critical because Stitch bottom nav bars use `md:hidden` and are invisible on desktop — without a clickable logo, desktop users have no way to return to the home page.\n    * Wire the bottom nav items and sidebar nav items to their corresponding routes using `\u003CLink>` with active-state highlighting based on `useLocation()`.\n* **Style mapping**: Use theme-mapped Tailwind classes from the synced `style-guide.json`. No arbitrary hex codes.\n* **Dark mode**: Apply `dark:` variants to ALL color classes throughout every component.\n\n### Anti-patterns for Phase 3\n- ❌ Putting all UI in a single monolithic page file.\n- ❌ Inline event handlers or business logic without hooks.\n- ❌ Hardcoding text, URLs, or data in component files.\n- ❌ Components without a `[Name]Props` interface.\n- ❌ Using hex color values instead of theme tokens.\n- ❌ Leaving `href=\"#\"` links unconverted.\n\n## Phase 4: Execution steps\n\n> **GATE: Phase 4 verification, audits, and validation checks are optional. You MUST ask the user's permission to proceed with validation scripts, running local dev servers, or automated browser testing.**\n\n1. **Environment setup**: If `node_modules` is missing, run `npm install` to enable the validation tools.\n2. **Data layer**: Create `src\u002Fdata\u002FmockData.ts` based on the design content.\n3. **Component drafting**: Use `resources\u002Fcomponent-template.tsx` as a base. Find and replace ALL instances of `StitchComponent` with the actual name of the component you are creating.\n4. **Application wiring**: Update the project entry point (like `App.tsx`) to render the new components.\n5. **Quality check (Optional - Ask User first)**:\n    * Run `npm run validate \u003Cfile_path>` for **EVERY** `.tsx` file in `src\u002Fcomponents\u002F` and `src\u002Fpages\u002F` to report component validity.\n    * Run `tsc --noEmit` to verify TypeScript compile status.\n    * Check output against `resources\u002Farchitecture-checklist.md`.\n    * Obtain permission before starting the dev server with `npm run dev` or initiating visual browser audits to verify the live result.\n\n### Anti-patterns for Phase 4\n- ❌ Commencing dev server start or browser audits without user consent.\n- ❌ Declaring task \"done\" without verifying code compiles.\n\n## Troubleshooting\n* **Fetch errors**: Ensure the URL is quoted in the bash command to prevent shell errors.\n* **Validation errors**: Review the AST report and fix any missing interfaces or hardcoded styles. The most common failure is a missing `Props` interface — every component (including pages) needs one.\n* **Dead navigation links**: Stitch HTML uses `href=\"#\"` placeholders everywhere. Every `\u003Ca href=\"#\">` must be converted to a `\u003CLink to=\"\u002Froute\">` with a real route. Verify all nav items are clickable and lead to the correct page.\n* **Stale style-guide.json**: If colors or fonts look wrong, the `style-guide.json` likely has tokens from a different project. Re-extract from the current HTML `\u003Chead>`.",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fstitch-react-components",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-react-components",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill stitch-react-components",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill stitch-react-components","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002FSKILL.md",true,[46,52,58,62,66,70,74,78,82,88],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"examples\u002Fgold-standard-card.tsx","OTHER","其他",1995,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fexamples\u002Fgold-standard-card.tsx",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"package-lock.json","REFERENCE","参考文档",7204,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fpackage-lock.json",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"package.json",355,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fpackage.json",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"README.md",1369,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002FREADME.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"resources\u002Farchitecture-checklist.md",613,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fresources\u002Farchitecture-checklist.md",{"path":71,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":72,"sourceHtmlUrl":73},"resources\u002Fcomponent-template.tsx",1049,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fresources\u002Fcomponent-template.tsx",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"resources\u002Fstitch-api-reference.md",1225,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fresources\u002Fstitch-api-reference.md",{"path":79,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":80,"sourceHtmlUrl":81},"resources\u002Fstyle-guide.json",496,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fresources\u002Fstyle-guide.json",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Ffetch-stitch.sh","SCRIPT","脚本",1009,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fscripts\u002Ffetch-stitch.sh",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fvalidate.js",2758,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fstitch-react-components\u002Fscripts\u002Fvalidate.js",[93,100,107,114,121,128],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"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",[],[]]