[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PRH7G2AFE1JQVWSYPDQPC2":3,"skill-same:01M6PRH7G2AFE1JQVWSYPDQPC2":94},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6PRH7G2AFE1JQVWSYPDQPC2","redis-query-engine",null,"Redis Query Engine (RQE) guidance covering FT.CREATE schema design, field type selection (TEXT, TAG, NUMERIC, GEO, GEOSHAPE, VECTOR), DIALECT 2 query syntax, efficient FT.SEARCH and FT.AGGREGATE queries, zero-downtime index updates via aliases, and the SKIPINITIALSCAN option. Use when defining a search index on Hash or JSON documents, picking between TEXT and TAG for filtering, writing FT.SEARCH queries with filters and SORTBY, managing or swapping indexes in production, or troubleshooting slow searches with FT.PROFILE.","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\u002Fredis-query-engine\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"redis query engine","query engine","redis","redis query","engine","query","use","for","zero-downtime","selection","geo","filters","schema","design","filtering","option","ZeRO","vector","search","writing","2026-11-10 10:12:30",false,"---\nname: redis-query-engine\ndescription: Redis Query Engine (RQE) guidance covering FT.CREATE schema design, field type selection (TEXT, TAG, NUMERIC, GEO, GEOSHAPE, VECTOR), DIALECT 2 query syntax, efficient FT.SEARCH and FT.AGGREGATE queries, zero-downtime index updates via aliases, and the SKIPINITIALSCAN option. Use when defining a search index on Hash or JSON documents, picking between TEXT and TAG for filtering, writing FT.SEARCH queries with filters and SORTBY, managing or swapping indexes in production, or troubleshooting slow searches with FT.PROFILE.\nlicense: MIT\nmetadata:\n  author: Redis, Inc.\n  version: \"0.1.0\"\n---\n\n# Redis Query Engine\n\nGuidance for using the Redis Query Engine (RQE) to index and search Hash or JSON documents. Covers schema design with `FT.CREATE`, field-type choices, query syntax, index lifecycle management, and the most common performance pitfalls.\n\n## When to apply\n\n- Creating, modifying, or reviewing an RQE index (`FT.CREATE`, `FT.ALTER`).\n- Writing or optimizing `FT.SEARCH` \u002F `FT.AGGREGATE` queries.\n- Deciding between `TEXT`, `TAG`, `NUMERIC`, `GEO`, `GEOSHAPE`, or `VECTOR` for a field.\n- Rolling out a new index schema without downtime.\n- Spinning up an index that should only cover newly written keys.\n\n## 1. Use DIALECT 2 (the modern default)\n\n`DIALECT 2` is the baseline. Other dialects (1, 3, 4) are deprecated as of Redis 8. Most modern client libraries already default to it — but specify it explicitly in raw commands for portability.\n\n```\nFT.SEARCH idx:products \"@name:laptop\" DIALECT 2\n```\n\n`DIALECT 2` is **required** for vector search queries. It also handles special characters and NULLs predictably.\n\nSee [references\u002Fdialect.md](references\u002Fdialect.md).\n\n## 2. Pick the right field type\n\nThe field type decides both what you can query and how fast that query is. Use the narrowest type that supports your access pattern.\n\n| Field type | Use when | Notes |\n|---|---|---|\n| `TEXT` | Full-text search needed | Tokenized + stemmed; **not** for exact match |\n| `TAG` | Exact match \u002F filtering | Add `SORTABLE UNF` for fastest tag queries |\n| `NUMERIC` | Range queries, sorting | Prices, counts, timestamps |\n| `GEO` | Lat\u002Flong point queries | Single points (stores, users) |\n| `GEOSHAPE` | Polygon \u002F area queries | Delivery zones, regions |\n| `VECTOR` | Similarity search | HNSW or FLAT; see redis-vector-search |\n\nThe classic mistake is using `TEXT` for a category or status field because \"it's a string.\" `TAG` is 10× faster for those.\n\nSee [references\u002Ffield-types.md](references\u002Ffield-types.md).\n\n## 3. Index only what you query — and always set a prefix\n\n`FT.CREATE` without a `PREFIX` indexes **every** matching key in the database; with a wide schema it can blow up index size and write latency.\n\n```\nFT.CREATE idx:products ON HASH PREFIX 1 product:\n    SCHEMA\n        name TEXT WEIGHT 2.0\n        category TAG SORTABLE\n        price NUMERIC SORTABLE\n        location GEO\n```\n\nRules of thumb:\n\n- Start with the minimum schema. Add fields as new query patterns emerge.\n- Always set `PREFIX` (or filter via `FILTER` expression).\n- Use `FT.INFO idx:\u003Cname>` to monitor index size after adding fields.\n- Use `SORTABLE` only on fields you actually sort by; it has a memory cost.\n\nSee [references\u002Findex-creation.md](references\u002Findex-creation.md).\n\n## 4. Zero-downtime index updates — use aliases\n\nFor schema changes in production, keep application queries pointed at an alias and swap the underlying index.\n\n```\nFT.CREATE idx:products_v2 ON HASH PREFIX 1 product: SCHEMA ...\nFT.ALIASUPDATE products idx:products_v2\n\n# App queries are stable:\nFT.SEARCH products \"@category:{electronics}\"\n```\n\nUseful management commands: `FT.INFO`, `FT.DROPINDEX`, `FT._LIST`, `FT.ALIASADD\u002FUPDATE\u002FDEL`.\n\nSee [references\u002Findex-management.md](references\u002Findex-management.md).\n\n## 5. SKIPINITIALSCAN — only when historical data is irrelevant\n\nBy default `FT.CREATE` walks all existing keys that match the prefix and indexes them. Use `SKIPINITIALSCAN` only when:\n\n- You're standing up the index for a *new* feature and existing data shouldn't be queryable.\n- Existing data is too large to scan synchronously.\n- You're indexing event streams where only future events matter.\n\nFor most schema migrations, the default (scan everything) is what you want.\n\nSee [references\u002Fskip-initial-scan.md](references\u002Fskip-initial-scan.md).\n\n## 6. Write specific queries, not `*`\n\nNarrow the result set with filters before paging or aggregating.\n\n```\n# Good — specific filter, limited fields returned\nFT.SEARCH idx:products \"@category:{electronics} @price:[100 500]\"\n    LIMIT 0 20\n    RETURN 3 name price category\n```\n\n```\n# Bad — full scan plus unbounded LIMIT\nFT.SEARCH idx:products \"*\" LIMIT 0 10000\n```\n\nOther levers:\n\n- `SORTBY` requires `SORTABLE` on the sort field. Without it, sort is slow.\n- `LIMIT` early; the engine still processes everything above the limit if you don't.\n- `RETURN` specific fields — don't fetch the whole document if you only need a few.\n- Profile with `FT.PROFILE idx:\u003Cname> SEARCH QUERY \"\u003Cquery>\"` when a query is slow.\n\nSee [references\u002Fquery-optimization.md](references\u002Fquery-optimization.md).\n\n## References\n\n- [Redis: Query Engine — Indexing](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Findexing\u002F)\n- [Redis: Query syntax](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Fquery\u002F)\n- [Redis: Query dialects](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Fadvanced-concepts\u002Fdialects\u002F)\n- [Redis: Administration (aliases, dropindex)](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Fadministration\u002F)\n- [FT.CREATE](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fcommands\u002Fft.create\u002F)\n","# Redis Query Engine\n\nGuidance for using the Redis Query Engine (RQE) to index and search Hash or JSON documents. Covers schema design with `FT.CREATE`, field-type choices, query syntax, index lifecycle management, and the most common performance pitfalls.\n\n## When to apply\n\n- Creating, modifying, or reviewing an RQE index (`FT.CREATE`, `FT.ALTER`).\n- Writing or optimizing `FT.SEARCH` \u002F `FT.AGGREGATE` queries.\n- Deciding between `TEXT`, `TAG`, `NUMERIC`, `GEO`, `GEOSHAPE`, or `VECTOR` for a field.\n- Rolling out a new index schema without downtime.\n- Spinning up an index that should only cover newly written keys.\n\n## 1. Use DIALECT 2 (the modern default)\n\n`DIALECT 2` is the baseline. Other dialects (1, 3, 4) are deprecated as of Redis 8. Most modern client libraries already default to it — but specify it explicitly in raw commands for portability.\n\n```\nFT.SEARCH idx:products \"@name:laptop\" DIALECT 2\n```\n\n`DIALECT 2` is **required** for vector search queries. It also handles special characters and NULLs predictably.\n\nSee [references\u002Fdialect.md](references\u002Fdialect.md).\n\n## 2. Pick the right field type\n\nThe field type decides both what you can query and how fast that query is. Use the narrowest type that supports your access pattern.\n\n| Field type | Use when | Notes |\n|---|---|---|\n| `TEXT` | Full-text search needed | Tokenized + stemmed; **not** for exact match |\n| `TAG` | Exact match \u002F filtering | Add `SORTABLE UNF` for fastest tag queries |\n| `NUMERIC` | Range queries, sorting | Prices, counts, timestamps |\n| `GEO` | Lat\u002Flong point queries | Single points (stores, users) |\n| `GEOSHAPE` | Polygon \u002F area queries | Delivery zones, regions |\n| `VECTOR` | Similarity search | HNSW or FLAT; see redis-vector-search |\n\nThe classic mistake is using `TEXT` for a category or status field because \"it's a string.\" `TAG` is 10× faster for those.\n\nSee [references\u002Ffield-types.md](references\u002Ffield-types.md).\n\n## 3. Index only what you query — and always set a prefix\n\n`FT.CREATE` without a `PREFIX` indexes **every** matching key in the database; with a wide schema it can blow up index size and write latency.\n\n```\nFT.CREATE idx:products ON HASH PREFIX 1 product:\n    SCHEMA\n        name TEXT WEIGHT 2.0\n        category TAG SORTABLE\n        price NUMERIC SORTABLE\n        location GEO\n```\n\nRules of thumb:\n\n- Start with the minimum schema. Add fields as new query patterns emerge.\n- Always set `PREFIX` (or filter via `FILTER` expression).\n- Use `FT.INFO idx:\u003Cname>` to monitor index size after adding fields.\n- Use `SORTABLE` only on fields you actually sort by; it has a memory cost.\n\nSee [references\u002Findex-creation.md](references\u002Findex-creation.md).\n\n## 4. Zero-downtime index updates — use aliases\n\nFor schema changes in production, keep application queries pointed at an alias and swap the underlying index.\n\n```\nFT.CREATE idx:products_v2 ON HASH PREFIX 1 product: SCHEMA ...\nFT.ALIASUPDATE products idx:products_v2\n\n# App queries are stable:\nFT.SEARCH products \"@category:{electronics}\"\n```\n\nUseful management commands: `FT.INFO`, `FT.DROPINDEX`, `FT._LIST`, `FT.ALIASADD\u002FUPDATE\u002FDEL`.\n\nSee [references\u002Findex-management.md](references\u002Findex-management.md).\n\n## 5. SKIPINITIALSCAN — only when historical data is irrelevant\n\nBy default `FT.CREATE` walks all existing keys that match the prefix and indexes them. Use `SKIPINITIALSCAN` only when:\n\n- You're standing up the index for a *new* feature and existing data shouldn't be queryable.\n- Existing data is too large to scan synchronously.\n- You're indexing event streams where only future events matter.\n\nFor most schema migrations, the default (scan everything) is what you want.\n\nSee [references\u002Fskip-initial-scan.md](references\u002Fskip-initial-scan.md).\n\n## 6. Write specific queries, not `*`\n\nNarrow the result set with filters before paging or aggregating.\n\n```\n# Good — specific filter, limited fields returned\nFT.SEARCH idx:products \"@category:{electronics} @price:[100 500]\"\n    LIMIT 0 20\n    RETURN 3 name price category\n```\n\n```\n# Bad — full scan plus unbounded LIMIT\nFT.SEARCH idx:products \"*\" LIMIT 0 10000\n```\n\nOther levers:\n\n- `SORTBY` requires `SORTABLE` on the sort field. Without it, sort is slow.\n- `LIMIT` early; the engine still processes everything above the limit if you don't.\n- `RETURN` specific fields — don't fetch the whole document if you only need a few.\n- Profile with `FT.PROFILE idx:\u003Cname> SEARCH QUERY \"\u003Cquery>\"` when a query is slow.\n\nSee [references\u002Fquery-optimization.md](references\u002Fquery-optimization.md).\n\n## References\n\n- [Redis: Query Engine — Indexing](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Findexing\u002F)\n- [Redis: Query syntax](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Fquery\u002F)\n- [Redis: Query dialects](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Fadvanced-concepts\u002Fdialects\u002F)\n- [Redis: Administration (aliases, dropindex)](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Finteract\u002Fsearch-and-query\u002Fadministration\u002F)\n- [FT.CREATE](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fcommands\u002Fft.create\u002F)\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"version":46},"Redis, Inc.","0.1.0","main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".claude\u002Fskills\u002Fredis-query-engine","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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill redis-query-engine",{"tool":60,"command":61},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill redis-query-engine",{"tool":63,"command":64},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill redis-query-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002FSKILL.md",true,[68,74,78,82,86,90],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fdialect.md","REFERENCE","参考文档",1117,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002Freferences\u002Fdialect.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Ffield-types.md",2106,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002Freferences\u002Ffield-types.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Findex-creation.md",1623,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002Freferences\u002Findex-creation.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Findex-management.md",864,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002Freferences\u002Findex-management.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fquery-optimization.md",1028,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002Freferences\u002Fquery-optimization.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fskip-initial-scan.md",2428,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-query-engine\u002Freferences\u002Fskip-initial-scan.md",[95,120,144,170,188,222],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":109,"publishedAt":39},"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",[101,106],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发",[110,111,112,113,114,25,115,116,117,118,119],"xunit","xunit skill","testing","injection","user","tests","triggers","unit","unit-testing","C#",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":128,"publishedAt":39},"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",[126,127],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},[129,130,112,131,132,133,134,135,25,136,137,138,139,140,115,116,141,142,26,143],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","objective",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":154,"publishedAt":39},"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",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},[155,156,157,158,159,160,161,162,25,163,164,165,166,167,168,26,169],"builder","world","world builder","MCP","create","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":178,"publishedAt":39},"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",[176,177],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},[179,112,180,131,181,182,183,184,114,25,185,139,115,116,186,187],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","URL","conf",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":203,"publishedAt":39},"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",[194,197,198],{"categoryNo":195,"categoryName":196,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":151,"categoryName":152,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":199,"categoryName":200,"taxonomyType":201,"taxonomyTypeDesc":202},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,116,221],"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":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":230,"publishedAt":39},"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",[228,229],{"categoryNo":151,"categoryName":152,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":199,"categoryName":200,"taxonomyType":201,"taxonomyTypeDesc":202},[32,205,231,212,215,25,232,233,140,220,234,116,141,235,26,236,237],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]