[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MDVASBCV46T2H13DENZWE":3,"skill-same:01M71MDVASBCV46T2H13DENZWE":70},{"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":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71MDVASBCV46T2H13DENZWE","clickhousectl-local-dev",null,"Use when a user wants to build an application with ClickHouse, set up a local ClickHouse development environment, install ClickHouse, create a local server, create tables, or start developing with ClickHouse. Covers the full flow from zero to a working local ClickHouse setup.","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\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_clickhouse_clickhousectl_local_dev\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"dev","clickhousectl local dev","local dev","local","flow","install","build","server","create","with","when","local server","use","up","environment","clickhouse","development","ZeRO","SET","development environment","2026-11-10 10:56:23",false,"---\nname: clickhousectl-local-dev\ndescription: Use when a user wants to build an application with ClickHouse, set up a local ClickHouse development environment, install ClickHouse, create a local server, create tables, or start developing with ClickHouse. Covers the full flow from zero to a working local ClickHouse setup.\nlicense: Apache-2.0\nmetadata:\n  author: ClickHouse Inc\n  version: \"0.1.0\"\n---\n\n# Local ClickHouse Development Setup\n\nThis skill walks through setting up a complete local ClickHouse development environment using `clickhousectl`. Follow these steps in order.\n\n## When to Apply\n\nUse this skill when the user wants to:\n- Build an application that needs an analytical database or ClickHouse specifically\n- Set up a local ClickHouse instance for development\n- Install ClickHouse on their machine\n- Create tables and start querying ClickHouse locally\n- Prototype or experiment with ClickHouse\n\n---\n\n## Step 1: Install clickhousectl\n\nCheck if `clickhousectl` is already available:\n\n```bash\nwhich clickhousectl\n```\n\nIf not found, install it:\n\n```bash\ncurl -fsSL https:\u002F\u002Fclickhouse.com\u002Fcli | sh\n```\n\nThis installs `clickhousectl` to `~\u002F.local\u002Fbin\u002Fclickhousectl` and creates a `chctl` alias.\n\n**If the command is still not found after install:** The user may need to add `~\u002F.local\u002Fbin` to their PATH or open a new terminal session. Suggest:\n\n```bash\nexport PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"\n```\n\n---\n\n## Step 2: Install ClickHouse\n\nInstall the latest stable ClickHouse version:\n\n```bash\nclickhousectl local install stable\n```\n\nThis downloads the ClickHouse binary to `~\u002F.clickhouse\u002Fversions\u002F`. The binary is shared across projects so it only needs to be downloaded once.\n\n**Alternative version specifiers** (use if the user has a specific need):\n- `lts` — latest long-term support release\n- `25.12` — latest patch of a specific minor version\n- `25.12.5.44` — exact version\n\nSet the installed version as the default:\n\n```bash\nclickhousectl local use stable\n```\n\n---\n\n## Step 3: Initialize the project\n\nFrom the user's project root directory:\n\n```bash\nclickhousectl local init\n```\n\nThis creates a standard folder structure:\n\n```\nclickhouse\u002F\n  tables\u002F                 # CREATE TABLE statements\n  materialized_views\u002F     # Materialized view definitions\n  queries\u002F                # Saved queries\n  seed\u002F                   # Seed data \u002F INSERT statements\n```\n\n**Note:** This step is optional. If the user already has their own folder structure for SQL files, skip this and adapt the later steps to use their paths.\n\n---\n\n## Step 4: Start a local server\n\n```bash\nclickhousectl local server start --name \u003Cname>\n```\n\nThis starts a ClickHouse server in the background. Server data is stored in `.clickhouse\u002Fservers\u002F\u003Canem>\u002Fdata\u002F` within the project directory.\n\n**To check running servers and see their exposed ports:**\n\n```bash\nclickhousectl local server list\n```\n\n---\n\n## Step 5: Create the schema\n\nBased on the user's application requirements, write CREATE TABLE SQL files.\n\n**Write each table definition to its own file** in `clickhouse\u002Ftables\u002F`:\n\n```bash\n# Example: clickhouse\u002Ftables\u002Fevents.sql\n```\n\n```sql\nCREATE TABLE IF NOT EXISTS events (\n    timestamp DateTime,\n    user_id UInt32,\n    event_type LowCardinality(String),\n    properties String\n)\nENGINE = MergeTree()\nORDER BY (event_type, timestamp)\n```\n\nWhen designing schemas, if the `clickhouse-best-practices` skill is available, consult it for guidance on ORDER BY column selection, data types, and partitioning.\n\n**Apply the schema to the running server:**\n\n```bash\nclickhousectl local client --name \u003Cname> --queries-file clickhouse\u002Ftables\u002Fevents.sql\n```\n\n---\n\n## Step 6: Seed data (optional)\n\nIf the user needs sample data for development, write INSERT statements to `clickhouse\u002Fseed\u002F`:\n\n```bash\n# Example: clickhouse\u002Fseed\u002Fevents.sql\n```\n\n```sql\nINSERT INTO events (timestamp, user_id, event_type, properties) VALUES\n    ('2024-01-01 00:00:00', 1, 'page_view', '{\"page\": \"\u002Fhome\"}'),\n    ('2024-01-01 00:01:00', 2, 'click', '{\"button\": \"signup\"}');\n```\n\n**Apply seed data:**\n\n```bash\nclickhousectl local client --name \u003Cname> --queries-file clickhouse\u002Fseed\u002Fevents.sql\n```\n\n---\n\n## Step 7: Verify the setup\n\nConfirm tables were created:\n\n```bash\nclickhousectl local client --name \u003Cname> --query \"SHOW TABLES\"\n```\n\nRun a test query:\n\n```bash\nclickhousectl local client --name \u003Cname> --query \"SELECT count() FROM events\"\n```\n\n---\n\nIf the user wants to use a managed ClickHouse service, use the `clickhousectl-cloud-deploy` skill to help the user deploy to ClickHouse Cloud.\n","# Local ClickHouse Development Setup\n\nThis skill walks through setting up a complete local ClickHouse development environment using `clickhousectl`. Follow these steps in order.\n\n## When to Apply\n\nUse this skill when the user wants to:\n- Build an application that needs an analytical database or ClickHouse specifically\n- Set up a local ClickHouse instance for development\n- Install ClickHouse on their machine\n- Create tables and start querying ClickHouse locally\n- Prototype or experiment with ClickHouse\n\n---\n\n## Step 1: Install clickhousectl\n\nCheck if `clickhousectl` is already available:\n\n```bash\nwhich clickhousectl\n```\n\nIf not found, install it:\n\n```bash\ncurl -fsSL https:\u002F\u002Fclickhouse.com\u002Fcli | sh\n```\n\nThis installs `clickhousectl` to `~\u002F.local\u002Fbin\u002Fclickhousectl` and creates a `chctl` alias.\n\n**If the command is still not found after install:** The user may need to add `~\u002F.local\u002Fbin` to their PATH or open a new terminal session. Suggest:\n\n```bash\nexport PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"\n```\n\n---\n\n## Step 2: Install ClickHouse\n\nInstall the latest stable ClickHouse version:\n\n```bash\nclickhousectl local install stable\n```\n\nThis downloads the ClickHouse binary to `~\u002F.clickhouse\u002Fversions\u002F`. The binary is shared across projects so it only needs to be downloaded once.\n\n**Alternative version specifiers** (use if the user has a specific need):\n- `lts` — latest long-term support release\n- `25.12` — latest patch of a specific minor version\n- `25.12.5.44` — exact version\n\nSet the installed version as the default:\n\n```bash\nclickhousectl local use stable\n```\n\n---\n\n## Step 3: Initialize the project\n\nFrom the user's project root directory:\n\n```bash\nclickhousectl local init\n```\n\nThis creates a standard folder structure:\n\n```\nclickhouse\u002F\n  tables\u002F                 # CREATE TABLE statements\n  materialized_views\u002F     # Materialized view definitions\n  queries\u002F                # Saved queries\n  seed\u002F                   # Seed data \u002F INSERT statements\n```\n\n**Note:** This step is optional. If the user already has their own folder structure for SQL files, skip this and adapt the later steps to use their paths.\n\n---\n\n## Step 4: Start a local server\n\n```bash\nclickhousectl local server start --name \u003Cname>\n```\n\nThis starts a ClickHouse server in the background. Server data is stored in `.clickhouse\u002Fservers\u002F\u003Canem>\u002Fdata\u002F` within the project directory.\n\n**To check running servers and see their exposed ports:**\n\n```bash\nclickhousectl local server list\n```\n\n---\n\n## Step 5: Create the schema\n\nBased on the user's application requirements, write CREATE TABLE SQL files.\n\n**Write each table definition to its own file** in `clickhouse\u002Ftables\u002F`:\n\n```bash\n# Example: clickhouse\u002Ftables\u002Fevents.sql\n```\n\n```sql\nCREATE TABLE IF NOT EXISTS events (\n    timestamp DateTime,\n    user_id UInt32,\n    event_type LowCardinality(String),\n    properties String\n)\nENGINE = MergeTree()\nORDER BY (event_type, timestamp)\n```\n\nWhen designing schemas, if the `clickhouse-best-practices` skill is available, consult it for guidance on ORDER BY column selection, data types, and partitioning.\n\n**Apply the schema to the running server:**\n\n```bash\nclickhousectl local client --name \u003Cname> --queries-file clickhouse\u002Ftables\u002Fevents.sql\n```\n\n---\n\n## Step 6: Seed data (optional)\n\nIf the user needs sample data for development, write INSERT statements to `clickhouse\u002Fseed\u002F`:\n\n```bash\n# Example: clickhouse\u002Fseed\u002Fevents.sql\n```\n\n```sql\nINSERT INTO events (timestamp, user_id, event_type, properties) VALUES\n    ('2024-01-01 00:00:00', 1, 'page_view', '{\"page\": \"\u002Fhome\"}'),\n    ('2024-01-01 00:01:00', 2, 'click', '{\"button\": \"signup\"}');\n```\n\n**Apply seed data:**\n\n```bash\nclickhousectl local client --name \u003Cname> --queries-file clickhouse\u002Fseed\u002Fevents.sql\n```\n\n---\n\n## Step 7: Verify the setup\n\nConfirm tables were created:\n\n```bash\nclickhousectl local client --name \u003Cname> --query \"SHOW TABLES\"\n```\n\nRun a test query:\n\n```bash\nclickhousectl local client --name \u003Cname> --query \"SELECT count() FROM events\"\n```\n\n---\n\nIf the user wants to use a managed ClickHouse service, use the `clickhousectl-cloud-deploy` skill to help the user deploy to ClickHouse Cloud.\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"version":46},"ClickHouse Inc","0.1.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_clickhouse_clickhousectl_local_dev",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill clickhousectl-local-dev",{"tool":62,"command":63},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill clickhousectl-local-dev",{"tool":65,"command":66},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill clickhousectl-local-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_clickhouse_clickhousectl_local_dev\u002Fskill.md",true,[],[71,103,126,148,167,190],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":102},"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",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[84,85,86,87,88,89,90,91,92,93,94,95,96,97,29,98,99,100,27,101],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","libraries","2026-11-10 13:02:02",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":102},"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",[109],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[84,111,112,88,113,114,115,116,97,117,29,118,98,119,120,121,122,123,124,125],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":102},"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",[132],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[84,134,135,88,136,116,137,29,138,118,98,139,140,141,142,143,144,145,146,147],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":102},"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",[154],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[156,88,157,144,158,159,160,161,147,162,163,31,29,164,118,98,165,166,99,84],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":102},"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",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000010","后端与接口",[177,178,179,180,136,181,182,183,125,145,116,184,185,137,186,31,187,188,189,29],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":197,"publishedAt":39},"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",[196],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[198,199,200,201,202,94,203,161,204,97,205,206,29,84,207,208,26,209,210,211],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","markdown","rendering","vue"]