[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQ09SWJAZNQXNXHCKF328":3,"skill-same:01M70FQ09SWJAZNQXNXHCKF328":56},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M70FQ09SWJAZNQXNXHCKF328","typescript",null,"Must always be enabled when writing\u002Freviewing TypeScript 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\u002Fclaude-code\u002Fskills\u002Ftypescript\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,24,25,26],"writing","when","code","2026-11-10 10:12:30",false,"---\nname: typescript\ndescription: Must always be enabled when writing\u002Freviewing TypeScript code.\n---\n\n\u003Cphilosophy>\n## Core Philosophy: Type-Level Verification\n\nLLM-generated code faces inherent challenges with E2E testing and runtime verification. Compensate by maximizing compile-time verification through:\n\n- Algebraic data types (discriminated unions, exhaustive pattern matching)\n- Strict type constraints that make invalid states unrepresentable\n- Type-level proofs over runtime assertions\n\n**Goal**: If it type-checks, it works. Shift as many bugs as possible from runtime to compile-time.\n\u003C\u002Fphilosophy>\n\n\u003Ctype_assertions>\n## Type Assertions: Banned by Default\n\n### Rule: `as` Type Assertions are Prohibited\n\n**Rationale**: Type assertions bypass TypeScript's type system and introduce type unsoundness. They are frequently misused to silence legitimate type errors.\n\n**Policy**:\n- ❌ **Never use** `as` to resolve type errors\n- ❌ **Never use** `as any` or `as unknown as X`\n- ⚠️ **Rare exceptions**: Compiler limitations (e.g., specific generic inference bugs)\n  - If you encounter such cases, **leave the type error unresolved**\n  - Escalate to user with explanation: \"Type error at `path\u002Fto\u002Ffile.ts:123` - requires manual review for potential `as` usage\"\n\n**Why you cannot judge appropriately**:\nAs an LLM, you lack the contextual understanding to determine if a type assertion is truly necessary vs. masking a real type error. When in doubt, preserve type safety.\n\n### Alternative: Fix the Root Cause\n\nInstead of `as`, address the underlying type issue:\n- Refine function signatures\n- Use type guards (`if (typeof x === 'string')`)\n- Employ discriminated unions\n- Add generic constraints\n\u003C\u002Ftype_assertions>\n\n\u003Cstrict_typing>\n## Strict Typing Patterns\n\n### Prefer `as const satisfies` Over Loose Annotations\n\n**Problem with loose typing**:\n```typescript\nconst config: Config = {\n  mode: 'development',  \u002F\u002F Type widened to string\n  port: 3000\n}\n\u002F\u002F config.mode is string, not 'development' | 'production'\n```\n\n**Solution - strict typing with `as const satisfies`**:\n```typescript\nconst config = {\n  mode: 'development',\n  port: 3000\n} as const satisfies Config\n\u002F\u002F config.mode is exactly 'development' (literal type preserved)\n```\n\n**Benefits**:\n- Preserves literal types\n- Catches typos at definition site\n- Enables exhaustive checking in consumers\n- No type widening\n\n**Application**:\n- Configuration objects\n- Constant lookup tables\n- Route definitions\n- Action type constants\n\n### Avoid Explicit Type Annotations When Inference Suffices\n\n```typescript\n\u002F\u002F ❌ Redundant annotation\nconst result: number = calculateTotal(items)\n\n\u002F\u002F ✅ Let TypeScript infer\nconst result = calculateTotal(items)\n```\n\nUse annotations when:\n- Constraining function parameters\n- Enforcing strict object shapes (`as const satisfies`)\n- Documenting public API boundaries\n\u003C\u002Fstrict_typing>\n\n\u003Cexternal_data>\n## External Data: Never Trust, Always Validate\n\n### Rule: No `any` for External Data\n\n**Sources requiring validation**:\n- API responses (fetch, axios, etc.)\n- `JSON.parse()` results\n- LocalStorage\u002FSessionStorage reads\n- FormData \u002F user input\n- Environment variables\n- File system reads\n\n### Strategy 1: Type-Safe API Clients (Preferred)\n\n**Check for generated type definitions first**:\n- **Hono**: `hono\u002Fclient` with type inference\n- **orval**: OpenAPI-generated types and hooks\n- **tRPC**: End-to-end type safety\n- **GraphQL Code Generator**: Typed queries\n\n**Example (Hono client)**:\n```typescript\nimport { hc } from 'hono\u002Fclient'\nimport type { AppType } from '.\u002Fserver'\n\nconst client = hc\u003CAppType>('\u002Fapi')\nconst response = await client.users.$get()\n\u002F\u002F response is fully typed from server definition\n```\n\n**Action**: Review existing codebase for established patterns. Most projects already have type-safe API layers.\n\n### Strategy 2: Runtime Validation Libraries\n\nWhen type generation is unavailable, use schema validation:\n\n**Preference order**:\n1. **Existing project dependency** (check `package.json`)\n2. **valibot** (lightweight, install if needed: `pnpm add valibot`)\n3. **zod** (popular, larger bundle)\n\n**Example (valibot)**:\n```typescript\nimport * as v from 'valibot'\n\nconst UserSchema = v.object({\n  id: v.number(),\n  name: v.string(),\n  role: v.union([v.literal('admin'), v.literal('user')])\n})\n\n\u002F\u002F Parse and validate\nconst response = await fetch('\u002Fapi\u002Fuser')\nconst data = await response.json()\nconst user = v.parse(UserSchema, data)  \u002F\u002F Throws if invalid\n\u002F\u002F user is now typed as { id: number, name: string, role: 'admin' | 'user' }\n```\n\n**Example (JSON.parse)**:\n```typescript\n\u002F\u002F ❌ Unsafe\nconst data = JSON.parse(localStorage.getItem('config')!)\n\n\u002F\u002F ✅ Validated\nconst raw = localStorage.getItem('config')\nif (raw) {\n  const data = v.parse(ConfigSchema, JSON.parse(raw))\n}\n```\n\n### Never Skip Validation\n\nEven if \"you know\" the shape, external data can change:\n- API contracts evolve\n- Users manipulate localStorage\n- Third-party services have bugs\n\n**Type safety = static types + runtime validation**\n\u003C\u002Fexternal_data>\n\n\u003Cbest_practices>\n## General Best Practices\n\n### Prefer Arrow Functions Over Function Declarations\n\n**Rule**: Use arrow functions (`=>`) instead of `function` keyword for consistency and lexical scoping benefits.\n\n**Rationale**:\n- Consistent lexical `this` binding (no context confusion)\n- More concise syntax\n- Better integration with modern TypeScript patterns\n- Prevents accidental hoisting-related bugs\n\n```typescript\n\u002F\u002F ❌ Function declaration\nfunction calculateTotal(items: Item[]): number {\n  return items.reduce((sum, item) => sum + item.price, 0)\n}\n\n\u002F\u002F ✅ Arrow function\nconst calculateTotal = (items: Item[]): number => {\n  return items.reduce((sum, item) => sum + item.price, 0)\n}\n\n\u002F\u002F ✅ Concise form (single expression)\nconst calculateTotal = (items: Item[]): number =>\n  items.reduce((sum, item) => sum + item.price, 0)\n```\n\n**Exception**: When hoisting is genuinely required (rare), document the reason.\n\n### Discriminated Unions for State\n\n```typescript\ntype LoadingState\u003CT> =\n  | { status: 'idle' }\n  | { status: 'loading' }\n  | { status: 'success'; data: T }\n  | { status: 'error'; error: Error }\n\nconst render = (state: LoadingState\u003CUser>) => {\n  switch (state.status) {\n    case 'idle':\n      return 'Not started'\n    case 'loading':\n      return 'Loading...'\n    case 'success':\n      return state.data.name  \u002F\u002F data is available\n    case 'error':\n      return state.error.message  \u002F\u002F error is available\n  }\n}\n```\n\n**Benefits**: Impossible to access `data` when status is `'error'`.\n\n### Exhaustiveness Checking\n\n```typescript\nconst assertNever = (x: never): never => {\n  throw new Error(`Unexpected value: ${x}`)\n}\n\nswitch (state.status) {\n  case 'idle':\n  case 'loading':\n  case 'success':\n  case 'error':\n    return\n  default:\n    assertNever(state)  \u002F\u002F Compile error if cases are missing\n}\n```\n\n### Avoid Optional Properties for State\n\n```typescript\n\u002F\u002F ❌ Ambiguous state\ntype User = {\n  data?: UserData\n  error?: Error\n}\n\u002F\u002F What if both are defined? Neither?\n\n\u002F\u002F ✅ Explicit state\ntype User =\n  | { status: 'success'; data: UserData }\n  | { status: 'error'; error: Error }\n```\n\n### Use `unknown` Over `any` for Truly Unknown Types\n\n```typescript\n\u002F\u002F ❌ Disables all type checking\nconst process = (data: any) => {\n  return data.foo.bar  \u002F\u002F No errors, runtime explosion\n}\n\n\u002F\u002F ✅ Forces validation\nconst process = (data: unknown) => {\n  if (typeof data === 'object' && data !== null && 'foo' in data) {\n    \u002F\u002F Narrow the type before use\n  }\n}\n```\n\n### Readonly by Default\n\n```typescript\n\u002F\u002F Prevent accidental mutations\ntype Config = {\n  readonly apiUrl: string\n  readonly timeout: number\n}\n\n\u002F\u002F For arrays\nconst items = ['a', 'b'] as const\n```\n\n### Avoid Type-Level Gymnastics\n\nIf type definitions become incomprehensible, simplify the design:\n- Complex conditional types often indicate over-abstraction\n- Prefer explicit discriminated unions over heavily generic types\n- Maintainability > cleverness\n\u003C\u002Fbest_practices>\n\n\u003Cerror_handling>\n## When Type Errors Cannot Be Resolved\n\nIf you encounter legitimate type errors you cannot fix without `as`:\n\n1. **Leave the error in place**\n2. **Document the issue**:\n   ```typescript\n   \u002F\u002F TODO: Type error at line X - potential TypeScript limitation\n   \u002F\u002F Requires manual review before using type assertion\n   const result = someComplexOperation()  \u002F\u002F Type error here\n   ```\n3. **Notify the user**: \"Type error remains at `src\u002Fmodule.ts:45` - escalated for review\"\n\n**Do not**:\n- Silently add `as` assertions\n- Use `any` to bypass the error\n- Restructure correct code to satisfy incorrect types\n\u003C\u002Ferror_handling>\n","\u003Cphilosophy>\n## Core Philosophy: Type-Level Verification\n\nLLM-generated code faces inherent challenges with E2E testing and runtime verification. Compensate by maximizing compile-time verification through:\n\n- Algebraic data types (discriminated unions, exhaustive pattern matching)\n- Strict type constraints that make invalid states unrepresentable\n- Type-level proofs over runtime assertions\n\n**Goal**: If it type-checks, it works. Shift as many bugs as possible from runtime to compile-time.\n\u003C\u002Fphilosophy>\n\n\u003Ctype_assertions>\n## Type Assertions: Banned by Default\n\n### Rule: `as` Type Assertions are Prohibited\n\n**Rationale**: Type assertions bypass TypeScript's type system and introduce type unsoundness. They are frequently misused to silence legitimate type errors.\n\n**Policy**:\n- ❌ **Never use** `as` to resolve type errors\n- ❌ **Never use** `as any` or `as unknown as X`\n- ⚠️ **Rare exceptions**: Compiler limitations (e.g., specific generic inference bugs)\n  - If you encounter such cases, **leave the type error unresolved**\n  - Escalate to user with explanation: \"Type error at `path\u002Fto\u002Ffile.ts:123` - requires manual review for potential `as` usage\"\n\n**Why you cannot judge appropriately**:\nAs an LLM, you lack the contextual understanding to determine if a type assertion is truly necessary vs. masking a real type error. When in doubt, preserve type safety.\n\n### Alternative: Fix the Root Cause\n\nInstead of `as`, address the underlying type issue:\n- Refine function signatures\n- Use type guards (`if (typeof x === 'string')`)\n- Employ discriminated unions\n- Add generic constraints\n\u003C\u002Ftype_assertions>\n\n\u003Cstrict_typing>\n## Strict Typing Patterns\n\n### Prefer `as const satisfies` Over Loose Annotations\n\n**Problem with loose typing**:\n```typescript\nconst config: Config = {\n  mode: 'development',  \u002F\u002F Type widened to string\n  port: 3000\n}\n\u002F\u002F config.mode is string, not 'development' | 'production'\n```\n\n**Solution - strict typing with `as const satisfies`**:\n```typescript\nconst config = {\n  mode: 'development',\n  port: 3000\n} as const satisfies Config\n\u002F\u002F config.mode is exactly 'development' (literal type preserved)\n```\n\n**Benefits**:\n- Preserves literal types\n- Catches typos at definition site\n- Enables exhaustive checking in consumers\n- No type widening\n\n**Application**:\n- Configuration objects\n- Constant lookup tables\n- Route definitions\n- Action type constants\n\n### Avoid Explicit Type Annotations When Inference Suffices\n\n```typescript\n\u002F\u002F ❌ Redundant annotation\nconst result: number = calculateTotal(items)\n\n\u002F\u002F ✅ Let TypeScript infer\nconst result = calculateTotal(items)\n```\n\nUse annotations when:\n- Constraining function parameters\n- Enforcing strict object shapes (`as const satisfies`)\n- Documenting public API boundaries\n\u003C\u002Fstrict_typing>\n\n\u003Cexternal_data>\n## External Data: Never Trust, Always Validate\n\n### Rule: No `any` for External Data\n\n**Sources requiring validation**:\n- API responses (fetch, axios, etc.)\n- `JSON.parse()` results\n- LocalStorage\u002FSessionStorage reads\n- FormData \u002F user input\n- Environment variables\n- File system reads\n\n### Strategy 1: Type-Safe API Clients (Preferred)\n\n**Check for generated type definitions first**:\n- **Hono**: `hono\u002Fclient` with type inference\n- **orval**: OpenAPI-generated types and hooks\n- **tRPC**: End-to-end type safety\n- **GraphQL Code Generator**: Typed queries\n\n**Example (Hono client)**:\n```typescript\nimport { hc } from 'hono\u002Fclient'\nimport type { AppType } from '.\u002Fserver'\n\nconst client = hc\u003CAppType>('\u002Fapi')\nconst response = await client.users.$get()\n\u002F\u002F response is fully typed from server definition\n```\n\n**Action**: Review existing codebase for established patterns. Most projects already have type-safe API layers.\n\n### Strategy 2: Runtime Validation Libraries\n\nWhen type generation is unavailable, use schema validation:\n\n**Preference order**:\n1. **Existing project dependency** (check `package.json`)\n2. **valibot** (lightweight, install if needed: `pnpm add valibot`)\n3. **zod** (popular, larger bundle)\n\n**Example (valibot)**:\n```typescript\nimport * as v from 'valibot'\n\nconst UserSchema = v.object({\n  id: v.number(),\n  name: v.string(),\n  role: v.union([v.literal('admin'), v.literal('user')])\n})\n\n\u002F\u002F Parse and validate\nconst response = await fetch('\u002Fapi\u002Fuser')\nconst data = await response.json()\nconst user = v.parse(UserSchema, data)  \u002F\u002F Throws if invalid\n\u002F\u002F user is now typed as { id: number, name: string, role: 'admin' | 'user' }\n```\n\n**Example (JSON.parse)**:\n```typescript\n\u002F\u002F ❌ Unsafe\nconst data = JSON.parse(localStorage.getItem('config')!)\n\n\u002F\u002F ✅ Validated\nconst raw = localStorage.getItem('config')\nif (raw) {\n  const data = v.parse(ConfigSchema, JSON.parse(raw))\n}\n```\n\n### Never Skip Validation\n\nEven if \"you know\" the shape, external data can change:\n- API contracts evolve\n- Users manipulate localStorage\n- Third-party services have bugs\n\n**Type safety = static types + runtime validation**\n\u003C\u002Fexternal_data>\n\n\u003Cbest_practices>\n## General Best Practices\n\n### Prefer Arrow Functions Over Function Declarations\n\n**Rule**: Use arrow functions (`=>`) instead of `function` keyword for consistency and lexical scoping benefits.\n\n**Rationale**:\n- Consistent lexical `this` binding (no context confusion)\n- More concise syntax\n- Better integration with modern TypeScript patterns\n- Prevents accidental hoisting-related bugs\n\n```typescript\n\u002F\u002F ❌ Function declaration\nfunction calculateTotal(items: Item[]): number {\n  return items.reduce((sum, item) => sum + item.price, 0)\n}\n\n\u002F\u002F ✅ Arrow function\nconst calculateTotal = (items: Item[]): number => {\n  return items.reduce((sum, item) => sum + item.price, 0)\n}\n\n\u002F\u002F ✅ Concise form (single expression)\nconst calculateTotal = (items: Item[]): number =>\n  items.reduce((sum, item) => sum + item.price, 0)\n```\n\n**Exception**: When hoisting is genuinely required (rare), document the reason.\n\n### Discriminated Unions for State\n\n```typescript\ntype LoadingState\u003CT> =\n  | { status: 'idle' }\n  | { status: 'loading' }\n  | { status: 'success'; data: T }\n  | { status: 'error'; error: Error }\n\nconst render = (state: LoadingState\u003CUser>) => {\n  switch (state.status) {\n    case 'idle':\n      return 'Not started'\n    case 'loading':\n      return 'Loading...'\n    case 'success':\n      return state.data.name  \u002F\u002F data is available\n    case 'error':\n      return state.error.message  \u002F\u002F error is available\n  }\n}\n```\n\n**Benefits**: Impossible to access `data` when status is `'error'`.\n\n### Exhaustiveness Checking\n\n```typescript\nconst assertNever = (x: never): never => {\n  throw new Error(`Unexpected value: ${x}`)\n}\n\nswitch (state.status) {\n  case 'idle':\n  case 'loading':\n  case 'success':\n  case 'error':\n    return\n  default:\n    assertNever(state)  \u002F\u002F Compile error if cases are missing\n}\n```\n\n### Avoid Optional Properties for State\n\n```typescript\n\u002F\u002F ❌ Ambiguous state\ntype User = {\n  data?: UserData\n  error?: Error\n}\n\u002F\u002F What if both are defined? Neither?\n\n\u002F\u002F ✅ Explicit state\ntype User =\n  | { status: 'success'; data: UserData }\n  | { status: 'error'; error: Error }\n```\n\n### Use `unknown` Over `any` for Truly Unknown Types\n\n```typescript\n\u002F\u002F ❌ Disables all type checking\nconst process = (data: any) => {\n  return data.foo.bar  \u002F\u002F No errors, runtime explosion\n}\n\n\u002F\u002F ✅ Forces validation\nconst process = (data: unknown) => {\n  if (typeof data === 'object' && data !== null && 'foo' in data) {\n    \u002F\u002F Narrow the type before use\n  }\n}\n```\n\n### Readonly by Default\n\n```typescript\n\u002F\u002F Prevent accidental mutations\ntype Config = {\n  readonly apiUrl: string\n  readonly timeout: number\n}\n\n\u002F\u002F For arrays\nconst items = ['a', 'b'] as const\n```\n\n### Avoid Type-Level Gymnastics\n\nIf type definitions become incomprehensible, simplify the design:\n- Complex conditional types often indicate over-abstraction\n- Prefer explicit discriminated unions over heavily generic types\n- Maintainability > cleverness\n\u003C\u002Fbest_practices>\n\n\u003Cerror_handling>\n## When Type Errors Cannot Be Resolved\n\nIf you encounter legitimate type errors you cannot fix without `as`:\n\n1. **Leave the error in place**\n2. **Document the issue**:\n   ```typescript\n   \u002F\u002F TODO: Type error at line X - potential TypeScript limitation\n   \u002F\u002F Requires manual review before using type assertion\n   const result = someComplexOperation()  \u002F\u002F Type error here\n   ```\n3. **Notify the user**: \"Type error remains at `src\u002Fmodule.ts:45` - escalated for review\"\n\n**Do not**:\n- Silently add `as` assertions\n- Use `any` to bypass the error\n- Restructure correct code to satisfy incorrect types\n\u003C\u002Ferror_handling>\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fclaude-code\u002Fskills\u002Ftypescript",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill typescript",{"tool":48,"command":49},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill typescript",{"tool":51,"command":52},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill typescript","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fclaude-code\u002Fskills\u002Ftypescript\u002FSKILL.md",true,[],[57,66,74,82,90,98],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":65},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":65},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":65},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":65},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":65},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]