[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ACRBPAV73GJJAMG4M4PMZ":3,"skill-same:01M74ACRBPAV73GJJAMG4M4PMZ":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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M74ACRBPAV73GJJAMG4M4PMZ","batch-import-relative-paths",null,"When you batch-add an `import` line to N source files via sed\u002Fawk, the relative path must be computed PER-FILE (depth varies). Vite\u002Fesbuild often silently normalize bad `..\u002F` and the bug hides across multiple deploys until a larger rebuild forces strict module resolution.","CarlosCaPe\u002Foctorato","CarlosCaPe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39838249?v=4","01M72WXX4ZRR8MBH1EP1QND2FQ","dataqbs","01M72WXX5NA7YCKRSJ54GW1GQ8",18,"MIT","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fbatch-import-relative-paths\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: batch-import-relative-paths\ndescription: \"When you batch-add an `import` line to N source files via sed\u002Fawk, the relative path must be computed PER-FILE (depth varies). Vite\u002Fesbuild often silently normalize bad `..\u002F` and the bug hides across multiple deploys until a larger rebuild forces strict module resolution.\"\nmetadata:\n  short-description: \"Sed-batched imports with hardcoded `..\u002F` chains break silently in Vite\u002Fesbuild — compute the path per-file with Python's os.path.relpath, then verify with a full build.\"\n---\n\n# Batch Import Relative Paths\n\n## What\n\nYou have a new library module — say `src\u002Flib\u002Ftiming-safe-equal.ts` — that\nyou want to import into 10 sibling endpoints under\n`src\u002Fpages\u002Fapi\u002F...\u002F*.ts`. A `sed` one-liner that inserts\n`import { X } from '..\u002F..\u002F..\u002F..\u002Flib\u002FX';` after the last existing import\nline LOOKS fine. The typecheck passes. The deploys pass. Then one day a\nbigger rebuild fails with `Could not resolve \"..\u002F..\u002F..\u002F..\u002Flib\u002FX\"` and\nsuddenly you discover the path was wrong all along — and you can't\ntrivially tell which of the 10 files had which depth.\n\n## Why this happens\n\nTwo compounding failure modes:\n\n### Mode A — Hardcoded `..\u002F` count assumes uniform depth\n\n`sed` doesn't know how deep each file lives in the tree. If your batch\nspans `src\u002Fpages\u002Fapi\u002FX.ts` (3 hops to `src\u002F`) AND\n`src\u002Fpages\u002Fapi\u002Finternal\u002FX.ts` (4 hops to `src\u002F`), a single sed pass\napplies the SAME `..\u002F` count to all of them — at least one set will be\nwrong.\n\n### Mode B — Vite \u002F esbuild silently normalize extra `..\u002F`\n\nWhen a relative path contains MORE `..\u002F` than the actual nesting, modern\nbundlers do not error immediately. They collapse the excess at the\nfilesystem root and then fall through to:\n\n1. Resolver plugins (Astro, SvelteKit, etc. each add their own).\n2. Path aliases from `tsconfig.json` (`@lib\u002F*`, `~\u002F*`, etc.).\n3. Cached resolved-module entries from prior builds.\n4. Implicit `package.json#exports` fallthrough.\n\nAny of these can \"find\" the module by sheer coincidence — especially in\nincremental builds where the previous valid resolution is cached. Your\nbuild passes. Your deploy works. The bug is latent.\n\nA larger rebuild (different entry points, a clean cache, a refactor that\ntouches the resolver's input graph) finally forces strict re-resolution\nand the latent bug surfaces.\n\n### Mode C — Inserting BEFORE the close of a multi-line import block\n\nIf sed inserts the new line \"after the last `^import ` line\" without\nchecking whether that line is the OPEN of a multi-line block —\n\n```ts\nimport {                              \u002F\u002F \u003C-- last `^import` line\n  thingA,\n  thingB,\nimport { newThing } from '..\u002F..\u002F...'; \u002F\u002F \u003C-- sed inserts HERE\n} from '..\u002F..\u002F..\u002Flib\u002Fold-block';\n```\n\n— you get a parser-level syntax error: `Expected \"as\" but found \"{\"` or\n`Unexpected token`. This is a separate-but-related failure mode of the\nsame naïve insertion strategy.\n\n## When to suspect this\n\n- Your CI just exploded with `Could not resolve \"..\u002F..\u002F...\"` after a\n  PR that doesn't touch any imports.\n- The `git blame` for the broken import points to a prior batch-insert\n  PR that \"deployed fine\" weeks\u002Fdays ago.\n- `Expected \"as\" but found \"{\"` at a `column 7` in a TypeScript file\n  whose line 1 is `import {`.\n- Different files in the same batch use **the same** `..\u002F..\u002F..\u002F...`\n  prefix despite living at different depths.\n\n## Workflow — how to do batch imports correctly\n\n### 1. Compute the relative path PER FILE with Python\n\n```python\nimport os, sys\n\nTARGET = 'src\u002Flib\u002Ftiming-safe-equal.ts'           # the new module\nFILES = [\n    'src\u002Fpages\u002Fapi\u002FX.ts',\n    'src\u002Fpages\u002Fapi\u002FY.ts',\n    'src\u002Fpages\u002Fapi\u002Finternal\u002FZ.ts',\n    'src\u002Fpages\u002Fapi\u002Finternal\u002Ffoo\u002FW.ts',\n]\n\nfor f in FILES:\n    rel = os.path.relpath(TARGET, os.path.dirname(f))\n    # Strip .ts\u002F.tsx for the import string\n    rel = rel.removesuffix('.ts').removesuffix('.tsx')\n    print(f\"{f}\\n  import {{ X }} from '{rel}';\")\n```\n\nThis is the ONLY reliable way. `os.path.relpath` handles every depth\ncorrectly; `sed` cannot.\n\n### 2. Detect multi-line import blocks before inserting\n\nInsert AFTER the last `} from '...'` (closing line of a multi-line\nblock) OR after the last single-line `^import ... from '...';`. Use\nPython with a tiny regex, not sed:\n\n```python\nimport re\nfrom pathlib import Path\n\ndef insert_import(file_path: str, new_import: str) -> None:\n    src = Path(file_path).read_text()\n    lines = src.splitlines()\n    last_idx = -1\n    for i, line in enumerate(lines):\n        s = line.strip()\n        # Multi-line block CLOSE: } from '...';\n        if re.match(r'\\}\\s*from\\s*[\\'\\\"].*[\\'\\\"]\\s*;?$', s):\n            last_idx = i\n        # Single-line import\n        elif re.match(r'^import\\s+.*\\s+from\\s+[\\'\\\"].*[\\'\\\"]\\s*;?$', s) or \\\n             re.match(r'^import\\s+[\\'\\\"].*[\\'\\\"]\\s*;?$', s):\n            last_idx = i\n        # Type-only import\n        elif re.match(r'^import\\s+type\\s+.*from\\s+[\\'\\\"].*[\\'\\\"]\\s*;?$', s):\n            last_idx = i\n    if last_idx \u003C 0:\n        # File has no imports; insert at top after any leading comment block\n        last_idx = 0\n    lines.insert(last_idx + 1, new_import)\n    Path(file_path).write_text('\\n'.join(lines) + '\\n')\n```\n\n### 3. ALWAYS run a full project build before committing\n\n```bash\n# Astro\nnpx astro build\n\n# SvelteKit\nnpm run build\n\n# Next.js\nnext build\n\n# Vite generic\nnpm run build\n```\n\nA full build forces strict module resolution and is the only signal\nthat catches Mode B. `tsc --noEmit` \u002F `astro check` \u002F `tsc --build` are\nNOT enough — they validate type signatures but lean on the dev server's\nlenient resolver.\n\n## Anti-patterns\n\n- **sed `s|FROM|TO|g` on multiple files with a single `..\u002F` chain.**\n  The depth is almost never uniform; the breakage is silent.\n- **Trusting `astro check` \u002F `tsc --noEmit` as your only validation.**\n  Both pass with broken relative paths because their resolver is more\n  permissive than the production build resolver.\n- **Inserting via `awk '\u002F^import \u002F{...}'` without recognizing multi-line\n  `import { ... }` blocks.** Splits the block, breaks the parser.\n- **Catching one file in a refactor and \"fixing it\" in isolation.**\n  Sister files in the batch will still be wrong; you'll get a second\n  failure 3 PRs later when a different rebuild path hits a different\n  file.\n\n## Diagnostic when the bug fires\n\n```bash\n# 1. Find every suspiciously-long ..\u002F chain\ngrep -rEn \"\\.\\.\u002F\\.\\.\u002F\\.\\.\u002F\\.\\.\u002F\\.\\.\" src\u002F 2>\u002Fdev\u002Fnull\n\n# 2. Compute the correct path for each hit\npython3 -c \"\nimport os\ntarget = 'src\u002Flib\u002F\u003Cmodule>.ts'\nfor f in \u003Cfiles-from-grep>:\n    print(f, '→', os.path.relpath(target, os.path.dirname(f)))\n\"\n\n# 3. Patch + run full build\nnpx astro build 2>&1 | grep -E '(ERROR|Could not resolve|Build failed)'\n```\n\n## Lessons Learned\n\n\u003C!-- Append new cases as encountered. Include: date, framework, how many\nfiles were silently broken, how many deploys passed before exposure. -->\n","# Batch Import Relative Paths\n\n## What\n\nYou have a new library module — say `src\u002Flib\u002Ftiming-safe-equal.ts` — that\nyou want to import into 10 sibling endpoints under\n`src\u002Fpages\u002Fapi\u002F...\u002F*.ts`. A `sed` one-liner that inserts\n`import { X } from '..\u002F..\u002F..\u002F..\u002Flib\u002FX';` after the last existing import\nline LOOKS fine. The typecheck passes. The deploys pass. Then one day a\nbigger rebuild fails with `Could not resolve \"..\u002F..\u002F..\u002F..\u002Flib\u002FX\"` and\nsuddenly you discover the path was wrong all along — and you can't\ntrivially tell which of the 10 files had which depth.\n\n## Why this happens\n\nTwo compounding failure modes:\n\n### Mode A — Hardcoded `..\u002F` count assumes uniform depth\n\n`sed` doesn't know how deep each file lives in the tree. If your batch\nspans `src\u002Fpages\u002Fapi\u002FX.ts` (3 hops to `src\u002F`) AND\n`src\u002Fpages\u002Fapi\u002Finternal\u002FX.ts` (4 hops to `src\u002F`), a single sed pass\napplies the SAME `..\u002F` count to all of them — at least one set will be\nwrong.\n\n### Mode B — Vite \u002F esbuild silently normalize extra `..\u002F`\n\nWhen a relative path contains MORE `..\u002F` than the actual nesting, modern\nbundlers do not error immediately. They collapse the excess at the\nfilesystem root and then fall through to:\n\n1. Resolver plugins (Astro, SvelteKit, etc. each add their own).\n2. Path aliases from `tsconfig.json` (`@lib\u002F*`, `~\u002F*`, etc.).\n3. Cached resolved-module entries from prior builds.\n4. Implicit `package.json#exports` fallthrough.\n\nAny of these can \"find\" the module by sheer coincidence — especially in\nincremental builds where the previous valid resolution is cached. Your\nbuild passes. Your deploy works. The bug is latent.\n\nA larger rebuild (different entry points, a clean cache, a refactor that\ntouches the resolver's input graph) finally forces strict re-resolution\nand the latent bug surfaces.\n\n### Mode C — Inserting BEFORE the close of a multi-line import block\n\nIf sed inserts the new line \"after the last `^import ` line\" without\nchecking whether that line is the OPEN of a multi-line block —\n\n```ts\nimport {                              \u002F\u002F \u003C-- last `^import` line\n  thingA,\n  thingB,\nimport { newThing } from '..\u002F..\u002F...'; \u002F\u002F \u003C-- sed inserts HERE\n} from '..\u002F..\u002F..\u002Flib\u002Fold-block';\n```\n\n— you get a parser-level syntax error: `Expected \"as\" but found \"{\"` or\n`Unexpected token`. This is a separate-but-related failure mode of the\nsame naïve insertion strategy.\n\n## When to suspect this\n\n- Your CI just exploded with `Could not resolve \"..\u002F..\u002F...\"` after a\n  PR that doesn't touch any imports.\n- The `git blame` for the broken import points to a prior batch-insert\n  PR that \"deployed fine\" weeks\u002Fdays ago.\n- `Expected \"as\" but found \"{\"` at a `column 7` in a TypeScript file\n  whose line 1 is `import {`.\n- Different files in the same batch use **the same** `..\u002F..\u002F..\u002F...`\n  prefix despite living at different depths.\n\n## Workflow — how to do batch imports correctly\n\n### 1. Compute the relative path PER FILE with Python\n\n```python\nimport os, sys\n\nTARGET = 'src\u002Flib\u002Ftiming-safe-equal.ts'           # the new module\nFILES = [\n    'src\u002Fpages\u002Fapi\u002FX.ts',\n    'src\u002Fpages\u002Fapi\u002FY.ts',\n    'src\u002Fpages\u002Fapi\u002Finternal\u002FZ.ts',\n    'src\u002Fpages\u002Fapi\u002Finternal\u002Ffoo\u002FW.ts',\n]\n\nfor f in FILES:\n    rel = os.path.relpath(TARGET, os.path.dirname(f))\n    # Strip .ts\u002F.tsx for the import string\n    rel = rel.removesuffix('.ts').removesuffix('.tsx')\n    print(f\"{f}\\n  import {{ X }} from '{rel}';\")\n```\n\nThis is the ONLY reliable way. `os.path.relpath` handles every depth\ncorrectly; `sed` cannot.\n\n### 2. Detect multi-line import blocks before inserting\n\nInsert AFTER the last `} from '...'` (closing line of a multi-line\nblock) OR after the last single-line `^import ... from '...';`. Use\nPython with a tiny regex, not sed:\n\n```python\nimport re\nfrom pathlib import Path\n\ndef insert_import(file_path: str, new_import: str) -> None:\n    src = Path(file_path).read_text()\n    lines = src.splitlines()\n    last_idx = -1\n    for i, line in enumerate(lines):\n        s = line.strip()\n        # Multi-line block CLOSE: } from '...';\n        if re.match(r'\\}\\s*from\\s*[\\'\\\"].*[\\'\\\"]\\s*;?$', s):\n            last_idx = i\n        # Single-line import\n        elif re.match(r'^import\\s+.*\\s+from\\s+[\\'\\\"].*[\\'\\\"]\\s*;?$', s) or \\\n             re.match(r'^import\\s+[\\'\\\"].*[\\'\\\"]\\s*;?$', s):\n            last_idx = i\n        # Type-only import\n        elif re.match(r'^import\\s+type\\s+.*from\\s+[\\'\\\"].*[\\'\\\"]\\s*;?$', s):\n            last_idx = i\n    if last_idx \u003C 0:\n        # File has no imports; insert at top after any leading comment block\n        last_idx = 0\n    lines.insert(last_idx + 1, new_import)\n    Path(file_path).write_text('\\n'.join(lines) + '\\n')\n```\n\n### 3. ALWAYS run a full project build before committing\n\n```bash\n# Astro\nnpx astro build\n\n# SvelteKit\nnpm run build\n\n# Next.js\nnext build\n\n# Vite generic\nnpm run build\n```\n\nA full build forces strict module resolution and is the only signal\nthat catches Mode B. `tsc --noEmit` \u002F `astro check` \u002F `tsc --build` are\nNOT enough — they validate type signatures but lean on the dev server's\nlenient resolver.\n\n## Anti-patterns\n\n- **sed `s|FROM|TO|g` on multiple files with a single `..\u002F` chain.**\n  The depth is almost never uniform; the breakage is silent.\n- **Trusting `astro check` \u002F `tsc --noEmit` as your only validation.**\n  Both pass with broken relative paths because their resolver is more\n  permissive than the production build resolver.\n- **Inserting via `awk '\u002F^import \u002F{...}'` without recognizing multi-line\n  `import { ... }` blocks.** Splits the block, breaks the parser.\n- **Catching one file in a refactor and \"fixing it\" in isolation.**\n  Sister files in the batch will still be wrong; you'll get a second\n  failure 3 PRs later when a different rebuild path hits a different\n  file.\n\n## Diagnostic when the bug fires\n\n```bash\n# 1. Find every suspiciously-long ..\u002F chain\ngrep -rEn \"\\.\\.\u002F\\.\\.\u002F\\.\\.\u002F\\.\\.\u002F\\.\\.\" src\u002F 2>\u002Fdev\u002Fnull\n\n# 2. Compute the correct path for each hit\npython3 -c \"\nimport os\ntarget = 'src\u002Flib\u002F\u003Cmodule>.ts'\nfor f in \u003Cfiles-from-grep>:\n    print(f, '→', os.path.relpath(target, os.path.dirname(f)))\n\"\n\n# 3. Patch + run full build\nnpx astro build 2>&1 | grep -E '(ERROR|Could not resolve|Build failed)'\n```\n\n## Lessons Learned\n\n\u003C!-- Append new cases as encountered. Include: date, framework, how many\nfiles were silently broken, how many deploys passed before exposure. -->\n",{"name":5,"metadata":24,"description":7},{"short-description":25},"Sed-batched imports with hardcoded `..\u002F` chains break silently in Vite\u002Fesbuild — compute the path per-file with Python's os.path.relpath, then verify with a full build.","master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Fbatch-import-relative-paths",6,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato","https:\u002F\u002Fwww.dataqbs.com\u002Foctorato","https:\u002F\u002Fgithub.com\u002FCarlosCaPe","www.dataqbs.com"," AI-powered data engineering\r\n& consulting\r\n\r\nWe build data platforms that turn complexity into clarity — from cloud architecture and ETL pipelines to AI-driven","2026-11-14 00:21:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add CarlosCaPe\u002Foctorato --skill batch-import-relative-paths",{"tool":42,"command":43},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill batch-import-relative-paths",{"tool":45,"command":46},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill batch-import-relative-paths","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fbatch-import-relative-paths\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"skill.json","REFERENCE","参考文档",398,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fbatch-import-relative-paths\u002Fskill.json",[57,66,74,81,89,97],{"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":61,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74EVAA4A4B4AKR5TT732GP4","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"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":61,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74EV4WMRDKP2NQS4YWR8PXH","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\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":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74EV05MHTXKEXD4B2QJEYTF","workspace-skill-discovery","Discover and include ALL skills across the workspace — not just global ones. Use at the start of every session or when the user asks about available skills. Ensures project-level skills (under .claude\u002Fskills\u002F or skills\u002F in any repo) are never missed.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-skill-discovery\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ETV78525B4VP2F28Z6NRD","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M74ETR75NF67WGVEN7288ACV","winui-app","Create, build and design WinUI 3 desktop apps with C# and the Windows App SDK following Microsoft's official guidance and CommunityToolkit. Covers XAML, navigation, theming, accessibility and deployment.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M74ETJFRNPPNSQZ36C6HD6CW","windows-brain-script-portability","Scripts in ~\u002F.claude\u002Fscripts\u002F that run on a Windows brain: use the python3.cmd shim and not bare python3, and reconfigure stdout to UTF-8 if you print symbols. Use it when writing a brain script or triaging a Windows-only crash.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwindows-brain-script-portability\u002FSKILL.md",[],[]]