[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75B7ZPCPVX6RPXPABAVJJS0":3,"skill-same:01M75B7ZPCPVX6RPXPABAVJJS0":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75B7ZPCPVX6RPXPABAVJJS0","stitch-loop",null,"Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern","ruake\u002FAWARE","ruake","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253885939?v=4","01M75AVBM7FRFTS61RZRNMZB6C","01M75AVBMYHD7500NHVANF1HKM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: stitch-loop\ndescription: Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern\nallowed-tools:\n  - \"stitch*:*\"\n  - \"chrome*:*\"\n  - \"Read\"\n  - \"Write\"\n  - \"Bash\"\n---\n\n# Stitch Build Loop\n\nYou are an **autonomous frontend builder** participating in an iterative site-building loop. Your goal is to generate a page using Stitch, integrate it into the site, and prepare instructions for the next iteration.\n\n## Overview\n\nThe Build Loop pattern enables continuous, autonomous website development through a \"baton\" system. Each iteration:\n1. Reads the current task from a baton file (`.stitch\u002Fnext-prompt.md`)\n2. Generates a page using Stitch MCP tools\n3. Integrates the page into the site structure\n4. Writes the next task to the baton file for the next iteration\n\n## Prerequisites\n\n**Required:**\n- Access to the Stitch MCP Server\n- A Stitch project (existing or will be created)\n- A `.stitch\u002FDESIGN.md` file (generate one using the `design-md` skill if needed)\n- A `.stitch\u002FSITE.md` file documenting the site vision and roadmap\n\n**Optional:**\n- Chrome DevTools MCP Server — enables visual verification of generated pages\n\n## The Baton System\n\nThe `.stitch\u002Fnext-prompt.md` file acts as a relay baton between iterations:\n\n```markdown\n---\npage: about\n---\nA page describing how jules.top tracking works.\n\n**DESIGN SYSTEM (REQUIRED):**\n[Copy from .stitch\u002FDESIGN.md Section 6]\n\n**Page Structure:**\n1. Header with navigation\n2. Explanation of tracking methodology\n3. Footer with links\n```\n\n**Critical rules:**\n- The `page` field in YAML frontmatter determines the output filename\n- The prompt content must include the design system block from `.stitch\u002FDESIGN.md`\n- You MUST update this file before completing your work to continue the loop\n\n## Execution Protocol\n\n### Step 1: Read the Baton\n\nParse `.stitch\u002Fnext-prompt.md` to extract:\n- **Page name** from the `page` frontmatter field\n- **Prompt content** from the markdown body\n\n### Step 2: Consult Context Files\n\nBefore generating, read these files:\n\n| File | Purpose |\n|------|---------|\n| `.stitch\u002FSITE.md` | Site vision, **Stitch Project ID**, existing pages (sitemap), roadmap |\n| `.stitch\u002FDESIGN.md` | Required visual style for Stitch prompts |\n\n**Important checks:**\n- Section 4 (Sitemap) — Do NOT recreate pages that already exist\n- Section 5 (Roadmap) — Pick tasks from here if backlog exists\n- Section 6 (Creative Freedom) — Ideas for new pages if roadmap is empty\n\n### Step 3: Generate with Stitch\n\nUse the Stitch MCP tools to generate the page:\n\n1. **Discover namespace**: Run `list_tools` to find the Stitch MCP prefix\n2. **Get or create project**: \n   - If `.stitch\u002Fmetadata.json` exists, use the `projectId` from it\n   - Otherwise, call `[prefix]:create_project`, then call `[prefix]:get_project` to retrieve full project details, and save them to `.stitch\u002Fmetadata.json` (see schema below)\n   - After generating each screen, call `[prefix]:get_project` again and update the `screens` map in `.stitch\u002Fmetadata.json` with each screen's full metadata (id, sourceScreen, dimensions, canvas position)\n3. **Generate screen**: Call `[prefix]:generate_screen_from_text` with:\n   - `projectId`: The project ID\n   - `prompt`: The full prompt from the baton (including design system block)\n   - `deviceType`: `DESKTOP` (or as specified)\n4. **Retrieve assets**: 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 or reuse the existing local files. Only re-download if the user confirms.\n   - **If files do not exist**: Proceed with download:\n     - `htmlCode.downloadUrl` — Download and save as `.stitch\u002Fdesigns\u002F{page}.html`\n      - `screenshot.downloadUrl` — Append `=w{width}` to the URL before downloading, where `{width}` is the `width` value from the screen metadata (Google CDN serves low-res thumbnails by default). Save as `.stitch\u002Fdesigns\u002F{page}.png`\n\n### Step 4: Integrate into Site\n\n1. Move generated HTML from `.stitch\u002Fdesigns\u002F{page}.html` to `site\u002Fpublic\u002F{page}.html`\n2. Fix any asset paths to be relative to the public folder\n3. Update navigation:\n   - Find existing placeholder links (e.g., `href=\"#\"`) and wire them to the new page\n   - Add the new page to the global navigation if appropriate\n4. Ensure consistent headers\u002Ffooters across all pages\n\n### Step 4.5: Visual Verification (Optional)\n\nIf the **Chrome DevTools MCP Server** is available, verify the generated page:\n\n1. **Check availability**: Run `list_tools` to see if `chrome*` tools are present\n2. **Start dev server**: Use Bash to start a local server (e.g., `npx serve site\u002Fpublic`)\n3. **Navigate to page**: Call `[chrome_prefix]:navigate` to open `http:\u002F\u002Flocalhost:3000\u002F{page}.html`\n4. **Capture screenshot**: Call `[chrome_prefix]:screenshot` to capture the rendered page\n5. **Visual comparison**: Compare against the Stitch screenshot (`.stitch\u002Fdesigns\u002F{page}.png`) for fidelity\n6. **Stop server**: Terminate the dev server process\n\n> **Note:** This step is optional. If Chrome DevTools MCP is not installed, skip to Step 5.\n\n### Step 5: Update Site Documentation\n\nModify `.stitch\u002FSITE.md`:\n- Add the new page to Section 4 (Sitemap) with `[x]`\n- Remove any idea you consumed from Section 6 (Creative Freedom)\n- Update Section 5 (Roadmap) if you completed a backlog item\n\n### Step 6: Prepare the Next Baton (Critical)\n\n**You MUST update `.stitch\u002Fnext-prompt.md` before completing.** This keeps the loop alive.\n\n1. **Decide the next page**: \n   - Check `.stitch\u002FSITE.md` Section 5 (Roadmap) for pending items\n   - If empty, pick from Section 6 (Creative Freedom)\n   - Or invent something new that fits the site vision\n2. **Write the baton** with proper YAML frontmatter:\n\n```markdown\n---\npage: achievements\n---\nA competitive achievements page showing developer badges and milestones.\n\n**DESIGN SYSTEM (REQUIRED):**\n[Copy the entire design system block from .stitch\u002FDESIGN.md]\n\n**Page Structure:**\n1. Header with title and navigation\n2. Badge grid showing unlocked\u002Flocked states\n3. Progress bars for milestone tracking\n```\n\n## File Structure Reference\n\n```\nproject\u002F\n├── .stitch\u002F\n│   ├── metadata.json   # Stitch project & screen IDs (persist this!)\n│   ├── DESIGN.md       # Visual design system (from design-md skill)\n│   ├── SITE.md         # Site vision, sitemap, roadmap\n│   ├── next-prompt.md  # The baton — current task\n│   └── designs\u002F        # Staging area for Stitch output\n│       ├── {page}.html\n│       └── {page}.png\n└── site\u002Fpublic\u002F        # Production pages\n    ├── index.html\n    └── {page}.html\n```\n\n### `.stitch\u002Fmetadata.json` Schema\n\nThis file persists all Stitch identifiers so future iterations can reference them for edits or variants. Populate it by calling `[prefix]:get_project` after creating a project or generating screens.\n\n```json\n{\n  \"name\": \"projects\u002F6139132077804554844\",\n  \"projectId\": \"6139132077804554844\",\n  \"title\": \"My App\",\n  \"visibility\": \"PRIVATE\",\n  \"createTime\": \"2026-03-04T23:11:25.514932Z\",\n  \"updateTime\": \"2026-03-04T23:34:40.400007Z\",\n  \"projectType\": \"PROJECT_DESIGN\",\n  \"origin\": \"STITCH\",\n  \"deviceType\": \"MOBILE\",\n  \"designTheme\": {\n    \"colorMode\": \"DARK\",\n    \"font\": \"INTER\",\n    \"roundness\": \"ROUND_EIGHT\",\n    \"customColor\": \"#40baf7\",\n    \"saturation\": 3\n  },\n  \"screens\": {\n    \"index\": {\n      \"id\": \"d7237c7d78f44befa4f60afb17c818c1\",\n      \"sourceScreen\": \"projects\u002F6139132077804554844\u002Fscreens\u002Fd7237c7d78f44befa4f60afb17c818c1\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 390,\n      \"height\": 1249\n    },\n    \"about\": {\n      \"id\": \"bf6a3fe5c75348e58cf21fc7a9ddeafb\",\n      \"sourceScreen\": \"projects\u002F6139132077804554844\u002Fscreens\u002Fbf6a3fe5c75348e58cf21fc7a9ddeafb\",\n      \"x\": 549,\n      \"y\": 0,\n      \"width\": 390,\n      \"height\": 1159\n    }\n  },\n  \"metadata\": {\n    \"userRole\": \"OWNER\"\n  }\n}\n```\n\n| Field | Description |\n|-------|-------------|\n| `name` | Full resource name (`projects\u002F{id}`) |\n| `projectId` | Stitch project ID (from `create_project` or `get_project`) |\n| `title` | Human-readable project title |\n| `designTheme` | Design system tokens: color mode, font, roundness, custom color, saturation |\n| `deviceType` | Target device: `MOBILE`, `DESKTOP`, `TABLET` |\n| `screens` | Map of page name → screen object. Each screen includes `id`, `sourceScreen` (resource path for MCP calls), canvas position (`x`, `y`), and dimensions (`width`, `height`) |\n| `metadata.userRole` | User's role on the project (`OWNER`, `EDITOR`, `VIEWER`) |\n\n## Orchestration Options\n\nThe loop can be driven by different orchestration layers:\n\n| Method | How it works |\n|--------|--------------|\n| **CI\u002FCD** | GitHub Actions triggers on `.stitch\u002Fnext-prompt.md` changes |\n| **Human-in-loop** | Developer reviews each iteration before continuing |\n| **Agent chains** | One agent dispatches to another (e.g., Jules API) |\n| **Manual** | Developer runs the agent repeatedly with the same repo |\n\nThe skill is orchestration-agnostic — focus on the pattern, not the trigger mechanism.\n\n## Design System Integration\n\nThis skill works best with the `design-md` skill:\n\n1. **First time setup**: Generate `.stitch\u002FDESIGN.md` using the `design-md` skill from an existing Stitch screen\n2. **Every iteration**: Copy Section 6 (\"Design System Notes for Stitch Generation\") into your baton prompt\n3. **Consistency**: All generated pages will share the same visual language\n\n## Common Pitfalls\n\n- ❌ Forgetting to update `.stitch\u002Fnext-prompt.md` (breaks the loop)\n- ❌ Recreating a page that already exists in the sitemap\n- ❌ Not including the design system block from `.stitch\u002FDESIGN.md` in the prompt\n- ❌ Leaving placeholder links (`href=\"#\"`) instead of wiring real navigation\n- ❌ Forgetting to persist `.stitch\u002Fmetadata.json` after creating a new project\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Stitch generation fails | Check that the prompt includes the design system block |\n| Inconsistent styles | Ensure `.stitch\u002FDESIGN.md` is up-to-date and copied correctly |\n| Loop stalls | Verify `.stitch\u002Fnext-prompt.md` was updated with valid frontmatter |\n| Navigation broken | Check all internal links use correct relative paths |\n","# Stitch Build Loop\n\nYou are an **autonomous frontend builder** participating in an iterative site-building loop. Your goal is to generate a page using Stitch, integrate it into the site, and prepare instructions for the next iteration.\n\n## Overview\n\nThe Build Loop pattern enables continuous, autonomous website development through a \"baton\" system. Each iteration:\n1. Reads the current task from a baton file (`.stitch\u002Fnext-prompt.md`)\n2. Generates a page using Stitch MCP tools\n3. Integrates the page into the site structure\n4. Writes the next task to the baton file for the next iteration\n\n## Prerequisites\n\n**Required:**\n- Access to the Stitch MCP Server\n- A Stitch project (existing or will be created)\n- A `.stitch\u002FDESIGN.md` file (generate one using the `design-md` skill if needed)\n- A `.stitch\u002FSITE.md` file documenting the site vision and roadmap\n\n**Optional:**\n- Chrome DevTools MCP Server — enables visual verification of generated pages\n\n## The Baton System\n\nThe `.stitch\u002Fnext-prompt.md` file acts as a relay baton between iterations:\n\n```markdown\n---\npage: about\n---\nA page describing how jules.top tracking works.\n\n**DESIGN SYSTEM (REQUIRED):**\n[Copy from .stitch\u002FDESIGN.md Section 6]\n\n**Page Structure:**\n1. Header with navigation\n2. Explanation of tracking methodology\n3. Footer with links\n```\n\n**Critical rules:**\n- The `page` field in YAML frontmatter determines the output filename\n- The prompt content must include the design system block from `.stitch\u002FDESIGN.md`\n- You MUST update this file before completing your work to continue the loop\n\n## Execution Protocol\n\n### Step 1: Read the Baton\n\nParse `.stitch\u002Fnext-prompt.md` to extract:\n- **Page name** from the `page` frontmatter field\n- **Prompt content** from the markdown body\n\n### Step 2: Consult Context Files\n\nBefore generating, read these files:\n\n| File | Purpose |\n|------|---------|\n| `.stitch\u002FSITE.md` | Site vision, **Stitch Project ID**, existing pages (sitemap), roadmap |\n| `.stitch\u002FDESIGN.md` | Required visual style for Stitch prompts |\n\n**Important checks:**\n- Section 4 (Sitemap) — Do NOT recreate pages that already exist\n- Section 5 (Roadmap) — Pick tasks from here if backlog exists\n- Section 6 (Creative Freedom) — Ideas for new pages if roadmap is empty\n\n### Step 3: Generate with Stitch\n\nUse the Stitch MCP tools to generate the page:\n\n1. **Discover namespace**: Run `list_tools` to find the Stitch MCP prefix\n2. **Get or create project**: \n   - If `.stitch\u002Fmetadata.json` exists, use the `projectId` from it\n   - Otherwise, call `[prefix]:create_project`, then call `[prefix]:get_project` to retrieve full project details, and save them to `.stitch\u002Fmetadata.json` (see schema below)\n   - After generating each screen, call `[prefix]:get_project` again and update the `screens` map in `.stitch\u002Fmetadata.json` with each screen's full metadata (id, sourceScreen, dimensions, canvas position)\n3. **Generate screen**: Call `[prefix]:generate_screen_from_text` with:\n   - `projectId`: The project ID\n   - `prompt`: The full prompt from the baton (including design system block)\n   - `deviceType`: `DESKTOP` (or as specified)\n4. **Retrieve assets**: 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 or reuse the existing local files. Only re-download if the user confirms.\n   - **If files do not exist**: Proceed with download:\n     - `htmlCode.downloadUrl` — Download and save as `.stitch\u002Fdesigns\u002F{page}.html`\n      - `screenshot.downloadUrl` — Append `=w{width}` to the URL before downloading, where `{width}` is the `width` value from the screen metadata (Google CDN serves low-res thumbnails by default). Save as `.stitch\u002Fdesigns\u002F{page}.png`\n\n### Step 4: Integrate into Site\n\n1. Move generated HTML from `.stitch\u002Fdesigns\u002F{page}.html` to `site\u002Fpublic\u002F{page}.html`\n2. Fix any asset paths to be relative to the public folder\n3. Update navigation:\n   - Find existing placeholder links (e.g., `href=\"#\"`) and wire them to the new page\n   - Add the new page to the global navigation if appropriate\n4. Ensure consistent headers\u002Ffooters across all pages\n\n### Step 4.5: Visual Verification (Optional)\n\nIf the **Chrome DevTools MCP Server** is available, verify the generated page:\n\n1. **Check availability**: Run `list_tools` to see if `chrome*` tools are present\n2. **Start dev server**: Use Bash to start a local server (e.g., `npx serve site\u002Fpublic`)\n3. **Navigate to page**: Call `[chrome_prefix]:navigate` to open `http:\u002F\u002Flocalhost:3000\u002F{page}.html`\n4. **Capture screenshot**: Call `[chrome_prefix]:screenshot` to capture the rendered page\n5. **Visual comparison**: Compare against the Stitch screenshot (`.stitch\u002Fdesigns\u002F{page}.png`) for fidelity\n6. **Stop server**: Terminate the dev server process\n\n> **Note:** This step is optional. If Chrome DevTools MCP is not installed, skip to Step 5.\n\n### Step 5: Update Site Documentation\n\nModify `.stitch\u002FSITE.md`:\n- Add the new page to Section 4 (Sitemap) with `[x]`\n- Remove any idea you consumed from Section 6 (Creative Freedom)\n- Update Section 5 (Roadmap) if you completed a backlog item\n\n### Step 6: Prepare the Next Baton (Critical)\n\n**You MUST update `.stitch\u002Fnext-prompt.md` before completing.** This keeps the loop alive.\n\n1. **Decide the next page**: \n   - Check `.stitch\u002FSITE.md` Section 5 (Roadmap) for pending items\n   - If empty, pick from Section 6 (Creative Freedom)\n   - Or invent something new that fits the site vision\n2. **Write the baton** with proper YAML frontmatter:\n\n```markdown\n---\npage: achievements\n---\nA competitive achievements page showing developer badges and milestones.\n\n**DESIGN SYSTEM (REQUIRED):**\n[Copy the entire design system block from .stitch\u002FDESIGN.md]\n\n**Page Structure:**\n1. Header with title and navigation\n2. Badge grid showing unlocked\u002Flocked states\n3. Progress bars for milestone tracking\n```\n\n## File Structure Reference\n\n```\nproject\u002F\n├── .stitch\u002F\n│   ├── metadata.json   # Stitch project & screen IDs (persist this!)\n│   ├── DESIGN.md       # Visual design system (from design-md skill)\n│   ├── SITE.md         # Site vision, sitemap, roadmap\n│   ├── next-prompt.md  # The baton — current task\n│   └── designs\u002F        # Staging area for Stitch output\n│       ├── {page}.html\n│       └── {page}.png\n└── site\u002Fpublic\u002F        # Production pages\n    ├── index.html\n    └── {page}.html\n```\n\n### `.stitch\u002Fmetadata.json` Schema\n\nThis file persists all Stitch identifiers so future iterations can reference them for edits or variants. Populate it by calling `[prefix]:get_project` after creating a project or generating screens.\n\n```json\n{\n  \"name\": \"projects\u002F6139132077804554844\",\n  \"projectId\": \"6139132077804554844\",\n  \"title\": \"My App\",\n  \"visibility\": \"PRIVATE\",\n  \"createTime\": \"2026-03-04T23:11:25.514932Z\",\n  \"updateTime\": \"2026-03-04T23:34:40.400007Z\",\n  \"projectType\": \"PROJECT_DESIGN\",\n  \"origin\": \"STITCH\",\n  \"deviceType\": \"MOBILE\",\n  \"designTheme\": {\n    \"colorMode\": \"DARK\",\n    \"font\": \"INTER\",\n    \"roundness\": \"ROUND_EIGHT\",\n    \"customColor\": \"#40baf7\",\n    \"saturation\": 3\n  },\n  \"screens\": {\n    \"index\": {\n      \"id\": \"d7237c7d78f44befa4f60afb17c818c1\",\n      \"sourceScreen\": \"projects\u002F6139132077804554844\u002Fscreens\u002Fd7237c7d78f44befa4f60afb17c818c1\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 390,\n      \"height\": 1249\n    },\n    \"about\": {\n      \"id\": \"bf6a3fe5c75348e58cf21fc7a9ddeafb\",\n      \"sourceScreen\": \"projects\u002F6139132077804554844\u002Fscreens\u002Fbf6a3fe5c75348e58cf21fc7a9ddeafb\",\n      \"x\": 549,\n      \"y\": 0,\n      \"width\": 390,\n      \"height\": 1159\n    }\n  },\n  \"metadata\": {\n    \"userRole\": \"OWNER\"\n  }\n}\n```\n\n| Field | Description |\n|-------|-------------|\n| `name` | Full resource name (`projects\u002F{id}`) |\n| `projectId` | Stitch project ID (from `create_project` or `get_project`) |\n| `title` | Human-readable project title |\n| `designTheme` | Design system tokens: color mode, font, roundness, custom color, saturation |\n| `deviceType` | Target device: `MOBILE`, `DESKTOP`, `TABLET` |\n| `screens` | Map of page name → screen object. Each screen includes `id`, `sourceScreen` (resource path for MCP calls), canvas position (`x`, `y`), and dimensions (`width`, `height`) |\n| `metadata.userRole` | User's role on the project (`OWNER`, `EDITOR`, `VIEWER`) |\n\n## Orchestration Options\n\nThe loop can be driven by different orchestration layers:\n\n| Method | How it works |\n|--------|--------------|\n| **CI\u002FCD** | GitHub Actions triggers on `.stitch\u002Fnext-prompt.md` changes |\n| **Human-in-loop** | Developer reviews each iteration before continuing |\n| **Agent chains** | One agent dispatches to another (e.g., Jules API) |\n| **Manual** | Developer runs the agent repeatedly with the same repo |\n\nThe skill is orchestration-agnostic — focus on the pattern, not the trigger mechanism.\n\n## Design System Integration\n\nThis skill works best with the `design-md` skill:\n\n1. **First time setup**: Generate `.stitch\u002FDESIGN.md` using the `design-md` skill from an existing Stitch screen\n2. **Every iteration**: Copy Section 6 (\"Design System Notes for Stitch Generation\") into your baton prompt\n3. **Consistency**: All generated pages will share the same visual language\n\n## Common Pitfalls\n\n- ❌ Forgetting to update `.stitch\u002Fnext-prompt.md` (breaks the loop)\n- ❌ Recreating a page that already exists in the sitemap\n- ❌ Not including the design system block from `.stitch\u002FDESIGN.md` in the prompt\n- ❌ Leaving placeholder links (`href=\"#\"`) instead of wiring real navigation\n- ❌ Forgetting to persist `.stitch\u002Fmetadata.json` after creating a new project\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Stitch generation fails | Check that the prompt includes the design system block |\n| Inconsistent styles | Ensure `.stitch\u002FDESIGN.md` is up-to-date and copied correctly |\n| Loop stalls | Verify `.stitch\u002Fnext-prompt.md` was updated with valid frontmatter |\n| Navigation broken | Check all internal links use correct relative paths |\n",{"name":5,"description":7,"allowed-tools":23},[24,25,26,27,28],"stitch*:*","chrome*:*","Read","Write","Bash","main","6184979e01f673905139589c194eab38198db2f7",".agents\u002Fskills\u002Fstitch-loop",1,"https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE","https:\u002F\u002Fruake.github.io\u002FAWARE","https:\u002F\u002Fgithub.com\u002Fruake","2026-11-15 04:27:27",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add ruake\u002FAWARE --skill stitch-loop",{"tool":43,"command":44},"bunx","bunx skills add ruake\u002FAWARE --skill stitch-loop",{"tool":46,"command":47},"pnpm","pnpm dlx skills add ruake\u002FAWARE --skill stitch-loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002FSKILL.md",true,[51,57,61,65,69],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"examples\u002Fnext-prompt.md","REFERENCE","参考文档",1236,"https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002Fexamples\u002Fnext-prompt.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"examples\u002FSITE.md",3255,"https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002Fexamples\u002FSITE.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"README.md",1465,"https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002FREADME.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"resources\u002Fbaton-schema.md",1663,"https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002Fresources\u002Fbaton-schema.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"resources\u002Fsite-template.md",2969,"https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstitch-loop\u002Fresources\u002Fsite-template.md",[74,80,87,94,101,107],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75BPBYT89TEE87CGBDX2KF5","xlsx","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75BPA000S9MTH5MY7CZNYYQ","writing-plans","Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste.","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75BP80ETH9GYVRH8A7QPCSG","web-design-guidelines","Review files for compliance with Web Interface Guidelines.","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M75BP5XG8SX5Q2WWZB6QRVFT","web-component-design","Build reusable, maintainable UI components using modern frameworks with clean composition patterns and styling approache","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-component-design\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M75BP4B1FC4V81QR1VB56H1E","web-artifacts-builder","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"01M75BP1XVRW8WQ2XXAJBAYV2V","vueuse-functions","This skill is a decision-and-implementation guide for VueUse composables in Vue.js \u002F Nuxt projects. It maps requirements","https:\u002F\u002Fgithub.com\u002Fruake\u002FAWARE\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fvueuse-functions\u002FSKILL.md",[],[]]