[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71J0RSD469RY22FP4P73QH5":3,"skill-same:01M71J0RSD469RY22FP4P73QH5":145},{"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":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M71J0RSD469RY22FP4P73QH5","karpathy-coder",null,"Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on \"review my diff\", \"check complexity\", \"am I overcomplicating this\", \"karpathy check\", \"before I commit\", or any code quality concern where the LLM might be overcoding.","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\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"karpathy coder","coder","karpathy","coding","patterns","my","anti-patterns","surgical-changes","code-quality","simplicity","discipline","opencode","cli","review my diff","review","commit","code","when","writing","complexity","2026-11-10 10:12:30",false,"---\nname: karpathy-coder\ndescription: Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on \"review my diff\", \"check complexity\", \"am I overcomplicating this\", \"karpathy check\", \"before I commit\", or any code quality concern where the LLM might be overcoding.\ncontext: fork\nversion: 2.3.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [code-quality, discipline, karpathy, simplicity, surgical-changes, anti-patterns, review]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Karpathy Coder — Active Coding Discipline\n\nDerived from [Andrej Karpathy's observations](https:\u002F\u002Fx.com\u002Fkarpathy\u002Fstatus\u002F2015883857489522876) on LLM coding pitfalls. This is **not just guidelines** — it ships Python tools that detect violations, a review agent, a slash command, and a pre-commit hook.\n\n> \"The models make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, don't seek clarifications, don't surface inconsistencies, don't present tradeoffs, don't push back when they should.\"\n>\n> \"They really like to overcomplicate code and APIs, bloat abstractions, don't clean up dead code... implement a bloated construction over 1000 lines when 100 would do.\"\n>\n> \"LLMs are exceptionally good at looping until they meet specific goals... Don't tell it what to do, give it success criteria and watch it go.\"\n>\n> — Andrej Karpathy\n\n## The four principles\n\n### 1. Think Before Coding\n\n**Don't assume. Don't hide confusion. Surface tradeoffs.**\n\n- State assumptions explicitly. If uncertain, ask.\n- If multiple interpretations exist, present them — don't pick silently.\n- If a simpler approach exists, say so. Push back when warranted.\n- If something is unclear, stop. Name what's confusing. Ask.\n\n### 2. Simplicity First\n\n**Minimum code that solves the problem. Nothing speculative.**\n\n- No features beyond what was asked.\n- No abstractions for single-use code.\n- No \"flexibility\" or \"configurability\" that wasn't requested.\n- No error handling for impossible scenarios.\n- If you write 200 lines and it could be 50, rewrite it.\n\n**The test:** Would a senior engineer say this is overcomplicated? If yes, simplify.\n\n### 3. Surgical Changes\n\n**Touch only what you must. Clean up only your own mess.**\n\n- Don't \"improve\" adjacent code, comments, or formatting.\n- Don't refactor things that aren't broken.\n- Match existing style, even if you'd do it differently.\n- If you notice unrelated dead code, mention it — don't delete it.\n- Remove imports\u002Fvariables\u002Ffunctions that YOUR changes made unused.\n- Don't remove pre-existing dead code unless asked.\n\n**The test:** Every changed line should trace directly to the user's request.\n\n### 4. Goal-Driven Execution\n\n**Define success criteria. Loop until verified.**\n\n| Instead of... | Transform to... |\n|---|---|\n| \"Add validation\" | \"Write tests for invalid inputs, then make them pass\" |\n| \"Fix the bug\" | \"Write a test that reproduces it, then make it pass\" |\n| \"Refactor X\" | \"Ensure tests pass before and after\" |\n\nFor multi-step tasks, state a brief plan:\n\n```\n1. [Step] → verify: [check]\n2. [Step] → verify: [check]\n3. [Step] → verify: [check]\n```\n\n## Slash command\n\n`\u002Fkarpathy-check` — Run the full 4-principle review on your staged changes.\n\n## Python tools (`scripts\u002F`)\n\nAll tools are stdlib-only. Run with `--help`.\n\n| Script | What it detects |\n|---|---|\n| `complexity_checker.py` | Over-engineering: too many classes, deep nesting, high cyclomatic complexity, unused params, premature abstractions |\n| `diff_surgeon.py` | Diff noise: lines that don't trace to the stated goal — comment changes, style drift, drive-by refactors |\n| `assumption_linter.py` | Hidden assumptions in a plan: unasked features, missing clarifications, silent interpretation choices |\n| `goal_verifier.py` | Weak success criteria: vague plans without verifiable checks, missing test assertions |\n\n## Sub-agent\n\n`karpathy-reviewer` — Runs all 4 principles against a diff. Dispatched by `\u002Fkarpathy-check` or manually before committing.\n\n## Pre-commit hook\n\n`hooks\u002Fkarpathy-gate.sh` — runs `complexity_checker.py` and `diff_surgeon.py` on staged files. Warns (non-blocking) when violations are found. Wire it via `.claude\u002Fsettings.json` or Husky.\n\n## References\n\n- `references\u002Fkarpathy-principles.md` — the source quotes, deeper context, when to relax each principle\n- `references\u002Fanti-patterns.md` — 10+ before\u002Fafter examples across Python, TypeScript, and shell\n- `references\u002Fenforcement-patterns.md` — how to wire hooks, CI integration, team adoption\n\n## When to relax\n\nThese principles bias toward **caution over speed**. For trivial tasks (typo fixes, obvious one-liners), use judgment. The principles matter most on:\n\n- Non-trivial implementations (>20 lines changed)\n- Code you don't fully understand\n- Multi-step tasks with unclear requirements\n- Anything that will be reviewed by humans\n\n## Cross-tool compatibility\n\nInstalls via plugin for Claude Code. For other tools, copy the principles into your schema file:\n\n| Tool | Schema file |\n|---|---|\n| Claude Code | `CLAUDE.md` (auto-loaded by plugin) |\n| Codex CLI | `AGENTS.md` |\n| Cursor | `AGENTS.md` or `.cursorrules` |\n| Antigravity \u002F OpenCode \u002F Gemini CLI | `AGENTS.md` |\n\n## Related skills (chains via `context: fork`)\n\n- **`self-eval`** — honest quality scoring after completing work\n- **`code-reviewer`** — broader code review; karpathy-coder focuses on the 4 LLM-specific pitfalls\n- **`llm-wiki`** — compound knowledge; karpathy-coder ensures you don't overcomplicate while building it\n","# Karpathy Coder — Active Coding Discipline\n\nDerived from [Andrej Karpathy's observations](https:\u002F\u002Fx.com\u002Fkarpathy\u002Fstatus\u002F2015883857489522876) on LLM coding pitfalls. This is **not just guidelines** — it ships Python tools that detect violations, a review agent, a slash command, and a pre-commit hook.\n\n> \"The models make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, don't seek clarifications, don't surface inconsistencies, don't present tradeoffs, don't push back when they should.\"\n>\n> \"They really like to overcomplicate code and APIs, bloat abstractions, don't clean up dead code... implement a bloated construction over 1000 lines when 100 would do.\"\n>\n> \"LLMs are exceptionally good at looping until they meet specific goals... Don't tell it what to do, give it success criteria and watch it go.\"\n>\n> — Andrej Karpathy\n\n## The four principles\n\n### 1. Think Before Coding\n\n**Don't assume. Don't hide confusion. Surface tradeoffs.**\n\n- State assumptions explicitly. If uncertain, ask.\n- If multiple interpretations exist, present them — don't pick silently.\n- If a simpler approach exists, say so. Push back when warranted.\n- If something is unclear, stop. Name what's confusing. Ask.\n\n### 2. Simplicity First\n\n**Minimum code that solves the problem. Nothing speculative.**\n\n- No features beyond what was asked.\n- No abstractions for single-use code.\n- No \"flexibility\" or \"configurability\" that wasn't requested.\n- No error handling for impossible scenarios.\n- If you write 200 lines and it could be 50, rewrite it.\n\n**The test:** Would a senior engineer say this is overcomplicated? If yes, simplify.\n\n### 3. Surgical Changes\n\n**Touch only what you must. Clean up only your own mess.**\n\n- Don't \"improve\" adjacent code, comments, or formatting.\n- Don't refactor things that aren't broken.\n- Match existing style, even if you'd do it differently.\n- If you notice unrelated dead code, mention it — don't delete it.\n- Remove imports\u002Fvariables\u002Ffunctions that YOUR changes made unused.\n- Don't remove pre-existing dead code unless asked.\n\n**The test:** Every changed line should trace directly to the user's request.\n\n### 4. Goal-Driven Execution\n\n**Define success criteria. Loop until verified.**\n\n| Instead of... | Transform to... |\n|---|---|\n| \"Add validation\" | \"Write tests for invalid inputs, then make them pass\" |\n| \"Fix the bug\" | \"Write a test that reproduces it, then make it pass\" |\n| \"Refactor X\" | \"Ensure tests pass before and after\" |\n\nFor multi-step tasks, state a brief plan:\n\n```\n1. [Step] → verify: [check]\n2. [Step] → verify: [check]\n3. [Step] → verify: [check]\n```\n\n## Slash command\n\n`\u002Fkarpathy-check` — Run the full 4-principle review on your staged changes.\n\n## Python tools (`scripts\u002F`)\n\nAll tools are stdlib-only. Run with `--help`.\n\n| Script | What it detects |\n|---|---|\n| `complexity_checker.py` | Over-engineering: too many classes, deep nesting, high cyclomatic complexity, unused params, premature abstractions |\n| `diff_surgeon.py` | Diff noise: lines that don't trace to the stated goal — comment changes, style drift, drive-by refactors |\n| `assumption_linter.py` | Hidden assumptions in a plan: unasked features, missing clarifications, silent interpretation choices |\n| `goal_verifier.py` | Weak success criteria: vague plans without verifiable checks, missing test assertions |\n\n## Sub-agent\n\n`karpathy-reviewer` — Runs all 4 principles against a diff. Dispatched by `\u002Fkarpathy-check` or manually before committing.\n\n## Pre-commit hook\n\n`hooks\u002Fkarpathy-gate.sh` — runs `complexity_checker.py` and `diff_surgeon.py` on staged files. Warns (non-blocking) when violations are found. Wire it via `.claude\u002Fsettings.json` or Husky.\n\n## References\n\n- `references\u002Fkarpathy-principles.md` — the source quotes, deeper context, when to relax each principle\n- `references\u002Fanti-patterns.md` — 10+ before\u002Fafter examples across Python, TypeScript, and shell\n- `references\u002Fenforcement-patterns.md` — how to wire hooks, CI integration, team adoption\n\n## When to relax\n\nThese principles bias toward **caution over speed**. For trivial tasks (typo fixes, obvious one-liners), use judgment. The principles matter most on:\n\n- Non-trivial implementations (>20 lines changed)\n- Code you don't fully understand\n- Multi-step tasks with unclear requirements\n- Anything that will be reviewed by humans\n\n## Cross-tool compatibility\n\nInstalls via plugin for Claude Code. For other tools, copy the principles into your schema file:\n\n| Tool | Schema file |\n|---|---|\n| Claude Code | `CLAUDE.md` (auto-loaded by plugin) |\n| Codex CLI | `AGENTS.md` |\n| Cursor | `AGENTS.md` or `.cursorrules` |\n| Antigravity \u002F OpenCode \u002F Gemini CLI | `AGENTS.md` |\n\n## Related skills (chains via `context: fork`)\n\n- **`self-eval`** — honest quality scoring after completing work\n- **`code-reviewer`** — broader code review; karpathy-coder focuses on the 4 LLM-specific pitfalls\n- **`llm-wiki`** — compound knowledge; karpathy-coder ensures you don't overcomplicate while building it\n",{"name":5,"tags":44,"author":45,"context":46,"license":15,"version":47,"description":7,"compatible_tools":48},[27,29,21,28,26,25,33],"claude-code-skills","fork","2.3.0",[49,50,51,52,30,53],"claude-code","codex-cli","cursor","antigravity","gemini-cli","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder",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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill karpathy-coder",{"tool":69,"command":70},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill karpathy-coder",{"tool":72,"command":73},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill karpathy-coder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002FSKILL.md",true,[77,83,87,91,95,99,103,107,113,117,121,125,129,133,137,141],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",707,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002F.claude-plugin\u002Fplugin.json",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"agents\u002Fkarpathy-reviewer.md",2904,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fagents\u002Fkarpathy-reviewer.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"commands\u002Fkarpathy-check.md",1664,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fcommands\u002Fkarpathy-check.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"expected_outputs\u002Fassumption_linter.json",933,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fexpected_outputs\u002Fassumption_linter.json",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"expected_outputs\u002Fcomplexity_checker.json",584,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fexpected_outputs\u002Fcomplexity_checker.json",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"expected_outputs\u002Fdiff_surgeon.json",158,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fexpected_outputs\u002Fdiff_surgeon.json",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"expected_outputs\u002Fgoal_verifier.json",853,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fexpected_outputs\u002Fgoal_verifier.json",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"hooks\u002Fkarpathy-gate.sh","SCRIPT","脚本",1409,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fhooks\u002Fkarpathy-gate.sh",{"path":114,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":115,"sourceHtmlUrl":116},"README.md",4399,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002FREADME.md",{"path":118,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fanti-patterns.md",4965,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Freferences\u002Fanti-patterns.md",{"path":122,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fenforcement-patterns.md",3751,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Freferences\u002Fenforcement-patterns.md",{"path":126,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fkarpathy-principles.md",3754,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Freferences\u002Fkarpathy-principles.md",{"path":130,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fassumption_linter.py",6830,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fscripts\u002Fassumption_linter.py",{"path":134,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":135,"sourceHtmlUrl":136},"scripts\u002Fcomplexity_checker.py",10976,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fscripts\u002Fcomplexity_checker.py",{"path":138,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":139,"sourceHtmlUrl":140},"scripts\u002Fdiff_surgeon.py",7918,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fscripts\u002Fdiff_surgeon.py",{"path":142,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":143,"sourceHtmlUrl":144},"scripts\u002Fgoal_verifier.py",6633,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fengineering\u002Fkarpathy-coder\u002Fscripts\u002Fgoal_verifier.py",[146,178,201,220,240,263],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":157,"publishedAt":177},"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",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[158,159,160,161,162,163,164,165,166,167,168,169,170,171,36,172,173,174,175,176],"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":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":177},"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",[184],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},[158,186,187,162,188,189,190,191,171,192,36,193,172,194,195,196,197,198,199,200],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":177},"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",[207],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},[158,209,210,162,211,191,37,36,35,193,172,212,213,214,215,216,23,217,218,219],"react best practices","vercel react best practices","best practices","data fetching","react components","next","refactoring","data","Optimization","guidelines","triggers",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":177},"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",[226],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},[228,162,229,23,230,231,232,233,219,234,235,236,36,237,193,172,238,239,173,158],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":244,"categories":245,"keywords":249,"publishedAt":177},"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",[246],{"categoryNo":247,"categoryName":248,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000010","后端与接口",[250,251,252,253,211,254,255,256,200,217,191,257,258,37,259,236,260,261,262,36],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":264,"name":265,"nameZh":6,"description":266,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":267,"categories":268,"keywords":270,"publishedAt":286},"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",[269],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},[271,272,273,274,275,168,276,233,277,171,278,279,36,158,280,281,282,283,284,285],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]