[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MPFYEMSJF0PBMNFQFDSCG":3,"skill-same:01M71MPFYEMSJF0PBMNFQFDSCG":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71MPFYEMSJF0PBMNFQFDSCG","acquire-codebase-knowledge",null,"Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like \"map this codebase\", \"document this architecture\", \"onboard me to this repo\", or \"create codebase docs\". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_github_acquire_codebase_knowledge\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"knowledge","acquire","codebase","acquire codebase knowledge","when","document","Existing","use","map","python","trigger","discovery","repo","for","fixes","codebase docs","feature implementation","platform","feature","do","2026-11-10 10:56:23",false,"---\nname: acquire-codebase-knowledge\ndescription: 'Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like \"map this codebase\", \"document this architecture\", \"onboard me to this repo\", or \"create codebase docs\". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.'\nlicense: MIT\ncompatibility: 'Cross-platform. Requires Python 3.8+ and git.'\nmetadata:\n  version: \"1.3\"\n---\n\n# Acquire Codebase Knowledge\n\nProduces seven populated documents in `docs\u002Fcodebase\u002F` covering everything needed to work effectively on the project.\n\n## Output Contract (Required)\n\nBefore finishing, all of the following must be true:\n\n1. Exactly these files exist in `docs\u002Fcodebase\u002F`: `STACK.md`, `STRUCTURE.md`, `ARCHITECTURE.md`, `CONVENTIONS.md`, `INTEGRATIONS.md`, `TESTING.md`, `CONCERNS.md`.\n2. Every claim is traceable to source files, config, or terminal output.\n3. Unknowns are marked as `[TODO]`; intent-dependent decisions are marked `[ASK USER]`.\n\n## Workflow\n\n```\n- [ ] Phase 1: Run scan, read intent documents\n- [ ] Phase 2: Investigate each documentation area\n- [ ] Phase 3: Populate all seven docs in docs\u002Fcodebase\u002F\n- [ ] Phase 4: Validate docs, present findings, resolve all [ASK USER] items\n```\n\n### Phase 1: Scan and Read Intent\n\n1. Run the scan script from the target project root:\n   ```bash\n   python3 \"$SKILL_ROOT\u002Fscripts\u002Fscan.py\" --output docs\u002Fcodebase\u002F.codebase-scan.txt\n   ```\n\n2. Search for `PRD`, `TRD`, `README`, `ROADMAP`, `SPEC`, `DESIGN` files and read them.\n3. Summarise the stated project intent before reading any source code.\n\n### Phase 2: Investigate\n\nUse the scan output to answer questions for each of the seven templates.\n\n### Phase 3: Populate Templates\n\nFill in this order:\n1. `STACK.md` — language, runtime, frameworks, all dependencies\n2. `STRUCTURE.md` — directory layout, entry points, key files\n3. `ARCHITECTURE.md` — layers, patterns, data flow\n4. `CONVENTIONS.md` — naming, formatting, error handling, imports\n5. `INTEGRATIONS.md` — external APIs, databases, auth, monitoring\n6. `TESTING.md` — test frameworks, coverage, CI\n7. `CONCERNS.md` — tech debt, risks, open questions\n","# Acquire Codebase Knowledge\n\nProduces seven populated documents in `docs\u002Fcodebase\u002F` covering everything needed to work effectively on the project.\n\n## Output Contract (Required)\n\nBefore finishing, all of the following must be true:\n\n1. Exactly these files exist in `docs\u002Fcodebase\u002F`: `STACK.md`, `STRUCTURE.md`, `ARCHITECTURE.md`, `CONVENTIONS.md`, `INTEGRATIONS.md`, `TESTING.md`, `CONCERNS.md`.\n2. Every claim is traceable to source files, config, or terminal output.\n3. Unknowns are marked as `[TODO]`; intent-dependent decisions are marked `[ASK USER]`.\n\n## Workflow\n\n```\n- [ ] Phase 1: Run scan, read intent documents\n- [ ] Phase 2: Investigate each documentation area\n- [ ] Phase 3: Populate all seven docs in docs\u002Fcodebase\u002F\n- [ ] Phase 4: Validate docs, present findings, resolve all [ASK USER] items\n```\n\n### Phase 1: Scan and Read Intent\n\n1. Run the scan script from the target project root:\n   ```bash\n   python3 \"$SKILL_ROOT\u002Fscripts\u002Fscan.py\" --output docs\u002Fcodebase\u002F.codebase-scan.txt\n   ```\n\n2. Search for `PRD`, `TRD`, `README`, `ROADMAP`, `SPEC`, `DESIGN` files and read them.\n3. Summarise the stated project intent before reading any source code.\n\n### Phase 2: Investigate\n\nUse the scan output to answer questions for each of the seven templates.\n\n### Phase 3: Populate Templates\n\nFill in this order:\n1. `STACK.md` — language, runtime, frameworks, all dependencies\n2. `STRUCTURE.md` — directory layout, entry points, key files\n3. `ARCHITECTURE.md` — layers, patterns, data flow\n4. `CONVENTIONS.md` — naming, formatting, error handling, imports\n5. `INTEGRATIONS.md` — external APIs, databases, auth, monitoring\n6. `TESTING.md` — test frameworks, coverage, CI\n7. `CONCERNS.md` — tech debt, risks, open questions\n",{"name":5,"license":15,"metadata":49,"description":7,"compatibility":51},{"version":50},"1.3","Cross-platform. Requires Python 3.8+ and git.","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_github_acquire_codebase_knowledge",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill acquire-codebase-knowledge",{"tool":67,"command":68},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill acquire-codebase-knowledge",{"tool":70,"command":71},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill acquire-codebase-knowledge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_github_acquire_codebase_knowledge\u002Fskill.md",true,[],[76,106,127,149,168,191],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":105},"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.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,28,100,101,102,103,104],"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":105},"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",[112],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[86,114,115,90,116,117,118,119,99,120,28,121,100,122,123,124,125,41,126,37],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","animations",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":105},"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",[133],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[86,135,136,90,137,119,138,28,139,121,100,140,141,142,143,144,145,146,147,148],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":105},"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",[155],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[157,90,158,145,159,160,161,162,148,163,164,31,28,165,121,100,166,167,101,86],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":105},"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",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[178,179,180,181,137,182,183,184,37,146,119,185,186,138,187,31,188,189,190,28],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":44},"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",[197],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[199,200,201,202,203,96,204,162,205,99,206,207,28,86,208,209,210,211,212,213],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue"]