[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XCBF6EFYKD0J8KTPFDRW0G":3,"skill-same:01M6XCBF6EFYKD0J8KTPFDRW0G":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":57},"01M6XCBF6EFYKD0J8KTPFDRW0G","typescript-compile-check-resilient",null,"TypeScript compile-checking in projects where npx and node_modules\u002F.bin symlinks fail, with a filtering technique to isolate errors from only newly-created or task-specific files — ignoring pre-existing legacy errors.","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Ftypescript-compile-check-resilient\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"typescript","compile","check","typescript compile check resilient","projects","node","filtering","only","modules","Legacy","files","npx","task","with","errors","Existing","2026-11-10 10:12:30",false,"---\nname: typescript-compile-check-resilient\ndescription: TypeScript compile-checking in projects where npx and node_modules\u002F.bin symlinks fail, with a filtering technique to isolate errors from only newly-created or task-specific files — ignoring pre-existing legacy errors.\n---\n\n# TypeScript Compile-Check (Resilient) with File-Scoped Error Filtering\n\nUse this workflow when you need to validate TypeScript changes in a project but the standard `npx tsc` or `node_modules\u002F.bin\u002Ftsc` invocations fail due to broken symlinks, missing PATH entries, or environment issues.\n\n---\n\n## When to Use This Skill\n\n- `npx tsc` fails with \"command not found\" or permission errors\n- `node_modules\u002F.bin\u002Ftsc` symlink is broken or unresolvable\n- You need to validate only *newly-created* or *task-specific* files without being blocked by pre-existing compile errors in the broader codebase\n\n---\n\n## Step 1 — Invoke tsc Directly via node_modules\n\nBypass `npx` and symlinks entirely by calling the TypeScript binary directly:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1; echo EXIT:$?\n```\n\n**Why this works:** The `tsc` CLI entry point is a plain Node.js script at `node_modules\u002Ftypescript\u002Fbin\u002Ftsc`. It does not depend on symlinks or PATH resolution. The `--noEmit` flag checks types without writing output files. Capturing `EXIT:$?` lets you programmatically detect success (`EXIT:0`) vs failure (`EXIT:1` or higher).\n\nIf the project uses a custom `tsconfig`, specify it explicitly:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit --project tsconfig.json 2>&1; echo EXIT:$?\n```\n\n---\n\n## Step 2 — Filter Output to Task-Specific Files Only\n\nWhen a legacy codebase has pre-existing errors, the full `tsc` output will be noisy and may cause false negatives. Pipe through `grep` to isolate errors from only the files you created or modified:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"(file-pattern)\" ; echo EXIT:${PIPESTATUS[0]}\n```\n\n### Examples\n\n**Single new file:**\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"settings-store\\.ts\"\n```\n\n**Multiple new files (pipe-delimited pattern):**\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"(settings-keys|settings-store|preferences|SettingsModal)\"\n```\n\n**All files in a specific directory:**\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"src\u002Ffeatures\u002Fmy-feature\u002F\"\n```\n\n**Check: no output = no errors in your files (success).**\n\n---\n\n## Step 3 — Capture Exit Code Correctly Through a Pipe\n\nWhen grepping, the shell exit code reflects `grep`, not `tsc`. Use `${PIPESTATUS[0]}` (bash) to recover the original `tsc` exit code:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"(my-file-pattern)\"; echo \"TSC_EXIT:${PIPESTATUS[0]}\"\n```\n\nOr store errors explicitly:\n\n```bash\nTSC_OUTPUT=$(node_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1)\nTSC_EXIT=$?\necho \"$TSC_OUTPUT\" | grep -E \"(settings-keys|settings-store|preferences|SettingsModal)\"\necho \"TSC_EXIT:$TSC_EXIT\"\n```\n\nThe second approach (storing output in a variable) is the most reliable since `$?` is captured before the pipe.\n\n---\n\n## Step 4 — Interpret Results\n\n| Condition | Meaning |\n|-----------|---------|\n| `TSC_EXIT:0`, no grep output | ✅ Full project clean, your files are fine |\n| `TSC_EXIT:1`, no grep output | ✅ Your files are fine; pre-existing errors elsewhere (acceptable) |\n| `TSC_EXIT:1`, grep output present | ❌ Your files have errors — fix them |\n| `TSC_EXIT:2` | ❌ tsc configuration error (bad tsconfig, missing typescript package) |\n\n---\n\n## Fallback: Verify TypeScript Is Installed\n\nIf `node_modules\u002Ftypescript\u002Fbin\u002Ftsc` does not exist:\n\n```bash\n# Check if typescript is installed\nls node_modules\u002Ftypescript\u002Fbin\u002Ftsc 2>\u002Fdev\u002Fnull || echo \"TypeScript not installed\"\n\n# Install if needed\nnpm install --save-dev typescript\n# or\nyarn add --dev typescript\n```\n\n---\n\n## Full Example\n\n```bash\n# Store full tsc output and exit code\nTSC_OUTPUT=$(node_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1)\nTSC_EXIT=$?\n\n# Show only errors in newly-created files\nNEW_FILE_ERRORS=$(echo \"$TSC_OUTPUT\" | grep -E \"(settings-keys|settings-store|preferences|SettingsModal)\")\n\nif [ -z \"$NEW_FILE_ERRORS\" ]; then\n  echo \"✅ No TypeScript errors in new files (TSC_EXIT:$TSC_EXIT)\"\nelse\n  echo \"❌ TypeScript errors in new files:\"\n  echo \"$NEW_FILE_ERRORS\"\n  exit 1\nfi\n```\n\n---\n\n## Notes\n\n- This technique is safe for CI and local environments alike.\n- The direct `node_modules\u002Ftypescript\u002Fbin\u002Ftsc` path works on macOS, Linux, and Windows (via `node node_modules\u002Ftypescript\u002Fbin\u002Ftsc` on Windows CMD).\n- On Windows, replace the bash script with: `node node_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit`\n- Always prefer `--noEmit` for validation-only checks to avoid side effects.","# TypeScript Compile-Check (Resilient) with File-Scoped Error Filtering\n\nUse this workflow when you need to validate TypeScript changes in a project but the standard `npx tsc` or `node_modules\u002F.bin\u002Ftsc` invocations fail due to broken symlinks, missing PATH entries, or environment issues.\n\n---\n\n## When to Use This Skill\n\n- `npx tsc` fails with \"command not found\" or permission errors\n- `node_modules\u002F.bin\u002Ftsc` symlink is broken or unresolvable\n- You need to validate only *newly-created* or *task-specific* files without being blocked by pre-existing compile errors in the broader codebase\n\n---\n\n## Step 1 — Invoke tsc Directly via node_modules\n\nBypass `npx` and symlinks entirely by calling the TypeScript binary directly:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1; echo EXIT:$?\n```\n\n**Why this works:** The `tsc` CLI entry point is a plain Node.js script at `node_modules\u002Ftypescript\u002Fbin\u002Ftsc`. It does not depend on symlinks or PATH resolution. The `--noEmit` flag checks types without writing output files. Capturing `EXIT:$?` lets you programmatically detect success (`EXIT:0`) vs failure (`EXIT:1` or higher).\n\nIf the project uses a custom `tsconfig`, specify it explicitly:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit --project tsconfig.json 2>&1; echo EXIT:$?\n```\n\n---\n\n## Step 2 — Filter Output to Task-Specific Files Only\n\nWhen a legacy codebase has pre-existing errors, the full `tsc` output will be noisy and may cause false negatives. Pipe through `grep` to isolate errors from only the files you created or modified:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"(file-pattern)\" ; echo EXIT:${PIPESTATUS[0]}\n```\n\n### Examples\n\n**Single new file:**\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"settings-store\\.ts\"\n```\n\n**Multiple new files (pipe-delimited pattern):**\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"(settings-keys|settings-store|preferences|SettingsModal)\"\n```\n\n**All files in a specific directory:**\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"src\u002Ffeatures\u002Fmy-feature\u002F\"\n```\n\n**Check: no output = no errors in your files (success).**\n\n---\n\n## Step 3 — Capture Exit Code Correctly Through a Pipe\n\nWhen grepping, the shell exit code reflects `grep`, not `tsc`. Use `${PIPESTATUS[0]}` (bash) to recover the original `tsc` exit code:\n\n```bash\nnode_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1 \\\n  | grep -E \"(my-file-pattern)\"; echo \"TSC_EXIT:${PIPESTATUS[0]}\"\n```\n\nOr store errors explicitly:\n\n```bash\nTSC_OUTPUT=$(node_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1)\nTSC_EXIT=$?\necho \"$TSC_OUTPUT\" | grep -E \"(settings-keys|settings-store|preferences|SettingsModal)\"\necho \"TSC_EXIT:$TSC_EXIT\"\n```\n\nThe second approach (storing output in a variable) is the most reliable since `$?` is captured before the pipe.\n\n---\n\n## Step 4 — Interpret Results\n\n| Condition | Meaning |\n|-----------|---------|\n| `TSC_EXIT:0`, no grep output | ✅ Full project clean, your files are fine |\n| `TSC_EXIT:1`, no grep output | ✅ Your files are fine; pre-existing errors elsewhere (acceptable) |\n| `TSC_EXIT:1`, grep output present | ❌ Your files have errors — fix them |\n| `TSC_EXIT:2` | ❌ tsc configuration error (bad tsconfig, missing typescript package) |\n\n---\n\n## Fallback: Verify TypeScript Is Installed\n\nIf `node_modules\u002Ftypescript\u002Fbin\u002Ftsc` does not exist:\n\n```bash\n# Check if typescript is installed\nls node_modules\u002Ftypescript\u002Fbin\u002Ftsc 2>\u002Fdev\u002Fnull || echo \"TypeScript not installed\"\n\n# Install if needed\nnpm install --save-dev typescript\n# or\nyarn add --dev typescript\n```\n\n---\n\n## Full Example\n\n```bash\n# Store full tsc output and exit code\nTSC_OUTPUT=$(node_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit 2>&1)\nTSC_EXIT=$?\n\n# Show only errors in newly-created files\nNEW_FILE_ERRORS=$(echo \"$TSC_OUTPUT\" | grep -E \"(settings-keys|settings-store|preferences|SettingsModal)\")\n\nif [ -z \"$NEW_FILE_ERRORS\" ]; then\n  echo \"✅ No TypeScript errors in new files (TSC_EXIT:$TSC_EXIT)\"\nelse\n  echo \"❌ TypeScript errors in new files:\"\n  echo \"$NEW_FILE_ERRORS\"\n  exit 1\nfi\n```\n\n---\n\n## Notes\n\n- This technique is safe for CI and local environments alike.\n- The direct `node_modules\u002Ftypescript\u002Fbin\u002Ftsc` path works on macOS, Linux, and Windows (via `node node_modules\u002Ftypescript\u002Fbin\u002Ftsc` on Windows CMD).\n- On Windows, replace the bash script with: `node node_modules\u002Ftypescript\u002Fbin\u002Ftsc --noEmit`\n- Always prefer `--noEmit` for validation-only checks to avoid side effects.",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","showcase\u002Fskills\u002Ftypescript-compile-check-resilient","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":46,"prompt":55,"zipAvailable":56},[47,49,52],{"tool":29,"command":48},"npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill typescript-compile-check-resilient",{"tool":50,"command":51},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill typescript-compile-check-resilient",{"tool":53,"command":54},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill typescript-compile-check-resilient","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Ftypescript-compile-check-resilient\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},".skill_id","OTHER","其他",48,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Ftypescript-compile-check-resilient\u002F.skill_id",[65,84,100,109,139,155],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":34},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[20,72,73,18,74,75,33,76,77,32,78,79,80,28,25,81,82,83],"write","write special chars ts check","filters","characters","type-checking","for","script","output","type","template","file","python",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":34},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[91,92,72,82,93,83,94,95,96,97,98,81,99,31,75,77,78],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":34},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[107,72,75,108,78,95,81,82,83,77],"write special chars heredoc","shell",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":34},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[121,122,123,124,125,18,126,127,128,129,130,77,131,132,133,134,135,136,137,138],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":34},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[146,147,148,149,77,150,31,151,152,153,154],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":34},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[162,163,164,165,166,167,82,168,169,170],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]