[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQCKS661FZ7TX3SP7PAQ4":3,"skill-same:01M70FQCKS661FZ7TX3SP7PAQ4":61},{"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":28,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M70FQCKS661FZ7TX3SP7PAQ4","react",null,"Must always be enabled when writing\u002Freviewing React code.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fd-kimuson-dotfiles\u002Fclaude-code\u002Fskills\u002Freact\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,29,30,31],"writing","when","code","2026-11-10 10:12:30",false,"---\nname: react\ndescription: Must always be enabled when writing\u002Freviewing React code.\n---\n\n\u003Crole>\nYou are implementing React components following modern best practices. Your goal is to write clean, performant React code that avoids unnecessary Effects and follows established patterns.\n\u003C\u002Frole>\n\n\u003Ccore_principles>\n## Core Principles\n\n### 1. Minimize useEffect Usage\n**Think harder before adding useEffect.** Most scenarios have better alternatives:\n\n\u003Cwhen_not_to_use_effect>\n#### When NOT to Use useEffect\n\n**Data transformation for rendering**:\n- ❌ Don't: Use Effect to compute derived state\n- ✅ Do: Calculate during render at top level\n```tsx\n\u002F\u002F ❌ Bad: Cascading updates\nconst [filteredItems, setFilteredItems] = useState\u003CItem[]>([]);\nuseEffect(() => {\n  setFilteredItems(items.filter(item => item.active));\n}, [items]);\n\n\u002F\u002F ✅ Good: Direct computation\nconst filteredItems = items.filter(item => item.active);\n```\n\n**Handling user events**:\n- ❌ Don't: Use Effect to respond to user actions\n- ✅ Do: Handle logic in event handlers\n```tsx\n\u002F\u002F ❌ Bad: Lost interaction context\nuseEffect(() => {\n  if (buttonClicked) {\n    submitForm();\n  }\n}, [buttonClicked]);\n\n\u002F\u002F ✅ Good: Explicit intent\nconst handleSubmit = () => {\n  submitForm();\n};\n```\n\n**Caching expensive computations**:\n- ❌ Don't: Store computed results in state via Effects\n- ✅ Do: Use useMemo\n```tsx\n\u002F\u002F ❌ Bad: Manual memoization\nconst [expensiveResult, setExpensiveResult] = useState\u003CResult | null>(null);\nuseEffect(() => {\n  setExpensiveResult(computeExpensiveValue(data));\n}, [data]);\n\n\u002F\u002F ✅ Good: useMemo\nconst expensiveResult = useMemo(() => computeExpensiveValue(data), [data]);\n```\n\n**Resetting state on prop changes**:\n- ❌ Don't: Use Effect to reset state\n- ✅ Do: Use key prop to force remount\n```tsx\n\u002F\u002F ❌ Bad: Manual synchronization\nuseEffect(() => {\n  setLocalState(defaultValue);\n}, [userId]);\n\n\u002F\u002F ✅ Good: Key-based reset\n\u003CProfile key={userId} userId={userId} \u002F>\n```\n\u003C\u002Fwhen_not_to_use_effect>\n\n\u003Clegitimate_use_cases>\n#### Legitimate useEffect Use Cases\n\n**Only use Effects for**:\n1. Synchronizing with external systems (browser APIs, third-party widgets)\n2. Data fetching with proper cleanup (avoid race conditions)\n3. Subscriptions (prefer useSyncExternalStore when possible)\n\n**Pattern for data fetching** (if not using query client):\n```tsx\nuseEffect(() => {\n  let ignore = false;\n\n  async function fetchData() {\n    const result = await api.getData();\n    if (!ignore) {\n      setData(result);\n    }\n  }\n\n  fetchData();\n  return () => { ignore = true; }; \u002F\u002F Cleanup to prevent race conditions\n}, [dependency]);\n```\n\u003C\u002Flegitimate_use_cases>\n\u003C\u002Fcore_principles>\n\n\u003Ccomponent_definition>\n### 2. Component Definition Style\n\n**Always use FC type annotation**:\n\n```tsx\nimport { FC, PropsWithChildren } from 'react';\n\n\u002F\u002F For components without children\ntype ButtonProps {\n  label: string;\n  onClick: () => void;\n}\n\nconst Button: FC\u003CButtonProps> = ({ label, onClick }) => {\n  return \u003Cbutton onClick={onClick}>{label}\u003C\u002Fbutton>;\n};\n\n\u002F\u002F For components that accept children\ntype CardProps {\n  title: string;\n}\n\nconst Card: FC\u003CPropsWithChildren\u003CCardProps>> = ({ title, children }) => {\n  return (\n    \u003Cdiv>\n      \u003Ch2>{title}\u003C\u002Fh2>\n      \u003Cdiv>{children}\u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  );\n};\n```\n\n**Never use function declaration syntax**:\n```tsx\n\u002F\u002F ❌ Bad: Avoid this style\nfunction MyComponent(props: Props) {\n  return \u003Cdiv \u002F>;\n}\n```\n\u003C\u002Fcomponent_definition>\n\n\u003Capi_requests>\n### 3. API Request Handling\n\n**Never use fetch directly in components.** Always use the project's query client.\n\n\u003Cdetection_workflow>\n#### Detection Workflow\n\n1. **Check project dependencies** in package.json:\n   - `@apollo\u002Fclient` → Use Apollo Client hooks\n   - `@tanstack\u002Freact-query` → Use Tanstack Query hooks\n   - `swr` → Use SWR hooks\n\n2. **Search for existing usage patterns**:\n   - Look for `useQuery`, `useMutation`, `useSWR`, `useApolloClient` in codebase\n   - Follow established patterns for consistency\n\n3. **Apply appropriate client**:\n\n\u003Capollo_client>\n**Apollo Client (GraphQL)**:\n```tsx\nimport { useQuery, useMutation, gql } from '@apollo\u002Fclient';\n\nconst GET_USER = gql`\n  query GetUser($id: ID!) {\n    user(id: $id) {\n      id\n      name\n      email\n    }\n  }\n`;\n\nconst UserProfile: FC\u003C{ userId: string }> = ({ userId }) => {\n  const { data, loading, error } = useQuery(GET_USER, {\n    variables: { id: userId },\n  });\n\n  if (loading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorMessage error={error} \u002F>;\n\n  return \u003Cdiv>{data.user.name}\u003C\u002Fdiv>;\n};\n\n\u002F\u002F Mutations\nconst UPDATE_USER = gql`\n  mutation UpdateUser($id: ID!, $name: String!) {\n    updateUser(id: $id, name: $name) {\n      id\n      name\n    }\n  }\n`;\n\nconst EditForm: FC = () => {\n  const [updateUser, { loading }] = useMutation(UPDATE_USER);\n\n  const handleSubmit = async (values: FormValues) => {\n    await updateUser({ variables: { id: values.id, name: values.name } });\n  };\n\n  return \u003Cform onSubmit={handleSubmit}>...\u003C\u002Fform>;\n};\n```\n\u003C\u002Fapollo_client>\n\n\u003Ctanstack_query>\n**Tanstack Query (REST)**:\n```tsx\nimport { useQuery, useMutation, useQueryClient } from '@tanstack\u002Freact-query';\n\nconst UserProfile: FC\u003C{ userId: string }> = ({ userId }) => {\n  const { data, isLoading, error } = useQuery({\n    queryKey: ['user', userId],\n    queryFn: () => api.getUser(userId),\n  });\n\n  if (isLoading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorMessage error={error} \u002F>;\n\n  return \u003Cdiv>{data.name}\u003C\u002Fdiv>;\n};\n\n\u002F\u002F Mutations with cache invalidation\nconst EditForm: FC = () => {\n  const queryClient = useQueryClient();\n\n  const mutation = useMutation({\n    mutationFn: (values: FormValues) => api.updateUser(values),\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['user'] });\n    },\n  });\n\n  const handleSubmit = (values: FormValues) => {\n    mutation.mutate(values);\n  };\n\n  return \u003Cform onSubmit={handleSubmit}>...\u003C\u002Fform>;\n};\n```\n\u003C\u002Ftanstack_query>\n\n\u003Cswr>\n**SWR**:\n```tsx\nimport useSWR from 'swr';\nimport useSWRMutation from 'swr\u002Fmutation';\n\nconst UserProfile: FC\u003C{ userId: string }> = ({ userId }) => {\n  const { data, error, isLoading } = useSWR(\n    `\u002Fapi\u002Fusers\u002F${userId}`,\n    fetcher\n  );\n\n  if (isLoading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorMessage error={error} \u002F>;\n\n  return \u003Cdiv>{data.name}\u003C\u002Fdiv>;\n};\n\n\u002F\u002F Mutations\nconst EditForm: FC = () => {\n  const { trigger, isMutating } = useSWRMutation(\n    '\u002Fapi\u002Fusers',\n    updateUser\n  );\n\n  const handleSubmit = async (values: FormValues) => {\n    await trigger(values);\n  };\n\n  return \u003Cform onSubmit={handleSubmit}>...\u003C\u002Fform>;\n};\n```\n\u003C\u002Fswr>\n\u003C\u002Fdetection_workflow>\n\n**Benefits of query clients**:\n- Automatic caching and deduplication\n- Loading\u002Ferror state management\n- Race condition handling\n- Cache invalidation and refetching\n- Optimistic updates support\n\u003C\u002Fapi_requests>\n\u003C\u002Fcore_principles>\n\n\u003Cworkflow>\n## Implementation Workflow\n\n1. **Before writing component**:\n   - Identify data dependencies and state requirements\n   - Think harder: Can state be derived instead of stored?\n   - Plan event handlers before considering Effects\n\n2. **During implementation**:\n   - Define component with FC type annotation\n   - Calculate derived values at top level\n   - Use useMemo only for expensive computations\n   - Handle user interactions in event handlers\n   - Use query client hooks for API requests\n\n3. **Effect review checklist**:\n   - [ ] Is this synchronizing with an external system?\n   - [ ] Could this be a calculated value instead?\n   - [ ] Should this be in an event handler?\n   - [ ] Am I using the right hook (useMemo, key prop)?\n   - [ ] If data fetching, is query client available?\n\n4. **If Effect is necessary**:\n   - Document why Effect is required\n   - Implement proper cleanup to prevent memory leaks\n   - Handle race conditions for async operations\n\u003C\u002Fworkflow>\n\n\u003Canti_patterns>\n## Anti-Patterns to Avoid\n\n❌ **Chaining Effects**:\n```tsx\n\u002F\u002F Bad: Effects triggering each other\nuseEffect(() => setB(a), [a]);\nuseEffect(() => setC(b), [b]);\n\n\u002F\u002F Good: Direct computation or single event handler\nconst b = computeB(a);\nconst c = computeC(b);\n```\n\n❌ **Effect-based initialization**:\n```tsx\n\u002F\u002F Bad: One-time initialization in Effect\nuseEffect(() => {\n  setData(expensiveInit());\n}, []);\n\n\u002F\u002F Good: useState with initializer\nconst [data] = useState(() => expensiveInit());\n```\n\n❌ **Direct fetch calls**:\n```tsx\n\u002F\u002F Bad: Manual fetch in component\nuseEffect(() => {\n  fetch('\u002Fapi\u002Fdata').then(res => res.json()).then(setData);\n}, []);\n\n\u002F\u002F Good: Use query client\nconst { data } = useQuery({ queryKey: ['data'], queryFn: fetchData });\n```\n\u003C\u002Fanti_patterns>\n","\u003Crole>\nYou are implementing React components following modern best practices. Your goal is to write clean, performant React code that avoids unnecessary Effects and follows established patterns.\n\u003C\u002Frole>\n\n\u003Ccore_principles>\n## Core Principles\n\n### 1. Minimize useEffect Usage\n**Think harder before adding useEffect.** Most scenarios have better alternatives:\n\n\u003Cwhen_not_to_use_effect>\n#### When NOT to Use useEffect\n\n**Data transformation for rendering**:\n- ❌ Don't: Use Effect to compute derived state\n- ✅ Do: Calculate during render at top level\n```tsx\n\u002F\u002F ❌ Bad: Cascading updates\nconst [filteredItems, setFilteredItems] = useState\u003CItem[]>([]);\nuseEffect(() => {\n  setFilteredItems(items.filter(item => item.active));\n}, [items]);\n\n\u002F\u002F ✅ Good: Direct computation\nconst filteredItems = items.filter(item => item.active);\n```\n\n**Handling user events**:\n- ❌ Don't: Use Effect to respond to user actions\n- ✅ Do: Handle logic in event handlers\n```tsx\n\u002F\u002F ❌ Bad: Lost interaction context\nuseEffect(() => {\n  if (buttonClicked) {\n    submitForm();\n  }\n}, [buttonClicked]);\n\n\u002F\u002F ✅ Good: Explicit intent\nconst handleSubmit = () => {\n  submitForm();\n};\n```\n\n**Caching expensive computations**:\n- ❌ Don't: Store computed results in state via Effects\n- ✅ Do: Use useMemo\n```tsx\n\u002F\u002F ❌ Bad: Manual memoization\nconst [expensiveResult, setExpensiveResult] = useState\u003CResult | null>(null);\nuseEffect(() => {\n  setExpensiveResult(computeExpensiveValue(data));\n}, [data]);\n\n\u002F\u002F ✅ Good: useMemo\nconst expensiveResult = useMemo(() => computeExpensiveValue(data), [data]);\n```\n\n**Resetting state on prop changes**:\n- ❌ Don't: Use Effect to reset state\n- ✅ Do: Use key prop to force remount\n```tsx\n\u002F\u002F ❌ Bad: Manual synchronization\nuseEffect(() => {\n  setLocalState(defaultValue);\n}, [userId]);\n\n\u002F\u002F ✅ Good: Key-based reset\n\u003CProfile key={userId} userId={userId} \u002F>\n```\n\u003C\u002Fwhen_not_to_use_effect>\n\n\u003Clegitimate_use_cases>\n#### Legitimate useEffect Use Cases\n\n**Only use Effects for**:\n1. Synchronizing with external systems (browser APIs, third-party widgets)\n2. Data fetching with proper cleanup (avoid race conditions)\n3. Subscriptions (prefer useSyncExternalStore when possible)\n\n**Pattern for data fetching** (if not using query client):\n```tsx\nuseEffect(() => {\n  let ignore = false;\n\n  async function fetchData() {\n    const result = await api.getData();\n    if (!ignore) {\n      setData(result);\n    }\n  }\n\n  fetchData();\n  return () => { ignore = true; }; \u002F\u002F Cleanup to prevent race conditions\n}, [dependency]);\n```\n\u003C\u002Flegitimate_use_cases>\n\u003C\u002Fcore_principles>\n\n\u003Ccomponent_definition>\n### 2. Component Definition Style\n\n**Always use FC type annotation**:\n\n```tsx\nimport { FC, PropsWithChildren } from 'react';\n\n\u002F\u002F For components without children\ntype ButtonProps {\n  label: string;\n  onClick: () => void;\n}\n\nconst Button: FC\u003CButtonProps> = ({ label, onClick }) => {\n  return \u003Cbutton onClick={onClick}>{label}\u003C\u002Fbutton>;\n};\n\n\u002F\u002F For components that accept children\ntype CardProps {\n  title: string;\n}\n\nconst Card: FC\u003CPropsWithChildren\u003CCardProps>> = ({ title, children }) => {\n  return (\n    \u003Cdiv>\n      \u003Ch2>{title}\u003C\u002Fh2>\n      \u003Cdiv>{children}\u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  );\n};\n```\n\n**Never use function declaration syntax**:\n```tsx\n\u002F\u002F ❌ Bad: Avoid this style\nfunction MyComponent(props: Props) {\n  return \u003Cdiv \u002F>;\n}\n```\n\u003C\u002Fcomponent_definition>\n\n\u003Capi_requests>\n### 3. API Request Handling\n\n**Never use fetch directly in components.** Always use the project's query client.\n\n\u003Cdetection_workflow>\n#### Detection Workflow\n\n1. **Check project dependencies** in package.json:\n   - `@apollo\u002Fclient` → Use Apollo Client hooks\n   - `@tanstack\u002Freact-query` → Use Tanstack Query hooks\n   - `swr` → Use SWR hooks\n\n2. **Search for existing usage patterns**:\n   - Look for `useQuery`, `useMutation`, `useSWR`, `useApolloClient` in codebase\n   - Follow established patterns for consistency\n\n3. **Apply appropriate client**:\n\n\u003Capollo_client>\n**Apollo Client (GraphQL)**:\n```tsx\nimport { useQuery, useMutation, gql } from '@apollo\u002Fclient';\n\nconst GET_USER = gql`\n  query GetUser($id: ID!) {\n    user(id: $id) {\n      id\n      name\n      email\n    }\n  }\n`;\n\nconst UserProfile: FC\u003C{ userId: string }> = ({ userId }) => {\n  const { data, loading, error } = useQuery(GET_USER, {\n    variables: { id: userId },\n  });\n\n  if (loading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorMessage error={error} \u002F>;\n\n  return \u003Cdiv>{data.user.name}\u003C\u002Fdiv>;\n};\n\n\u002F\u002F Mutations\nconst UPDATE_USER = gql`\n  mutation UpdateUser($id: ID!, $name: String!) {\n    updateUser(id: $id, name: $name) {\n      id\n      name\n    }\n  }\n`;\n\nconst EditForm: FC = () => {\n  const [updateUser, { loading }] = useMutation(UPDATE_USER);\n\n  const handleSubmit = async (values: FormValues) => {\n    await updateUser({ variables: { id: values.id, name: values.name } });\n  };\n\n  return \u003Cform onSubmit={handleSubmit}>...\u003C\u002Fform>;\n};\n```\n\u003C\u002Fapollo_client>\n\n\u003Ctanstack_query>\n**Tanstack Query (REST)**:\n```tsx\nimport { useQuery, useMutation, useQueryClient } from '@tanstack\u002Freact-query';\n\nconst UserProfile: FC\u003C{ userId: string }> = ({ userId }) => {\n  const { data, isLoading, error } = useQuery({\n    queryKey: ['user', userId],\n    queryFn: () => api.getUser(userId),\n  });\n\n  if (isLoading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorMessage error={error} \u002F>;\n\n  return \u003Cdiv>{data.name}\u003C\u002Fdiv>;\n};\n\n\u002F\u002F Mutations with cache invalidation\nconst EditForm: FC = () => {\n  const queryClient = useQueryClient();\n\n  const mutation = useMutation({\n    mutationFn: (values: FormValues) => api.updateUser(values),\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['user'] });\n    },\n  });\n\n  const handleSubmit = (values: FormValues) => {\n    mutation.mutate(values);\n  };\n\n  return \u003Cform onSubmit={handleSubmit}>...\u003C\u002Fform>;\n};\n```\n\u003C\u002Ftanstack_query>\n\n\u003Cswr>\n**SWR**:\n```tsx\nimport useSWR from 'swr';\nimport useSWRMutation from 'swr\u002Fmutation';\n\nconst UserProfile: FC\u003C{ userId: string }> = ({ userId }) => {\n  const { data, error, isLoading } = useSWR(\n    `\u002Fapi\u002Fusers\u002F${userId}`,\n    fetcher\n  );\n\n  if (isLoading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorMessage error={error} \u002F>;\n\n  return \u003Cdiv>{data.name}\u003C\u002Fdiv>;\n};\n\n\u002F\u002F Mutations\nconst EditForm: FC = () => {\n  const { trigger, isMutating } = useSWRMutation(\n    '\u002Fapi\u002Fusers',\n    updateUser\n  );\n\n  const handleSubmit = async (values: FormValues) => {\n    await trigger(values);\n  };\n\n  return \u003Cform onSubmit={handleSubmit}>...\u003C\u002Fform>;\n};\n```\n\u003C\u002Fswr>\n\u003C\u002Fdetection_workflow>\n\n**Benefits of query clients**:\n- Automatic caching and deduplication\n- Loading\u002Ferror state management\n- Race condition handling\n- Cache invalidation and refetching\n- Optimistic updates support\n\u003C\u002Fapi_requests>\n\u003C\u002Fcore_principles>\n\n\u003Cworkflow>\n## Implementation Workflow\n\n1. **Before writing component**:\n   - Identify data dependencies and state requirements\n   - Think harder: Can state be derived instead of stored?\n   - Plan event handlers before considering Effects\n\n2. **During implementation**:\n   - Define component with FC type annotation\n   - Calculate derived values at top level\n   - Use useMemo only for expensive computations\n   - Handle user interactions in event handlers\n   - Use query client hooks for API requests\n\n3. **Effect review checklist**:\n   - [ ] Is this synchronizing with an external system?\n   - [ ] Could this be a calculated value instead?\n   - [ ] Should this be in an event handler?\n   - [ ] Am I using the right hook (useMemo, key prop)?\n   - [ ] If data fetching, is query client available?\n\n4. **If Effect is necessary**:\n   - Document why Effect is required\n   - Implement proper cleanup to prevent memory leaks\n   - Handle race conditions for async operations\n\u003C\u002Fworkflow>\n\n\u003Canti_patterns>\n## Anti-Patterns to Avoid\n\n❌ **Chaining Effects**:\n```tsx\n\u002F\u002F Bad: Effects triggering each other\nuseEffect(() => setB(a), [a]);\nuseEffect(() => setC(b), [b]);\n\n\u002F\u002F Good: Direct computation or single event handler\nconst b = computeB(a);\nconst c = computeC(b);\n```\n\n❌ **Effect-based initialization**:\n```tsx\n\u002F\u002F Bad: One-time initialization in Effect\nuseEffect(() => {\n  setData(expensiveInit());\n}, []);\n\n\u002F\u002F Good: useState with initializer\nconst [data] = useState(() => expensiveInit());\n```\n\n❌ **Direct fetch calls**:\n```tsx\n\u002F\u002F Bad: Manual fetch in component\nuseEffect(() => {\n  fetch('\u002Fapi\u002Fdata').then(res => res.json()).then(setData);\n}, []);\n\n\u002F\u002F Good: Use query client\nconst { data } = useQuery({ queryKey: ['data'], queryFn: fetchData });\n```\n\u003C\u002Fanti_patterns>\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fd-kimuson-dotfiles\u002Fclaude-code\u002Fskills\u002Freact",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill react",{"tool":53,"command":54},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill react",{"tool":56,"command":57},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill react","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fd-kimuson-dotfiles\u002Fclaude-code\u002Fskills\u002Freact\u002FSKILL.md",true,[],[62,71,79,87,95,103],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":70},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":70},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":70},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"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":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":70},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":70},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]