[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PR2Z6SVEK4S3SYPNJX84ST":3,"skill-same:01M6PR2Z6SVEK4S3SYPNJX84ST":82},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6PR2Z6SVEK4S3SYPNJX84ST","postman-openapi-converter",null,"Convert OpenAPI 3.x or Swagger 2.0 specs (YAML or JSON) into complete, import-ready Postman Collection v2.1 JSON files. Use this skill whenever the user provides or references an OpenAPI spec, Swagger file, openapi.yaml, swagger.json, or uses phrases like \"convert my OpenAPI spec\", \"import swagger to Postman\", \"turn this spec into a collection\", or \"generate Postman requests from my API spec\". Also triggers when the user pastes YAML or JSON that begins with `openapi:`, `swagger:`, or contains `paths:` with HTTP method keys. Always prefer this skill over the general collection generator when the input is a structured spec file.","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpostman-openapi-converter\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"converter","postman openapi converter","postman","openapi","api-testing","collection","file","api","convert","use","testing","ready","files","general","triggers","complete","import","with","generator","http","2026-11-10 10:12:30",false,"---\nname: postman-openapi-converter\ndescription: >\n  Convert OpenAPI 3.x or Swagger 2.0 specs (YAML or JSON) into complete, import-ready\n  Postman Collection v2.1 JSON files. Use this skill whenever the user provides or\n  references an OpenAPI spec, Swagger file, openapi.yaml, swagger.json, or uses phrases\n  like \"convert my OpenAPI spec\", \"import swagger to Postman\", \"turn this spec into a\n  collection\", or \"generate Postman requests from my API spec\". Also triggers when the\n  user pastes YAML or JSON that begins with `openapi:`, `swagger:`, or contains `paths:`\n  with HTTP method keys. Always prefer this skill over the general collection generator\n  when the input is a structured spec file.\nlanguages:\n  - JSON\n  - YAML\ncategory: api-testing\nlicense: MIT\nmetadata:\n  author: TestMu AI\n  version: \"1.0\"\n---\n\n# OpenAPI → Postman Collection Converter\n\nConverts **OpenAPI 3.x** or **Swagger 2.0** specs into a valid **Postman Collection v2.1**.\n\n---\n\n## Step 1 — Detect & Validate Input\n\nIdentify the spec version from the input:\n- `openapi: 3.x.x` → OpenAPI 3\n- `swagger: \"2.0\"` → Swagger 2\n\nIf the input is truncated or partial, convert what's available and note missing sections.\n\n---\n\n## Step 2 — Extraction Mapping\n\n### OpenAPI 3 → Postman\n\n| OpenAPI field | Postman mapping |\n|---|---|\n| `info.title` | Collection name |\n| `info.description` | Collection description |\n| `servers[0].url` | `{{base_url}}` variable |\n| `paths.\u003Cpath>.\u003Cmethod>` | One request item per operation |\n| `operationId` or `summary` | Request name |\n| `parameters` (path\u002Fquery\u002Fheader) | URL path variables, query params, headers |\n| `requestBody.content.application\u002Fjson.schema` | Body (raw JSON), generate example from schema |\n| `responses` | Saved example responses |\n| `components.securitySchemes` | Collection-level auth |\n| `tags` | Folder grouping |\n\n### Swagger 2 → Postman\n\n| Swagger field | Postman mapping |\n|---|---|\n| `host` + `basePath` | `{{base_url}}` |\n| `paths.\u003Cpath>.\u003Cmethod>` | Request item |\n| `parameters` | Query\u002Fpath\u002Fheader\u002Fbody params |\n| `consumes` \u002F `produces` | Content-Type \u002F Accept headers |\n| `securityDefinitions` | Collection auth |\n| `tags` | Folders |\n\n---\n\n## Step 3 — Generate Example Bodies\n\nFor each request with a `requestBody` or `body` parameter, generate a realistic example JSON body from the schema:\n- Use property names as keys\n- Infer sensible example values from type + format (e.g., `\"email\"` format → `\"user@example.com\"`, `\"date-time\"` → `\"2024-01-15T10:30:00Z\"`)\n- For `$ref` schemas, resolve them inline\n\n---\n\n## Step 4 — Auth Handling\n\nMap security schemes to Postman auth:\n\n| OpenAPI scheme | Postman auth type |\n|---|---|\n| `http: bearer` | `bearer` with `{{token}}` |\n| `http: basic` | `basic` with `{{username}}` \u002F `{{password}}` |\n| `apiKey: header` | `apikey` header with `{{api_key}}` |\n| `apiKey: query` | `apikey` query param |\n| `oauth2` | `oauth2` (note: requires manual token setup) |\n\nApply auth at **collection level** if all endpoints share the same scheme. Override at request level for exceptions.\n\n---\n\n## Step 5 — Build Collection JSON\n\nUse the standard v2.1 structure (same schema as postman-collection-generator skill).\n\nKey differences for spec-converted collections:\n- Always group by `tags` into folders\n- Include `description` field on each request from `operationId` + `summary` + `description`\n- Add saved example responses where `responses` are defined in the spec\n\n```json\n\"response\": [\n  {\n    \"name\": \"200 OK\",\n    \"status\": \"OK\",\n    \"code\": 200,\n    \"header\": [{ \"key\": \"Content-Type\", \"value\": \"application\u002Fjson\" }],\n    \"body\": \"{ \\\"id\\\": 1, \\\"name\\\": \\\"example\\\" }\",\n    \"originalRequest\": { \u003Ccopy of the request> }\n  }\n]\n```\n\n---\n\n## Step 6 — Environment File\n\nExtract all variables into a companion environment:\n- `base_url` from `servers[0].url` or `host + basePath`\n- `token`, `api_key`, `username`, `password` as empty placeholders\n- Any server variables from `servers[0].variables`\n\n---\n\n## Step 7 — Output\n\n1. `collection.json` — Full Postman Collection v2.1\n2. `environment.json` — Matching environment file\n3. **Conversion summary**: number of endpoints converted, folders created, auth type detected, any fields skipped or approximated\n4. Import instructions\n\n---\n\n## Edge Cases\n\n- **`$ref` chains**: Resolve all `$ref` pointers inline before mapping\n- **`allOf` \u002F `oneOf` \u002F `anyOf`**: Use the first\u002Fprimary schema for body generation; note alternatives in description\n- **Path parameters**: Convert `{param}` to `:param` in URL path AND add to `variable` array in url object\n- **Multiple content types**: Prefer `application\u002Fjson`; note others in request description\n- **No operationId**: Generate name from `METHOD \u002Fpath` (e.g., `GET \u002Fusers\u002F{id}` → `Get User by ID`)\n\n---\n\n## Quality Checklist\n\n- [ ] Every `paths` entry produces at least one request\n- [ ] Path params use `:param` format in Postman URL\n- [ ] All `$ref` resolved — no raw `$ref` strings in output\n- [ ] Auth tokens are `{{variables}}`, never hardcoded\n- [ ] JSON output is valid and importable\n\n---\n\n## After Completing the API Design\n\nOnce the API design output is delivered, ask the user:\n\n\"Would you like me to generate API documentation for this design? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the API Documentation skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the API Documentation skill\n  - Use the API design output above as the input\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the API Documentation skill isn't installed. \n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---","# OpenAPI → Postman Collection Converter\n\nConverts **OpenAPI 3.x** or **Swagger 2.0** specs into a valid **Postman Collection v2.1**.\n\n---\n\n## Step 1 — Detect & Validate Input\n\nIdentify the spec version from the input:\n- `openapi: 3.x.x` → OpenAPI 3\n- `swagger: \"2.0\"` → Swagger 2\n\nIf the input is truncated or partial, convert what's available and note missing sections.\n\n---\n\n## Step 2 — Extraction Mapping\n\n### OpenAPI 3 → Postman\n\n| OpenAPI field | Postman mapping |\n|---|---|\n| `info.title` | Collection name |\n| `info.description` | Collection description |\n| `servers[0].url` | `{{base_url}}` variable |\n| `paths.\u003Cpath>.\u003Cmethod>` | One request item per operation |\n| `operationId` or `summary` | Request name |\n| `parameters` (path\u002Fquery\u002Fheader) | URL path variables, query params, headers |\n| `requestBody.content.application\u002Fjson.schema` | Body (raw JSON), generate example from schema |\n| `responses` | Saved example responses |\n| `components.securitySchemes` | Collection-level auth |\n| `tags` | Folder grouping |\n\n### Swagger 2 → Postman\n\n| Swagger field | Postman mapping |\n|---|---|\n| `host` + `basePath` | `{{base_url}}` |\n| `paths.\u003Cpath>.\u003Cmethod>` | Request item |\n| `parameters` | Query\u002Fpath\u002Fheader\u002Fbody params |\n| `consumes` \u002F `produces` | Content-Type \u002F Accept headers |\n| `securityDefinitions` | Collection auth |\n| `tags` | Folders |\n\n---\n\n## Step 3 — Generate Example Bodies\n\nFor each request with a `requestBody` or `body` parameter, generate a realistic example JSON body from the schema:\n- Use property names as keys\n- Infer sensible example values from type + format (e.g., `\"email\"` format → `\"user@example.com\"`, `\"date-time\"` → `\"2024-01-15T10:30:00Z\"`)\n- For `$ref` schemas, resolve them inline\n\n---\n\n## Step 4 — Auth Handling\n\nMap security schemes to Postman auth:\n\n| OpenAPI scheme | Postman auth type |\n|---|---|\n| `http: bearer` | `bearer` with `{{token}}` |\n| `http: basic` | `basic` with `{{username}}` \u002F `{{password}}` |\n| `apiKey: header` | `apikey` header with `{{api_key}}` |\n| `apiKey: query` | `apikey` query param |\n| `oauth2` | `oauth2` (note: requires manual token setup) |\n\nApply auth at **collection level** if all endpoints share the same scheme. Override at request level for exceptions.\n\n---\n\n## Step 5 — Build Collection JSON\n\nUse the standard v2.1 structure (same schema as postman-collection-generator skill).\n\nKey differences for spec-converted collections:\n- Always group by `tags` into folders\n- Include `description` field on each request from `operationId` + `summary` + `description`\n- Add saved example responses where `responses` are defined in the spec\n\n```json\n\"response\": [\n  {\n    \"name\": \"200 OK\",\n    \"status\": \"OK\",\n    \"code\": 200,\n    \"header\": [{ \"key\": \"Content-Type\", \"value\": \"application\u002Fjson\" }],\n    \"body\": \"{ \\\"id\\\": 1, \\\"name\\\": \\\"example\\\" }\",\n    \"originalRequest\": { \u003Ccopy of the request> }\n  }\n]\n```\n\n---\n\n## Step 6 — Environment File\n\nExtract all variables into a companion environment:\n- `base_url` from `servers[0].url` or `host + basePath`\n- `token`, `api_key`, `username`, `password` as empty placeholders\n- Any server variables from `servers[0].variables`\n\n---\n\n## Step 7 — Output\n\n1. `collection.json` — Full Postman Collection v2.1\n2. `environment.json` — Matching environment file\n3. **Conversion summary**: number of endpoints converted, folders created, auth type detected, any fields skipped or approximated\n4. Import instructions\n\n---\n\n## Edge Cases\n\n- **`$ref` chains**: Resolve all `$ref` pointers inline before mapping\n- **`allOf` \u002F `oneOf` \u002F `anyOf`**: Use the first\u002Fprimary schema for body generation; note alternatives in description\n- **Path parameters**: Convert `{param}` to `:param` in URL path AND add to `variable` array in url object\n- **Multiple content types**: Prefer `application\u002Fjson`; note others in request description\n- **No operationId**: Generate name from `METHOD \u002Fpath` (e.g., `GET \u002Fusers\u002F{id}` → `Get User by ID`)\n\n---\n\n## Quality Checklist\n\n- [ ] Every `paths` entry produces at least one request\n- [ ] Path params use `:param` format in Postman URL\n- [ ] All `$ref` resolved — no raw `$ref` strings in output\n- [ ] Auth tokens are `{{variables}}`, never hardcoded\n- [ ] JSON output is valid and importable\n\n---\n\n## After Completing the API Design\n\nOnce the API design output is delivered, ask the user:\n\n\"Would you like me to generate API documentation for this design? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the API Documentation skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the API Documentation skill\n  - Use the API design output above as the input\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the API Documentation skill isn't installed. \n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---",{"name":5,"license":15,"category":33,"metadata":54,"languages":57,"description":60},{"author":55,"version":56},"TestMu AI","1.0",[58,59],"JSON","YAML","Convert OpenAPI 3.x or Swagger 2.0 specs (YAML or JSON) into complete, import-ready Postman Collection v2.1 JSON files. Use this skill whenever the user provides or references an OpenAPI spec, Swagger file, openapi.yaml, swagger.json, or uses phrases like \"convert my OpenAPI spec\", \"import swagger to Postman\", \"turn this spec into a collection\", or \"generate Postman requests from my API spec\". Also triggers when the user pastes YAML or JSON that begins with `openapi:`, `swagger:`, or contains `paths:` with HTTP method keys. Always prefer this skill over the general collection generator when the input is a structured spec file.\n","main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".claude\u002Fskills\u002Fpostman-openapi-converter","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill postman-openapi-converter",{"tool":74,"command":75},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill postman-openapi-converter",{"tool":77,"command":78},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill postman-openapi-converter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpostman-openapi-converter\u002FSKILL.md",true,[],[83,104,129,155,173,206],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":95,"publishedAt":49},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[89,92],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[96,97,39,98,99,38,100,43,101,102,103],"xunit","xunit skill","injection","user","tests","unit","unit-testing","C#",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":112,"publishedAt":49},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[110,111],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[113,114,39,115,116,117,118,119,38,120,121,122,123,124,100,43,125,126,127,128],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","for","objective",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":139,"publishedAt":49},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[140,141,142,143,144,145,146,147,38,148,149,150,151,152,153,127,154],"builder","world","world builder","MCP","create","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":49},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[161,162],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[164,39,165,115,166,167,168,169,99,38,170,123,100,43,171,172],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","URL","conf",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":186,"publishedAt":49},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[179,182,183],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":184,"categoryName":185,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,43,205],"design","web","guidelines","web design guidelines","web design","css","performance","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","platform","implementing",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":214,"publishedAt":49},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[212,213],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":184,"categoryName":185,"taxonomyType":26,"taxonomyTypeDesc":27},[187,189,215,196,199,38,216,217,124,204,218,43,125,219,127,220,221],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]