[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EM9G0RYBM7FDM30TFZK78":3,"skill-same:01M71EM9G0RYBM7FDM30TFZK78":62},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M71EM9G0RYBM7FDM30TFZK78","clickhouse-best-practices",null,"MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_clickhouse_clickhouse_best_practices\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"clickhouse best practices","clickhouse","best practices","relevant","files","when","recommendations","read","use","Rules","queries","rule","2026-11-10 10:12:30",false,"---\nname: clickhouse-best-practices\ndescription: MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.\nlicense: Apache-2.0\nmetadata:\n  author: ClickHouse Inc\n  version: \"0.3.0\"\n---\n\n# ClickHouse Best Practices\n\nComprehensive guidance for ClickHouse covering schema design, query optimization, and data ingestion. Contains 28 rules across 3 main categories (schema, query, insert), prioritized by impact.\n\n> **Official docs:** [ClickHouse Best Practices](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fbest-practices)\n\n## IMPORTANT: How to Apply This Skill\n\n**Before answering ClickHouse questions, follow this priority order:**\n\n1. **Check for applicable rules** in the `rules\u002F` directory\n2. **If rules exist:** Apply them and cite them in your response using \"Per `rule-name`...\"\n3. **If no rule exists:** Use the LLM's ClickHouse knowledge or search documentation\n4. **If uncertain:** Use web search for current best practices\n5. **Always cite your source:** rule name, \"general ClickHouse guidance\", or URL\n\n**Why rules take priority:** ClickHouse has specific behaviors (columnar storage, sparse indexes, merge tree mechanics) where general database intuition can be misleading. The rules encode validated, ClickHouse-specific guidance.\n\n### For Formal Reviews\n\nWhen performing a formal review of schemas, queries, or data ingestion:\n\n---\n\n## Review Procedures\n\n### For Schema Reviews (CREATE TABLE, ALTER TABLE)\n\n**Read these rule files in order:**\n\n1. `rules\u002Fschema_pk_plan_before_creation.md` - ORDER BY is immutable\n2. `rules\u002Fschema_pk_cardinality_order.md` - Column ordering in keys\n3. `rules\u002Fschema_pk_prioritize_filters.md` - Filter column inclusion\n4. `rules\u002Fschema_types_native_types.md` - Proper type selection\n5. `rules\u002Fschema_types_minimize_bitwidth.md` - Numeric type sizing\n6. `rules\u002Fschema_types_lowcardinality.md` - LowCardinality usage\n7. `rules\u002Fschema_types_avoid_nullable.md` - Nullable vs DEFAULT\n8. `rules\u002Fschema_partition_low_cardinality.md` - Partition count limits\n9. `rules\u002Fschema_partition_lifecycle.md` - Partitioning purpose\n\n**Check for:**\n- [ ] PRIMARY KEY \u002F ORDER BY column order (low-to-high cardinality)\n- [ ] Data types match actual data ranges\n- [ ] LowCardinality applied to appropriate string columns\n- [ ] Partition key cardinality bounded (100-1,000 values)\n- [ ] ReplacingMergeTree has version column if used\n\n### For Query Reviews (SELECT, JOIN, aggregations)\n\n**Read these rule files:**\n\n1. `rules\u002Fquery_join_choose_algorithm.md` - Algorithm selection\n2. `rules\u002Fquery_join_filter_before.md` - Pre-join filtering\n3. `rules\u002Fquery_join_use_any.md` - ANY vs regular JOIN\n4. `rules\u002Fquery_index_skipping_indices.md` - Secondary index usage\n5. `rules\u002Fschema_pk_filter_on_orderby.md` - Filter alignment with ORDER BY\n\n**Check for:**\n- [ ] Filters use ORDER BY prefix columns\n- [ ] JOINs filter tables before joining (not after)\n- [ ] Correct JOIN algorithm for table sizes\n- [ ] Skipping indices for non-ORDER BY filter columns\n\n### For Insert Strategy Reviews (data ingestion, updates, deletes)\n\n**Read these rule files:**\n\n1. `rules\u002Finsert_batch_size.md` - Batch sizing requirements\n2. `rules\u002Finsert_mutation_avoid_update.md` - UPDATE alternatives\n3. `rules\u002Finsert_mutation_avoid_delete.md` - DELETE alternatives\n4. `rules\u002Finsert_async_small_batches.md` - Async insert usage\n5. `rules\u002Finsert_optimize_avoid_final.md` - OPTIMIZE TABLE risks\n\n**Check for:**\n- [ ] Batch size 10K-100K rows per INSERT\n- [ ] No ALTER TABLE UPDATE for frequent changes\n- [ ] ReplacingMergeTree or CollapsingMergeTree for update patterns\n- [ ] Async inserts enabled for high-frequency small batches\n\n---\n\n## Output Format\n\nStructure your response as follows:\n\n```\n## Rules Checked\n- `rule-name-1` - Compliant \u002F Violation found\n- `rule-name-2` - Compliant \u002F Violation found\n...\n\n## Findings\n\n### Violations\n- **`rule-name`**: Description of the issue\n  - Current: [what the code does]\n  - Required: [what it should do]\n  - Fix: [specific correction]\n\n### Compliant\n- `rule-name`: Brief note on why it's correct\n\n## Recommendations\n[Prioritized list of changes, citing rules]\n```\n\n---\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix | Rule Count |\n|----------|----------|--------|--------|------------|\n| 1 | Primary Key Selection | CRITICAL | `schema-pk-` | 4 |\n| 2 | Data Type Selection | CRITICAL | `schema-types-` | 5 |\n| 3 | JOIN Optimization | CRITICAL | `query-join-` | 5 |\n| 4 | Insert Batching | CRITICAL | `insert-batch-` | 1 |\n| 5 | Mutation Avoidance | CRITICAL | `insert-mutation-` | 2 |\n| 6 | Partitioning Strategy | HIGH | `schema-partition-` | 4 |\n| 7 | Skipping Indices | HIGH | `query-index-` | 1 |\n| 8 | Materialized Views | HIGH | `query-mv-` | 2 |\n| 9 | Async Inserts | HIGH | `insert-async-` | 2 |\n| 10 | OPTIMIZE Avoidance | HIGH | `insert-optimize-` | 1 |\n| 11 | JSON Usage | MEDIUM | `schema-json-` | 1 |\n\n---\n\n## Quick Reference\n\n### Schema Design - Primary Key (CRITICAL)\n\n- `schema-pk-plan-before-creation` - Plan ORDER BY before table creation (immutable)\n- `schema-pk-cardinality-order` - Order columns low-to-high cardinality\n- `schema-pk-prioritize-filters` - Include frequently filtered columns\n- `schema-pk-filter-on-orderby` - Query filters must use ORDER BY prefix\n\n### Schema Design - Data Types (CRITICAL)\n\n- `schema-types-native-types` - Use native types, not String for everything\n- `schema-types-minimize-bitwidth` - Use smallest numeric type that fits\n- `schema-types-lowcardinality` - LowCardinality for \u003C10K unique strings\n- `schema-types-enum` - Enum for finite value sets with validation\n- `schema-types-avoid-nullable` - Avoid Nullable; use DEFAULT instead\n\n### Schema Design - Partitioning (HIGH)\n\n- `schema-partition-low-cardinality` - Keep partition count 100-1,000\n- `schema-partition-lifecycle` - Use partitioning for data lifecycle, not queries\n- `schema-partition-query-tradeoffs` - Understand partition pruning trade-offs\n- `schema-partition-start-without` - Consider starting without partitioning\n\n### Schema Design - JSON (MEDIUM)\n\n- `schema-json-when-to-use` - JSON for dynamic schemas; typed columns for known\n\n### Query Optimization - JOINs (CRITICAL)\n\n- `query-join-choose-algorithm` - Select algorithm based on table sizes\n- `query-join-use-any` - ANY JOIN when only one match needed\n- `query-join-filter-before` - Filter tables before joining\n- `query-join-consider-alternatives` - Dictionaries\u002Fdenormalization vs JOIN\n- `query-join-null-handling` - join_use_nulls=0 for default values\n\n### Query Optimization - Indices (HIGH)\n\n- `query-index-skipping-indices` - Skipping indices for non-ORDER BY filters\n\n### Query Optimization - Materialized Views (HIGH)\n\n- `query-mv-incremental` - Incremental MVs for real-time aggregations\n- `query-mv-refreshable` - Refreshable MVs for complex joins\n\n### Insert Strategy - Batching (CRITICAL)\n\n- `insert-batch-size` - Batch 10K-100K rows per INSERT\n\n### Insert Strategy - Async (HIGH)\n\n- `insert-async-small-batches` - Async inserts for high-frequency small batches\n- `insert-format-native` - Native format for best performance\n\n### Insert Strategy - Mutations (CRITICAL)\n\n- `insert-mutation-avoid-update` - ReplacingMergeTree instead of ALTER UPDATE\n- `insert-mutation-avoid-delete` - Lightweight DELETE or DROP PARTITION\n\n### Insert Strategy - Optimization (HIGH)\n\n- `insert-optimize-avoid-final` - Let background merges work\n\n---\n\n## When to Apply\n\nThis skill activates when you encounter:\n\n- `CREATE TABLE` statements\n- `ALTER TABLE` modifications\n- `ORDER BY` or `PRIMARY KEY` discussions\n- Data type selection questions\n- Slow query troubleshooting\n- JOIN optimization requests\n- Data ingestion pipeline design\n- Update\u002Fdelete strategy questions\n- ReplacingMergeTree or other specialized engine usage\n- Partitioning strategy decisions\n\n---\n\n## Rule File Structure\n\nEach rule file in `rules\u002F` contains:\n\n- **YAML frontmatter**: title, impact level, tags\n- **Brief explanation**: Why this rule matters\n- **Incorrect example**: Anti-pattern with explanation\n- **Correct example**: Best practice with explanation\n- **Additional context**: Trade-offs, when to apply, references\n\n---\n\n## Full Compiled Document\n\nFor the complete guide with all rules expanded inline: `AGENTS.md`\n\nUse `AGENTS.md` when you need to check multiple rules quickly without reading individual files.\n","# ClickHouse Best Practices\n\nComprehensive guidance for ClickHouse covering schema design, query optimization, and data ingestion. Contains 28 rules across 3 main categories (schema, query, insert), prioritized by impact.\n\n> **Official docs:** [ClickHouse Best Practices](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fbest-practices)\n\n## IMPORTANT: How to Apply This Skill\n\n**Before answering ClickHouse questions, follow this priority order:**\n\n1. **Check for applicable rules** in the `rules\u002F` directory\n2. **If rules exist:** Apply them and cite them in your response using \"Per `rule-name`...\"\n3. **If no rule exists:** Use the LLM's ClickHouse knowledge or search documentation\n4. **If uncertain:** Use web search for current best practices\n5. **Always cite your source:** rule name, \"general ClickHouse guidance\", or URL\n\n**Why rules take priority:** ClickHouse has specific behaviors (columnar storage, sparse indexes, merge tree mechanics) where general database intuition can be misleading. The rules encode validated, ClickHouse-specific guidance.\n\n### For Formal Reviews\n\nWhen performing a formal review of schemas, queries, or data ingestion:\n\n---\n\n## Review Procedures\n\n### For Schema Reviews (CREATE TABLE, ALTER TABLE)\n\n**Read these rule files in order:**\n\n1. `rules\u002Fschema_pk_plan_before_creation.md` - ORDER BY is immutable\n2. `rules\u002Fschema_pk_cardinality_order.md` - Column ordering in keys\n3. `rules\u002Fschema_pk_prioritize_filters.md` - Filter column inclusion\n4. `rules\u002Fschema_types_native_types.md` - Proper type selection\n5. `rules\u002Fschema_types_minimize_bitwidth.md` - Numeric type sizing\n6. `rules\u002Fschema_types_lowcardinality.md` - LowCardinality usage\n7. `rules\u002Fschema_types_avoid_nullable.md` - Nullable vs DEFAULT\n8. `rules\u002Fschema_partition_low_cardinality.md` - Partition count limits\n9. `rules\u002Fschema_partition_lifecycle.md` - Partitioning purpose\n\n**Check for:**\n- [ ] PRIMARY KEY \u002F ORDER BY column order (low-to-high cardinality)\n- [ ] Data types match actual data ranges\n- [ ] LowCardinality applied to appropriate string columns\n- [ ] Partition key cardinality bounded (100-1,000 values)\n- [ ] ReplacingMergeTree has version column if used\n\n### For Query Reviews (SELECT, JOIN, aggregations)\n\n**Read these rule files:**\n\n1. `rules\u002Fquery_join_choose_algorithm.md` - Algorithm selection\n2. `rules\u002Fquery_join_filter_before.md` - Pre-join filtering\n3. `rules\u002Fquery_join_use_any.md` - ANY vs regular JOIN\n4. `rules\u002Fquery_index_skipping_indices.md` - Secondary index usage\n5. `rules\u002Fschema_pk_filter_on_orderby.md` - Filter alignment with ORDER BY\n\n**Check for:**\n- [ ] Filters use ORDER BY prefix columns\n- [ ] JOINs filter tables before joining (not after)\n- [ ] Correct JOIN algorithm for table sizes\n- [ ] Skipping indices for non-ORDER BY filter columns\n\n### For Insert Strategy Reviews (data ingestion, updates, deletes)\n\n**Read these rule files:**\n\n1. `rules\u002Finsert_batch_size.md` - Batch sizing requirements\n2. `rules\u002Finsert_mutation_avoid_update.md` - UPDATE alternatives\n3. `rules\u002Finsert_mutation_avoid_delete.md` - DELETE alternatives\n4. `rules\u002Finsert_async_small_batches.md` - Async insert usage\n5. `rules\u002Finsert_optimize_avoid_final.md` - OPTIMIZE TABLE risks\n\n**Check for:**\n- [ ] Batch size 10K-100K rows per INSERT\n- [ ] No ALTER TABLE UPDATE for frequent changes\n- [ ] ReplacingMergeTree or CollapsingMergeTree for update patterns\n- [ ] Async inserts enabled for high-frequency small batches\n\n---\n\n## Output Format\n\nStructure your response as follows:\n\n```\n## Rules Checked\n- `rule-name-1` - Compliant \u002F Violation found\n- `rule-name-2` - Compliant \u002F Violation found\n...\n\n## Findings\n\n### Violations\n- **`rule-name`**: Description of the issue\n  - Current: [what the code does]\n  - Required: [what it should do]\n  - Fix: [specific correction]\n\n### Compliant\n- `rule-name`: Brief note on why it's correct\n\n## Recommendations\n[Prioritized list of changes, citing rules]\n```\n\n---\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix | Rule Count |\n|----------|----------|--------|--------|------------|\n| 1 | Primary Key Selection | CRITICAL | `schema-pk-` | 4 |\n| 2 | Data Type Selection | CRITICAL | `schema-types-` | 5 |\n| 3 | JOIN Optimization | CRITICAL | `query-join-` | 5 |\n| 4 | Insert Batching | CRITICAL | `insert-batch-` | 1 |\n| 5 | Mutation Avoidance | CRITICAL | `insert-mutation-` | 2 |\n| 6 | Partitioning Strategy | HIGH | `schema-partition-` | 4 |\n| 7 | Skipping Indices | HIGH | `query-index-` | 1 |\n| 8 | Materialized Views | HIGH | `query-mv-` | 2 |\n| 9 | Async Inserts | HIGH | `insert-async-` | 2 |\n| 10 | OPTIMIZE Avoidance | HIGH | `insert-optimize-` | 1 |\n| 11 | JSON Usage | MEDIUM | `schema-json-` | 1 |\n\n---\n\n## Quick Reference\n\n### Schema Design - Primary Key (CRITICAL)\n\n- `schema-pk-plan-before-creation` - Plan ORDER BY before table creation (immutable)\n- `schema-pk-cardinality-order` - Order columns low-to-high cardinality\n- `schema-pk-prioritize-filters` - Include frequently filtered columns\n- `schema-pk-filter-on-orderby` - Query filters must use ORDER BY prefix\n\n### Schema Design - Data Types (CRITICAL)\n\n- `schema-types-native-types` - Use native types, not String for everything\n- `schema-types-minimize-bitwidth` - Use smallest numeric type that fits\n- `schema-types-lowcardinality` - LowCardinality for \u003C10K unique strings\n- `schema-types-enum` - Enum for finite value sets with validation\n- `schema-types-avoid-nullable` - Avoid Nullable; use DEFAULT instead\n\n### Schema Design - Partitioning (HIGH)\n\n- `schema-partition-low-cardinality` - Keep partition count 100-1,000\n- `schema-partition-lifecycle` - Use partitioning for data lifecycle, not queries\n- `schema-partition-query-tradeoffs` - Understand partition pruning trade-offs\n- `schema-partition-start-without` - Consider starting without partitioning\n\n### Schema Design - JSON (MEDIUM)\n\n- `schema-json-when-to-use` - JSON for dynamic schemas; typed columns for known\n\n### Query Optimization - JOINs (CRITICAL)\n\n- `query-join-choose-algorithm` - Select algorithm based on table sizes\n- `query-join-use-any` - ANY JOIN when only one match needed\n- `query-join-filter-before` - Filter tables before joining\n- `query-join-consider-alternatives` - Dictionaries\u002Fdenormalization vs JOIN\n- `query-join-null-handling` - join_use_nulls=0 for default values\n\n### Query Optimization - Indices (HIGH)\n\n- `query-index-skipping-indices` - Skipping indices for non-ORDER BY filters\n\n### Query Optimization - Materialized Views (HIGH)\n\n- `query-mv-incremental` - Incremental MVs for real-time aggregations\n- `query-mv-refreshable` - Refreshable MVs for complex joins\n\n### Insert Strategy - Batching (CRITICAL)\n\n- `insert-batch-size` - Batch 10K-100K rows per INSERT\n\n### Insert Strategy - Async (HIGH)\n\n- `insert-async-small-batches` - Async inserts for high-frequency small batches\n- `insert-format-native` - Native format for best performance\n\n### Insert Strategy - Mutations (CRITICAL)\n\n- `insert-mutation-avoid-update` - ReplacingMergeTree instead of ALTER UPDATE\n- `insert-mutation-avoid-delete` - Lightweight DELETE or DROP PARTITION\n\n### Insert Strategy - Optimization (HIGH)\n\n- `insert-optimize-avoid-final` - Let background merges work\n\n---\n\n## When to Apply\n\nThis skill activates when you encounter:\n\n- `CREATE TABLE` statements\n- `ALTER TABLE` modifications\n- `ORDER BY` or `PRIMARY KEY` discussions\n- Data type selection questions\n- Slow query troubleshooting\n- JOIN optimization requests\n- Data ingestion pipeline design\n- Update\u002Fdelete strategy questions\n- ReplacingMergeTree or other specialized engine usage\n- Partitioning strategy decisions\n\n---\n\n## Rule File Structure\n\nEach rule file in `rules\u002F` contains:\n\n- **YAML frontmatter**: title, impact level, tags\n- **Brief explanation**: Why this rule matters\n- **Incorrect example**: Anti-pattern with explanation\n- **Correct example**: Best practice with explanation\n- **Additional context**: Trade-offs, when to apply, references\n\n---\n\n## Full Compiled Document\n\nFor the complete guide with all rules expanded inline: `AGENTS.md`\n\nUse `AGENTS.md` when you need to check multiple rules quickly without reading individual files.\n",{"name":5,"license":15,"metadata":36,"description":7},{"author":37,"version":38},"ClickHouse Inc","0.3.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_clickhouse_clickhouse_best_practices",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill clickhouse-best-practices",{"tool":54,"command":55},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill clickhouse-best-practices",{"tool":57,"command":58},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill clickhouse-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_clickhouse_clickhouse_best_practices\u002Fskill.md",true,[],[63,96,119,140,159,181],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":95},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,24,90,91,92,93,94],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":95},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[102],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[76,104,105,80,106,107,108,109,89,110,24,111,90,112,113,114,115,116,117,118],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":95},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[125],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[76,127,128,80,21,109,129,24,130,111,90,131,132,133,134,135,136,137,138,139],"react best practices","vercel react best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":95},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[146],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[148,80,149,136,150,151,152,153,139,154,155,27,24,156,111,90,157,158,91,76],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":95},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口",[169,170,171,172,21,173,174,175,118,137,109,176,177,129,178,27,28,179,180,24],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","critical","database",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":204},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[187],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[189,190,191,192,193,86,194,153,195,89,196,197,24,76,198,199,200,201,202,203],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]